Hi! > > > Hope this helps. > > > Pavel > > > > > > so the problem that I see is that this dsdt defines two separate dock > > devices, one outside the scope of pci, and one within it. The one > > outside the scope of pci defines the _EJ0 and _DCK methods. So, when > > acpiphp loads, it scans the pci slots for ejectable slots, finds none > > (because _EJ0 is defined in the dock device that is outside the scope of > > pci) and exits. This dsdt is different from the others I've used in > > that most of them define all methods related to docking under the actual > > dock bridge (within the scope of pci). perhaps some acpi people can > > shed some light on the best way to handle this - otherwise I'm sure I > > can hack something up that will be less than acceptable :). > > > > ACPI has (had?) a braindamage - it drops devices that do not present > when initially scanning ACPI namespace. So if you boot undocked - too > bad. Driver won't ever see your docking station.
I think I booted docked.... -- Thanks, Sharp! - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
