* Re: + pnp-mpu401-adjust-pnp_register_driver-signature.patch added to -mm tree [not found] <200603022340.k22Neq0o014875@shell0.pdx.osdl.net> @ 2006-03-03 0:55 ` Eric W. Biederman 2006-03-03 3:39 ` Bjorn Helgaas 2006-03-03 6:58 ` Matthieu CASTET 0 siblings, 2 replies; 4+ messages in thread From: Eric W. Biederman @ 2006-03-03 0:55 UTC (permalink / raw) To: linux-kernel; +Cc: bjorn.helgaas, ambx1, mm-commits akpm@osdl.org writes: > The patch titled > > pnp: mpu401: adjust pnp_register_driver signature > > has been added to the -mm tree. Its filename is > > pnp-mpu401-adjust-pnp_register_driver-signature.patch > > See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find > out what to do about this > > > From: Bjorn Helgaas <bjorn.helgaas@hp.com> > > This series of patches removes the assumption that pnp_register_driver() > returns the number of devices claimed. Returning the count is unreliable > because devices may be hot-plugged in the future. (Many devices don't support > hot-plug, of course, but PNP in general does.) Huh? How do onboard devices or ISA plug and play devices support hot-plug? Or what devices supported by the pnp subsystem support hot-plug? This may be a reasonable cleanup, but I'm worried about justifying it with supporting hardware that does not exist. Eric ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: + pnp-mpu401-adjust-pnp_register_driver-signature.patch added to -mm tree 2006-03-03 0:55 ` + pnp-mpu401-adjust-pnp_register_driver-signature.patch added to -mm tree Eric W. Biederman @ 2006-03-03 3:39 ` Bjorn Helgaas 2006-03-03 3:57 ` Eric W. Biederman 2006-03-03 6:58 ` Matthieu CASTET 1 sibling, 1 reply; 4+ messages in thread From: Bjorn Helgaas @ 2006-03-03 3:39 UTC (permalink / raw) To: Eric W. Biederman; +Cc: linux-kernel, bjorn.helgaas, ambx1, mm-commits >> This series of patches removes the assumption that pnp_register_driver() >> returns the number of devices claimed. Returning the count is >> unreliable >> because devices may be hot-plugged in the future. (Many devices don't >> support >> hot-plug, of course, but PNP in general does.) > > Huh? > > How do onboard devices or ISA plug and play devices support hot-plug? > > Or what devices supported by the pnp subsystem support hot-plug? I don't know for sure whether ISAPNP or PNPBIOS support hot-plug, but ACPI does, and ACPI devices are being integrated into the PNP subsystem via PNPACPI. One example is HP sx2000 hardware that supports hot-plug of cells. Each cell contains CPUs, memory, I/O bridges, and some miscellaneous hardware like on-board serial devices. All this stuff is described by ACPI, and we'd like to use PNP drivers like 8250_pnp.c when we can. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: + pnp-mpu401-adjust-pnp_register_driver-signature.patch added to -mm tree 2006-03-03 3:39 ` Bjorn Helgaas @ 2006-03-03 3:57 ` Eric W. Biederman 0 siblings, 0 replies; 4+ messages in thread From: Eric W. Biederman @ 2006-03-03 3:57 UTC (permalink / raw) To: Bjorn Helgaas; +Cc: linux-kernel, ambx1, mm-commits "Bjorn Helgaas" <bjorn.helgaas@hp.com> writes: >>> This series of patches removes the assumption that pnp_register_driver() >>> returns the number of devices claimed. Returning the count is >>> unreliable >>> because devices may be hot-plugged in the future. (Many devices don't >>> support >>> hot-plug, of course, but PNP in general does.) >> >> Huh? >> >> How do onboard devices or ISA plug and play devices support hot-plug? >> >> Or what devices supported by the pnp subsystem support hot-plug? > > I don't know for sure whether ISAPNP or PNPBIOS support hot-plug, > but ACPI does, and ACPI devices are being integrated into the > PNP subsystem via PNPACPI. > > One example is HP sx2000 hardware that supports hot-plug of cells. > Each cell contains CPUs, memory, I/O bridges, and some miscellaneous > hardware like on-board serial devices. All this stuff is described > by ACPI, and we'd like to use PNP drivers like 8250_pnp.c when we can. Ok, hot plug of motherboards. The pieces fall together now for me. Most things controlled by isapnp are either cold plug or not even pluggable (like most serial ports). So imaging them in a hot-plug situation takes some effort. But node/cell based NUMA systems where you plug and unplug motherboards. That make sense. Eric ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: + pnp-mpu401-adjust-pnp_register_driver-signature.patch added to -mm tree 2006-03-03 0:55 ` + pnp-mpu401-adjust-pnp_register_driver-signature.patch added to -mm tree Eric W. Biederman 2006-03-03 3:39 ` Bjorn Helgaas @ 2006-03-03 6:58 ` Matthieu CASTET 1 sibling, 0 replies; 4+ messages in thread From: Matthieu CASTET @ 2006-03-03 6:58 UTC (permalink / raw) To: linux-kernel Hi, Le Thu, 02 Mar 2006 17:55:47 -0700, Eric W. Biederman a écrit : > Huh? > > How do onboard devices or ISA plug and play devices support hot-plug? > Imagine a laptop that can dock on a base station. The laptop doesn't have midi, the base station have it. > Or what devices supported by the pnp subsystem support hot-plug? > For pnpacpi yes (maybe some code is still need). For pnpbios there something for dock event IIRC. Matthieu ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-03-03 6:58 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <200603022340.k22Neq0o014875@shell0.pdx.osdl.net>
2006-03-03 0:55 ` + pnp-mpu401-adjust-pnp_register_driver-signature.patch added to -mm tree Eric W. Biederman
2006-03-03 3:39 ` Bjorn Helgaas
2006-03-03 3:57 ` Eric W. Biederman
2006-03-03 6:58 ` Matthieu CASTET
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®