From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Adrian Bunk <bunk@stusta.de>, Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, ibm-acpi-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: [2.6.20-rc4 regression] ibm-acpi: bay support disabled
Date: Tue, 9 Jan 2007 15:28:45 -0200 [thread overview]
Message-ID: <20070109172845.GA3528@khazad-dum.debian.net> (raw)
A new one for you, it exists since 2.6.20-rc2.
Subject : ThinkPad removable bay support disabled unconditionally
References : http://marc.theaimsgroup.com/?l=linux-acpi&m=116750681901208&w=2
Caused-By : Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Handled-By : Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Status : patch attached
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
ACPI: ibm-acpi: fix Kconfig entries for ibm-acpi bay and dock
Support for ACPI_BAY has not been merged in mainline yet. Usage of
"depends on FOO=n" fails if FOO is undefined, thus ibm-acpi support
for bay was being made non-available in a kernel that has no other
sort of bay support.
Fix it to use "depends on ! FOO" instead, that does the right thing
when FOO is undefined. Fix ACPI_IBM_DOCK accordingly as well while
at it, and also improve the help text.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
---
drivers/acpi/Kconfig | 17 ++++++++++-------
1 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
index 1639998..34cc8d5 100644
--- a/drivers/acpi/Kconfig
+++ b/drivers/acpi/Kconfig
@@ -215,26 +215,29 @@ config ACPI_IBM
config ACPI_IBM_DOCK
bool "Legacy Docking Station Support"
depends on ACPI_IBM
- depends on ACPI_DOCK=n
- default n
+ depends on ! ACPI_DOCK
+ default y
---help---
Allows the ibm_acpi driver to handle docking station events.
This support is obsoleted by CONFIG_HOTPLUG_PCI_ACPI. It will
allow locking and removing the laptop from the docking station,
but will not properly connect PCI devices.
- If you are not sure, say N here.
+ If you are not sure, select ACPI_DOCK instead.
config ACPI_IBM_BAY
bool "Legacy Removable Bay Support"
depends on ACPI_IBM
- depends on ACPI_BAY=n
- default n
+ depends on ! ACPI_BAY
+ default y
---help---
Allows the ibm_acpi driver to handle removable bays.
- This support is obsoleted by CONFIG_ACPI_BAY.
+ This support is obsoleted by CONFIG_ACPI_BAY. It will allow
+ enabling and disabling devices in the removable bays, but it
+ will not properly add or remove the devices from the kernel,
+ which must be done manually by userspace scripts.
- If you are not sure, say N here.
+ If you are not sure, select ACPI_BAY instead if it is available.
config ACPI_TOSHIBA
tristate "Toshiba Laptop Extras"
--
1.4.4.3
next reply other threads:[~2007-01-09 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 17:28 Henrique de Moraes Holschuh [this message]
2007-01-09 17:45 ` [2.6.20-rc4 regression] ibm-acpi: bay support disabled Adrian Bunk
2007-01-09 18:54 ` Henrique de Moraes Holschuh
2007-01-11 7:59 ` 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=20070109172845.GA3528@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=bunk@stusta.de \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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