On Sun, Apr 21, 2013 at 12:06:00AM +0200, Rafael J. Wysocki wrote: > On Friday, April 19, 2013 07:24:03 AM Seth Forshee wrote: > > On Mon, Mar 18, 2013 at 04:25:46PM -0500, Seth Forshee wrote: > > > > I've had the patches implementing your suggestions written for a while > > > > now but just got test feedback this week. So here they are. > > > > > > Ping. > > > > > > Matthew, do these patches look like what you had in mind? > > > > What needs to be done to move forward on this issue? Because so far no > > one besides Aaron has made any comment at all on the actual content of > > the patches. > > I'm not commenting mostly because I haven't had the time to think more about > this issue yet. Sorry about that. > > If I were to comment without much consideration, though, I'd say I wasn't > particularly impressed by any approach mentioned so far. I doubt there's going to be any "good" solution to this problem. What gives the best results is to force the affected models back to the pre-Win8 behavior, but of course that requires quirking. If we could assume that all graphics drivers will export backlight control then just disabling the ACPI interface for these machines would work nearly as well, but I don't think we can count on that, and it probably requires quirking as well. If we rule out quirking there are only a couple of options that anyone has suggested. We can hit every intermediate brightness level as in the patches I sent, but this is imperfect and requires a number of comprimises. Or we can test every level the machine claims to support and see which ones cause the value returned by _BQC to change, which seems like it ought to work but means changing the brightness during boot (which Matthew already objected to, though in another context). I haven't been able to think of any others, but I'm happy to listen to suggestions. Thanks, Seth -- 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
