On Wed, 2011-07-13 at 15:22 +0300, Pasi Kärkkäinen wrote: > On Tue, Jul 12, 2011 at 10:01:25PM +0100, Matthew Garrett wrote: > > Please don't. ACPI lid state is not reliable on a range of hardware for > > a bunch of reasons, ranging from open events that are never fired to > > query methods that read from the wrong register. We can't pay attention > > to it by default, and running a survey doesn't change that. > > Ok. Do you know if there are other (better working) methods to get the lid state info? If we knew of any, they'd be implemented in the kernel, and we'd be using them. I know this is a frustrating thing to hear, and I empathize, I really do. But the state of the art right now is that there's one interface for laptop lids, it's in ACPI, and it's not reliable. Once upon a time there was an effort to make a Linux-based test kit for firmware [1], so vendors could run it before releasing hardware and verify that the Linux interfaces function. Lid state and lid events could have been one such test case. Sadly the effort seems to have stagnated; it could really use a revival. But even such a test kit would only fix new hardware, existing machines will continue to be as broken as they currently are forever. [1] - http://linuxfirmwarekit.org/ - ajax
Attachment:
signature.asc
Description: This is a digitally signed message part
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel