Hi All, It turns out that some BIOSes add container device IDs as _CIDs to device object that in principle may be matched against the other scan handlers (or ACPI drivers, but that's not a problem, because the container scan handler can co-exist with an ACPI driver). That's why our recent fix for an issue related to the ACPI video driver had to be reverted right before -rc5. Although I submitted an alternative fix for that bug, I think the problem with the container scan handler possibly matching devices already having some other scan handlers attached needs addressing, because we may need to use the container hotplug profile for those devices. The following patch series is supposed to address it. [1/5] ACPI / scan: Do not bind ACPI drivers to objects with scan handlers (this version shouldn't break the Tony's IA64 HP box the previous one broke) [2/5] ACPI / scan: Separate hotplug profiles from scan handlers [3/5] ACPI / scan: Add hotplug profile pointer to struct acpi_device [4/5] ACPI / scan: Use container hotplug profile for matching device objects [5/5] ACPI / ia64 / sba_iommu: Use ACPI scan handler for discovery Patches [1-4/5] were run on my Toshiba test box and didn't break it, but it really doesn't do any ACPI hotplug notifications. Patch [5/5] is kind of additional, but it wouldn't work correctly without the previous ones (to be honest, I haven't tried to compile it yet, but here it goes for completness). The patches are against the linux-next branch of the linux-pm.git tree. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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
