Re: [PATCH] H22xx backlight support

Slavek Banko <[email protected]>
Newsgroups gmane.comp.handhelds.opie.devel
Organization axis, spol. s r. o.
Message-ID <[email protected]>
Dne úterý 30 květen 2006 22:25 Erik Hovland napsal(a):
> On Tue, May 30, 2006 at 09:25:16PM +0200, Michael 'Mickey' Lauer wrote:
> > Am Sonntag, den 28.05.2006, 16:58 +0200 schrieb Slavek Banko:
> > > I consider to replace all model
> > > specific /sys/class/backlight/_model_specific_device_/brightness
> > > and /sys/class/lcd/_model_specific_device_/power by code, that find
> > > devices by current contents of /sys/class/backlight/ and
> > > /sys/class/lcd/. That code will be common for more devices. Can I
> > > make it?
> >
> > Do you mean for all ipaqs or for all PDAs? I'm not sure whether we
> > want to have such a large reorganization done.
>
> There will be a day where all handhelds use the sysfs interface. But
> that isn't now. Many handhelds still run the 2.4 kernel. Only h2200 and
> hx4700 can be switched to sysfs for backlight in odevice_ipaq.cpp.
>
> E

I'm interested in code for all iPaqs with kernel 2.6. But the same 
solution can be used for all PDAs. Now is "model specific" code for ipaq, 
jornada, mypal, zaurus, htc and motorola_ezx.

Code for zaurus (and motorola_ezx) is better - Zaurus::init sets 
m_backlightdev by model and Zaurus::displayBrightnessResolution, 
Zaurus::setDisplayBrightness and Zaurus::setDisplayStatus is common for 
all zauruses with 2.6 kernel.

My concept assume to get "m_backlightdev" automatically by contents 
of /sys/class/backlight/ and /sys/class/lcd/. This will be common for all 
PDAa. I can make code at first for all iPaqs and next we can discuss 
about the right place for that code. May be?

Slavek
_______________________________________________

http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex

Opie-devel mailing list
[email protected]
https://handhelds.org/mailman/listinfo/opie-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.