On Thursday 09 April 2009 03:12:19 am yakui_zhao wrote: > On Wed, 2009-04-08 at 18:17 +0800, Thomas Renninger wrote: > > Hi, > > > > We have these interfaces: > > - vendor specific implementation > > (mostly in drivers/platform/x86/vendor-laptop.c) > > - ACPI generic backlight only > > - Opregion (this is the KMS/i915 interface you are talking about > > or is there another abstraction?) > > IMO it is unnecessary to consider the Opregion as the interface. In fact > it is only for the communication between the ACPI and graphics driver. > We can send the request by using ACPI generic backlight and then the > brightness is changed in the graphics driver. > > What you said is also OK. > But I don't know whether this will make the problem complex. > This issue I raised is related with that no backlight can be controlled > by xrandr tool after using KMS. > For example: >http://bugs.freedesktop.org/show_bug.cgi?id=20963 Why should this get a i915 and not a native samsung-laptop driver? Can someone come up with some example code how the backlight switching implementation for this one would look like. This is needed anyway and then it is much easier to think about how to make sure backlight drivers do not get double registered. Thomas -- 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
