On Wed, 2009-06-17 at 02:33 +0800, Jesse Barnes wrote: > Well, what should we use then? Think of a common use case: you plug > in > an external monitor and shut your lid. Do we want to make the user > manually change their configuration? Or detect that the lid is no > longer in use? And what about the case where they boot with the lid > closed (e.g. in a docked scenario)? We want to support that > automatically too... This feature should work on most laptops. When the LID is closed, the LVDS is marked as disconnected. But this can't work for some boxes on which the initial Lid state is incorrect. We see such an exception on several laptops in ACPI bugzilla. If we expect this feature for most laptops, how about adding the exception boxes into the blacklist that doesn't support this feature? Thanks. > > If we can solve these issues some other way, that's fine, but right > now > we have nothing; I think my patch is an improvement over that, even if > it won't work everywhere w/o quirks. > > Len or Matthew, any comments -- 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
