On Fri, 04 Jul 2008, Matthew Garrett wrote: > Got it. The reason for the delay is that BRTO sits in a loop for no > obvious reason unless BRTF is cleared. The only thing that clears BRTF > is the PWMS function, which isn't called anywhere in the ACPI tables. > The NetBSD driver has the following code: > > /* Claim ownership of brightness control */ > param[0].Integer.Value = 0; > (void)AcpiEvaluateObject(sc->sc_node->ad_handle, "PWMS", ¶ms, NULL); > > and doing this in thinkpad_acpi means my brightness control works in an > acceptably speedy manner with opregion. Henrique, any thoughts on this? > If you're happy with it, we can get opregion support into .27 and add > the patch to remove duplicate ACPI video devices and everything will > work in a beautiful and harmonious manner. Well done! Please give me one or two days to check the data I have and look over the new DSDTs, and I will give you a better reply. I really should go over the FreeBSD and NetBSD thinkpad drivers with a fine comb looking over for stuff they figured out about the firmware that thinkpad-acpi doesn't know about yet. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
