From: Len Brown <len.brown@intel.com>
To: linux-acpi@vger.kernel.org
Cc: Len Brown <len.brown@intel.com>
Subject: [PATCH 5/7] ACPI: schedule obsolete features for deletion
Date: Thu, 11 Jan 2007 04:11:46 -0500 [thread overview]
Message-ID: <11685067141577-git-send-email-len.brown@intel.com> (raw)
Message-ID: <1bb67c2582f4271488721001a707124fd0af347e.1168506584.git.len.brown@intel.com> (raw)
In-Reply-To: <11685067121393-git-send-email-len.brown@intel.com>
In-Reply-To: <3948ec9406f9a60a43d63f23f6f5284db6529b9c.1168506584.git.len.brown@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
---
Documentation/feature-removal-schedule.txt | 45 ++++++++++++++++++++++++++++
1 files changed, 45 insertions(+), 0 deletions(-)
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 30f3c8c..2ee16b4 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -256,3 +256,48 @@ Why: Speedstep-centrino driver with ACPI hooks and acpi-cpufreq driver are
Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
---------------------------
+
+What: ACPI hotkey driver (CONFIG_ACPI_HOTKEY)
+When: 2.6.21
+Why: hotkey.c was an attempt to consolidate multiple drivers that use
+ ACPI to implement hotkeys. However, hotkeys are not documented
+ in the ACPI specification, so the drivers used undocumented
+ vendor-specific hooks and turned out to be more different than
+ the same.
+
+ Further, the keys and the features supplied by each platform
+ are different, so there will always be a need for
+ platform-specific drivers.
+
+ So the new plan is to delete hotkey.c and instead, work on the
+ platform specific drivers to try to make them look the same
+ to the user when they supply the same features.
+
+ hotkey.c has always depended on CONFIG_EXPERIMENTAL
+
+Who: Len Brown <len.brown@intel.com>
+
+---------------------------
+
+What: /sys/firmware/acpi/namespace
+When: 2.6.21
+Why: The ACPI namespace is effectively the symbol list for
+ the BIOS. The device names are completely arbitrary
+ and have no place being exposed to user-space.
+
+ For those interested in the BIOS ACPI namespace,
+ the BIOS can be extracted and disassembled with acpidump
+ and iasl as documented in the pmtools package here:
+ http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils
+
+Who: Len Brown <len.brown@intel.com>
+
+---------------------------
+
+What: /proc/acpi/button
+When: August 2007
+Why: /proc/acpi/button has been replaced by events to the input layer
+ since 2.6.20.
+Who: Len Brown <len.brown@intel.com>
+
+---------------------------
--
1.4.4.4.ge05d
next prev parent reply other threads:[~2007-01-11 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 9:11 patches on ACPI release branch Len Brown
[not found] ` <3948ec9406f9a60a43d63f23f6f5284db6529b9c.1168506584.git.len.brown@intel.com>
2007-01-11 9:11 ` [PATCH 1/7] ACPI: Altix: ACPI _PRT support Len Brown
[not found] ` <723fe2ca82d1ffc80c9d53035babf011f84c65d4.1168506584.git.len.brown@intel.com>
2007-01-11 9:11 ` [PATCH 2/7] ACPI: ec: enable printk on cmdline use Len Brown
[not found] ` <5d65131fa8d333d4575e7dfe5a05d3a9fa4a687e.1168506584.git.len.brown@intel.com>
2007-01-11 9:11 ` [PATCH 3/7] ACPI: rename cstate_entry_s to cstate_entry Len Brown
[not found] ` <d6637b28ffb38f207015c990e481fde5bba233d7.1168506584.git.len.brown@intel.com>
2007-01-11 9:11 ` [PATCH 4/7] ACPI: delete two spurious ACPI messages Len Brown
[not found] ` <1bb67c2582f4271488721001a707124fd0af347e.1168506584.git.len.brown@intel.com>
2007-01-11 9:11 ` Len Brown [this message]
[not found] ` <8b59a454c421542a51c391f542c80d165f7547a0.1168506584.git.len.brown@intel.com>
2007-01-11 9:11 ` [PATCH 6/7] ACPI: update MAINTAINERS Len Brown
[not found] ` <d2fadbbbf0e42b842731da71864f222e7f119461.1168506584.git.len.brown@intel.com>
2007-01-11 9:11 ` [PATCH 7/7] Revert "ACPI: ibm-acpi: make non-generic bay support optional" Len Brown
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=11685067141577-git-send-email-len.brown@intel.com \
--to=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).