Skip to content

acpi_drv: replace I/O memory backend by more dynamic variant #4452

@chelmuth

Description

@chelmuth

The current heuristic that all ACPI tables will fit into one size-aligned 1 GiB region does not work on a recent Tigerlake notebook. A dynamic I/O memory mapping approach could be implemented with a scoped pattern like follows.

  Memory::access(Memory::Range { first_byte, last_byte }, [&] (void *ptr) { ... });

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions