From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] acpid: drop x86 architecture dependency
Date: Mon, 27 Aug 2018 18:07:01 +0200 [thread overview]
Message-ID: <20180827160701.13990-1-peter@korsgaard.com> (raw)
Closes #11241
While ACPI is historically exclusively a x86 feature, ia64 and (some) arm64
server platforms also use it. Furthermore, even if the firmware does not
provide an ACPI interface and/or the kernel is not built with ACPI support,
acpid can still be used to command an orderly shutdown of the system as it
also listens for KEY_POWER / KEY_SUSPEND events from the input subsystem
(and calls shutdown by default).
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
package/acpid/Config.in | 1 -
1 file changed, 1 deletion(-)
diff --git a/package/acpid/Config.in b/package/acpid/Config.in
index 2bd83ea8b9..b74e9d2262 100644
--- a/package/acpid/Config.in
+++ b/package/acpid/Config.in
@@ -1,6 +1,5 @@
config BR2_PACKAGE_ACPID
bool "acpid"
- depends on BR2_x86_64 || BR2_i386
help
Advanced Configuration and Power Interface event daemon.
--
2.11.0
next reply other threads:[~2018-08-27 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 16:07 Peter Korsgaard [this message]
2018-08-29 20:06 ` [Buildroot] [PATCH] acpid: drop x86 architecture dependency Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180827160701.13990-1-peter@korsgaard.com \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox