diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2008-10-10 17:00:17 +0200 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-10-10 17:00:17 +0200 |
commit | ed458df4d2470adc02762a87a9ad665d0b1a2bd4 (patch) | |
tree | 7f5a8409b5b1514e05bf54c4c666711131f6de2f /drivers/ps3 | |
parent | Merge branch 'upstream-2.6.28' of git://git.kernel.org/pub/scm/linux/kernel/g... (diff) | |
download | linux-ed458df4d2470adc02762a87a9ad665d0b1a2bd4.tar.xz linux-ed458df4d2470adc02762a87a9ad665d0b1a2bd4.zip |
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>
Diffstat (limited to 'drivers/ps3')
0 files changed, 0 insertions, 0 deletions