Messages in this thread | | | Date | Wed, 21 Feb 2007 18:47:52 -0500 | From | "Jaya Kumar" <> | Subject | Re: [Linux-fbdev-devel] [PATCH 2.6.20 1/1] fbdev, mm: hecuba/E-Ink fbdev driver |
| |
On 2/21/07, Antonino A. Daplas <adaplas@gmail.com> wrote: > On Wed, 2007-02-21 at 11:55 -0500, Jaya Kumar wrote: > > > > You are right. I will need that. I could put that into struct > > fb_deferred_io. So drivers would setup like: > > > > Is it also possible to let the drivers do the 'deferred_io' > themselves? Say, a driver that would flush the dirty pages on > every VBLANK interrupt.
Yes, I think so. The deferred_io callback that the driver would get would be to provide them with the dirty pages list. Then, they could use that to handle the on-vblank work.
> > When the driver calls register_framebuffer and unregister_framebuffer, > > I can then do the init and destruction of the other members of that > > struct. Does this sound okay? > > It would be better if separate registering functions are created for > this functionality (ie deferred_io_register/unregister). >
Ok. Will do it that way.
Thanks, jaya - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |