https://bugs.freedesktop.org/show_bug.cgi?id=27859
--- Comment #10 from Kay Sievers <[email protected]> 2010-04-29 08:18:56 PDT --- (In reply to comment #9) > Also, what > about non-X use cases? How do we change the backlight in that case? The > kernel backlight interface would be the obvious choice; why create a second > one > for X that has to be duplicated in all the drivers? Well, this is not about a second mechanic controlling the same thing, it's just about a common higher-level interface on top of whatever is in charge of actual controlling the hardware. That it's using the low-level sysfs stuff on Linux is just an implementation detail that the higher-level randr interface should not export to desktop-like stuff at all. The X/non-X logic is actually the other way around, it's: if X controls the screen, it should also control the backlight belonging to the screen. And non-X custom use cases are obviously not touched at all by an interface provided by X. :) And the actual driver in X could be shared between all drivers if that is your concern. It could even be extended to support more than sysfs if needed, and all that logic would live well behind randr and not need to leak into any other crufty userspace logic. That all seems pretty simple and consistent to me. :) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
