]> www.pilppa.org Git - linux-2.6-omap-h63xx.git/commit
PnP: move pnpacpi/pnpbios_init to after PCI init
authorLinus Torvalds <torvalds@linux-foundation.org>
Fri, 10 Oct 2008 15:00:17 +0000 (08:00 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Fri, 10 Oct 2008 15:00:17 +0000 (08:00 -0700)
commited458df4d2470adc02762a87a9ad665d0b1a2bd4
tree7f5a8409b5b1514e05bf54c4c666711131f6de2f
parent82219fceeb654789a9dd7cd3c6cce12dbf659342
PnP: move pnpacpi/pnpbios_init to after PCI init

We already did that a long time ago for pnp_system_init, but
pnpacpi_init and pnpbios_init remained as subsys_initcalls, and get
linked into the kernel before the arch-specific routines that finalize
the PCI resources (pci_subsys_init).

This means that the PnP routines would either register their resources
before the PCI layer could, or would be unable to check whether a PCI
resource had already been registered.  Both are problematic.

I wanted to do this before 2.6.27, but every time we change something
like this, something breaks.  That said, _every_ single time we trust
some firmware (like PnP tables) more than we trust the hardware itself
(like PCI probing), the problems have been worse.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
drivers/pnp/Makefile
drivers/pnp/pnpacpi/core.c
drivers/pnp/pnpbios/core.c