On 10:31 Fri 31 May , Liu Ying wrote:
>2013/5/30 Jean-Christophe PLAGNIOL-VILLARD
>
> On 16:13 Thu 30 May , Liu Ying wrote:
> > We don't have to turn backlight on/off everytime a blanking
> > or unblanking event comes because the backlight status may have
> >
On 16:13 Thu 30 May , Liu Ying wrote:
> We don't have to turn backlight on/off everytime a blanking
> or unblanking event comes because the backlight status may have
> already been what we want. Another thought is that one backlight
> device may be shared by multiple framebuffers. We don't
We don't have to turn backlight on/off everytime a blanking
or unblanking event comes because the backlight status may have
already been what we want. Another thought is that one backlight
device may be shared by multiple framebuffers. We don't hope that
blanking one of the framebuffers would turn
We don't have to turn backlight on/off everytime a blanking
or unblanking event comes because the backlight status may have
already been what we want. Another thought is that one backlight
device may be shared by multiple framebuffers. We don't hope that
blanking one of the framebuffers would turn
On 16:13 Thu 30 May , Liu Ying wrote:
We don't have to turn backlight on/off everytime a blanking
or unblanking event comes because the backlight status may have
already been what we want. Another thought is that one backlight
device may be shared by multiple framebuffers. We don't hope
On 10:31 Fri 31 May , Liu Ying wrote:
2013/5/30 Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
On 16:13 Thu 30 May , Liu Ying wrote:
We don't have to turn backlight on/off everytime a blanking
or unblanking event comes because the backlight status may have
6 matches
Mail list logo
