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>
This commit is contained in:
@@ -571,7 +571,7 @@ static int __init pnpbios_init(void)
|
||||
return 0;
|
||||
}
|
||||
|
||||
subsys_initcall(pnpbios_init);
|
||||
fs_initcall(pnpbios_init);
|
||||
|
||||
static int __init pnpbios_thread_init(void)
|
||||
{
|
||||
|
Reference in New Issue
Block a user