Skip to content

Conversation

@nashif
Copy link
Member

@nashif nashif commented Nov 14, 2025

acpi is not really library code based on the new definition of what
should go into lib/. Move acpi into arch/x86/ where it is being used
exclusively.

Signed-off-by: Anas Nashif [email protected]

@zephyrbot zephyrbot added area: Tests Issues related to a particular existing or missing test area: X86 x86 Architecture (32-bit) area: MAINTAINER File labels Nov 14, 2025
@nashif nashif force-pushed the topic/arch/x86/acpi branch 2 times, most recently from 8a72d9c to ebede1b Compare November 14, 2025 12:46
acpi is not really library code based on the new definition of what
should go into lib/. Move acpi into arch/x86/ where it is being used
exclusively.

Signed-off-by: Anas Nashif <[email protected]>
@sonarqubecloud
Copy link

@dkalowsk
Copy link
Contributor

I'd like to point out that ACPI is not specifically tied to x86 and some platforms (notably Ampere's) make use of ACPI as well. Granted Ampere is not using the Zephyr library, but moving to x86 specific paths does limit future adoption for platforms that are not x86.

@nashif
Copy link
Member Author

nashif commented Nov 15, 2025

I'd like to point out that ACPI is not specifically tied to x86 and some platforms (notably Ampere's) make use of ACPI as well. Granted Ampere is not using the Zephyr library, but moving to x86 specific paths does limit future adoption for platforms that are not x86.

yeah, we can move it to arch/common, I do not really have a preference, anything but lib/acpi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: MAINTAINER File area: Tests Issues related to a particular existing or missing test area: X86 x86 Architecture (32-bit)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants