Re: [PATCH/RFC 2.6.20-rc4 1/1] fbdev,mm: hecuba/E-Ink fbdev driver

On Thu, 2007-01-11 at 19:22 -0500, Jaya Kumar wrote:

Agreed. Though I may be misunderstanding what you mean by first-touch.
Currently, I do a schedule_delayed_work and leave 1s between when the
page_mkwrite callback indicating the first touch is received and when
the deferred IO is processed to actually deliver the data to the
display. I picked 1s because it rounds up the display latency. I
imagine increasing the delay further may make it miss some desirable
display activity. For example, a slider indicating progress of music
may be slower than optimal. Perhaps I should make the delay a module
parameter and leave the choice to the user?

How about implementing the sync_page() aop? Then you could force the
flush using msync(MS_SYNC). 

Hmm... that might require more surgery but the idea would work I think.