I have posted some days ago, some problems on resume from suspend to
disk on my motherboard (asus p5ld2 se) related to acpi pnp. The serial
didn't worked after resume. Using pnpacpi=off it worked.
Now using this patch what will be the behaviour?
Bye
2007/1/19, Bjorn Helgaas <bjorn.helgaas@xxxxxx>:
The ACPI motherboard driver is mostly redundant with the PNP system
driver. This series moves the little bit of ACPI-specific stuff out
of the motherboard driver into acpi/osl.c, adds a little bit to the
PNP system driver so it covers all the remaining functionality of
the ACPI driver, and removes the ACPI driver.
Thanks for the comments on the previous version. This set of patches:
- Makes acpi_reserve_resources() a device_initcall(), so the FADT
resources will be reserved after the pnp/system driver claims its
resources. This lets us reserve a motherboard region larger than
the FADT describes without conflicts.
- Adds CONFIG_PNPACPI=y to the i386/defconfig patch. This is needed
for the pnp/system driver to find its devices.
Len asked about the CONFIG_PNP=n, CONFIG_ACPI=y case. In this case,
we won't have a pnp/system driver to claim motherboard resources. But
we already have this situation with other devices. My IR device
responds to ioports 0x100-0x10f and my ECP parallel port responds to
ioports 0x778-0x77a. If those drivers aren't loaded (or if they
aren't smart enough to claim all the resources), the resources just
aren't claimed.
So I think a better solution for this problem would be to make the
PNP core reserve all the regions for every active device, similar to
what PCI does.
Bjorn
-
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
-
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
