Re: [PATCH 2.6.19-rc1 full] drivers: add LCD support

["Franck Bui-Huu" <vagabon.xyz@gmail.com>]

On 10/26/06, Miguel Ojeda <maxextreme@gmail.com> wrote:
> To be clearer. And you are wrong: you can write other modules which
> want to know what the LCD is showing, or use it; without worrying
> about framebuffer things. They can read / write "cfag12864b_buffer" as
> well as cfag12864bfb do. Why not?
>

Suppose I'm writing a user space application which uses your frame
buffer driver. I would naturaly mmap your device since it's the
easiest way to use a frame buffer. Now I want to display as fast as
possible a set of images. How am I sure that each image is sent to the
lcd ? For example, suppose the application just finished to copy image
A into the buffer,  and now it starts to copy image B into the buffer
but the work queue has not been scheduled yet...

Futhermore I'm not sure it's a common use case for such device, is it
? I would say that the usual case for such LCD is to display an image
every now and then. If so do we really need to give the possibility to
mmap the device ? Is a simple synchrone write() enough ?

BTW how can the application retrieve the refresh rate from the driver ?

                Franck