On Wed, 2009-04-08 at 12:17 +0200, Thomas Renninger wrote: > Matthew and Jesse are looking for following approach: > Let all drivers try to register for the generic backlight interface. > As we do not know which driver will get loaded first, you want to > detect whether another driver already registered the backlight > interface and implement a priority to eventually let the newly > loaded driver unregister the other driver's backlight device, notify > this driver via a notifier chain and then register the own backlight > interface (is that correct?). > > Priority could look like: > 1) vendor specific drivers > 2) ACPI generic drivers > 3) Graphics card's specific kernel drivers (IGD/Opregion and possibly > others) > 3 has highest prio. > > If I got that right, I do not like: > - the complexity that has to be added to the generic backlight > interface and each backlight driver.
I'm not arguing for or against any approach here but if we need to have this priority handoff system, I'd like to see it as a wrapper around the backlight class and the class itself is unlikely to need changes. The wrapper would register one backlight device with the generic class and then redirect the function calls as needed. Cheers, Richard ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
