[patch 07/10] acpiphp: use new dock driver

2006-06-08 Thread akpm
From: Kristen Accardi <[EMAIL PROTECTED]> Modify the acpiphp driver to use the acpi dock driver for dock notifications. Only load the acpiphp driver if we find we have pci dock devices [EMAIL PROTECTED]: handle_hotplug_event_func() can now become static] Signed-off-by: Kristen Carlson Accardi <

[patch 10/10] ACPI: Atlas ACPI driver

2006-06-08 Thread akpm
From: [EMAIL PROTECTED] An ACPI driver for Atlas boards, including input support. Signed-off-by: Jaya Kumar <[EMAIL PROTECTED]> Cc: "Brown, Len" <[EMAIL PROTECTED]> Cc: Dmitry Torokhov <[EMAIL PROTECTED]> Cc: "Yu, Luming" <[EMAIL PROTECTED]> Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> ---

[patch 09/10] asus_acpi: W3000 support

2006-06-08 Thread akpm
From: Marek W <[EMAIL PROTECTED]> Add support for W3000 (W3V) and indirectly fixes an issue with kmilo under KDE (it was triggering excessive LCD read error messages by querying asus_acpi module) allowing people (I am probably the only one who tested this) with W3000 to run kmilo. Signed-off-by

[patch 01/10] asus_acpi_init: propagate correct return value

2006-06-08 Thread akpm
From: Andrew Morton <[EMAIL PROTECTED]> Cc: Bjorn Helgaas <[EMAIL PROTECTED]> Cc: "Brown, Len" <[EMAIL PROTECTED]> Acked-by: Francois Romieu <[EMAIL PROTECTED]> Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> --- drivers/acpi/asus_acpi.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[patch 03/10] Catch notification of memory add event of ACPI via container driver. (register start func for memory device)

2006-06-08 Thread akpm
From: Yasunori Goto <[EMAIL PROTECTED]> This is a patch to call add_memroy() when notify reaches for new node's add event. When new node is added, notify of ACPI reaches container device which means the node. Container device driver calls acpi_bus_scan() to find and add belonging devices (which

[patch 04/10] Catch notification of memory add event of ACPI via container driver. (avoid redundant call add_memory)

2006-06-08 Thread akpm
From: Yasunori Goto <[EMAIL PROTECTED]> When acpi_memory_device_init() is called at boottime to register struct memory acpi_memory_device, acpi_bus_add() are called via acpi_driver_attach(). But it also calls ops->start() function. It is called even if the memory blocks are initialized at early

[patch 05/10] KEVENT: add new uevent

2006-06-08 Thread akpm
From: Kristen Accardi <[EMAIL PROTECTED]> Add dock uevents so that userspace can be notified of dock and undock events. Signed-off-by: Kristen Carlson Accardi <[EMAIL PROTECTED]> Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]> Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> --- include/

[patch 06/10] acpi: dock driver

2006-06-08 Thread akpm
From: Kristen Accardi <[EMAIL PROTECTED]> Create a driver which lives in the acpi subsystem to handle dock events. This driver is not an acpi driver, because acpi drivers require that the object be present when the driver is loaded. Signed-off-by: Kristen Carlson Accardi <[EMAIL PROTECTED]> Cc:

[patch 08/10] acpiphp: prevent duplicate slot numbers when no _SUN

2006-06-08 Thread akpm
From: Kristen Accardi <[EMAIL PROTECTED]> Dock bridges generally do not implement _SUN, yet show up as ejectable slots. If you have more than one ejectable slot that does not implement SUN, with the current code you will get duplicate slot numbers. So, if there is no _SUN, use the current count

Re: 2.6.17-rc5-mm3: oops when ejecting dock

2006-06-08 Thread Jeremy Fitzhardinge
Kristen Accardi wrote: To me it seems unwise to do anything outside the ide subsystem other than notify of an event and call some handler or something. Sounds reasonable to me. I presume what happens (or should happen?) is that pressing the "want to undock" button would send an event to acpid