On Thu, Sep 15, 2011 at 9:58 PM, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote: >> One of my biggest problems with KMS is that it has (naturally) a lot more >> complexity than the fb API which leads to instability. Basically it's very > > It shouldn't do - and a sample of one (your machine) is not a > statistically valid set. Fb is pretty much ununsable in contrast on my > main box, but that's not a statistically valid sample either. > > I'm not that convinced by the complexity either. For a simple video card > setup such as those that the fb layer can kind of cope with (ie linear > buffer, simple mode changes, no client rendering, no vblank flipping, > limited mode management, no serious multi-head) a DRM driver is also > pretty tiny and simple. That's not true, many drivers work around the lack of features in the fb API by providing custom interfaces. For example, in omapfb it's possible to use the overlays from user-space, configure some YUV format, do vsink, and multipages just fine: https://github.com/felipec/gst-omapfb/blob/master/omapfb.c It's perfect to render video clips. Of course, it would be even better if those custom interfaces were merged into the fb API. -- Felipe Contreras _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
