| Summary: | ACPID shouldn't depend on BR2_x86_64 || BR2_i386 | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | happycorsair |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | buildroot, happycorsair |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
happycorsair
2018-08-17 17:59:48 UTC
Sorry, what firmware provides ACPI on your cubieboard? Or do you just mean that some of the functionality of acpid is usable without firmware/kernel support? drivers/acpi in the Linux kernel is guarded by ARCH_SUPPORTS_ACPI, which is selected for arm64/ia64/x86. With that said, if it builds on other architectures and there are use cases for it on those, then I don't have a problem exposing it. Hi, Peter! I'm not a specialist in ACPI or power management, so please don't blame me a lot :) It seems to me, that you are right. All ACPI-related options in Cubieboard 6 kernel config are disabled (it's ARM, not ARM64). But at the same time, acpid handles power button pushes and powers off the board. If no acpid is running, I can only reboot the board by long push. So, it's useful. I found no building issues. |