On Fri, Nov 26, 2010 at 2:55 PM, Ville SyrjÃlà <ville.syrjala@xxxxxxxxx> wrote: > On Fri, Nov 26, 2010 at 05:38:11PM +0530, ext Hiremath, Vaibhav wrote: >> With this finding, in case of OMAP3 we have to use OMAPFB_WAITFORGO (breaking standard applications). > > Applications using the standard fbdev API won't work with manual update > displays anyway. You need omapfb specific code to handle it so having > another small difference is not a big deal. > > In DirectFB the that's trivial since there's already a simple omap > gfxdriver where you could override the default flip functionality with > WAITFORGO based stuff. > > Or, as I said, you could add another standard ioctl and fix up userspace > to use it where appropriate and if the kernel driver supports it. That sounds more appealing to me: there's no point in having omap-specific interfaces if they can be standard. -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
