On Sun, 2006-08-27 at 19:19 +0200, Thomas Renninger wrote: > On Fri, 2006-08-25 at 20:59 +0900, Yasunori Goto wrote: > > > I sent a patch a while ago that gets rid of the whole namespace walking > > > by making acpi_memoryhotplug an acpi device and making use of the .add > > > callback function and the acpi_bus_register_driver call. > > > > > > I am not sure whether this is possible if you have multiple memory > > > devices, though (if not maybe it should be made possible?)... > > > > > > Yasunori even tested the patch and sent an Ok: > > > http://marc.theaimsgroup.com/?t=114065312400001&r=1&w=2 > > > > > > If this is acceptable I can rebase the patch on a current kernel. > > > > Hi. Thomas-san. > > Did you rebase your patch? > > > > I'm trying to do it now too. > > But, current code (2.6.18-rc4) seems to register handler for > > only enable status devices at boot time. > > So, notification is -discarded- due to no handler for new memory > > device when hot-add event occurs. Hmmm. :-( > > Trying again with a real mailer, sorry about the previous junk ... > The email address of the module author (naveen.b.s@xxxxxxxxx) seems to > be invalid? > > Thomas Sorry for taking so long to test this out. I just hooked it up with 2.6.18-rc4-mm3 (I built with CONFIG_ACPI_HOTPLUG_MEMORY=y) and I get ACPI Exception (acpi_bus-0071): AE_NOT_FOUND, No context for object [ffff81107357a5d0] [20060707] when I do a hot-add. It might be a day or two before I can sort out what is going on but I think Yasunori's mail may be getting at the issue. (My device is only presented to the OS at add time.) Thanks, Keith - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
