From: Sven <lu...@dp...> - 2001-09-28 06:43:03
|
On Fri, Sep 28, 2001 at 09:48:52AM +0400, Nick Kurshev wrote: > Hello, Romain! > On Thu, 27 Sep 2001 11:31:25 +0200, you wrote: > > > Romain Dolbeau wrote: > > > > > Still, I guess I should use them ; I think I could add > > > a 'number of FOURCC supported' field in the > > > "struct fb_vidoverlay_avail", and add (yet) another > > > ioctl to get only the variable-length FOURCC list. > > > > F-up myself, here's an updated file. The sample implementation > > in pm3fb compile (not near thebox, can't test it yet :-) > > > > Any comment/criticism/improvement/advice very much welcome. > > > > -- > > DOLBEAU Romain | l'histoire est entierement vraie, puisque > > ENS Cachan / Ker Lann | je l'ai imaginee d'un bout a l'autre > > do...@ir... | -- Boris Vian > Well, it seems - o'k. > I'm not sure - but what about having a support of hardware accelerated > decoding? (I mean such things as mpeg1, mpeg2 decoding, de-zigzag and so on) > Unfortunatelly I never saw any opensource project which has implementation > of such things but if you know how it should be implemented then such extensions > are gladly accepted too. mmm, The Xv extension to X does this. That said, i guess the problem here would be the same as for generic accels in the kernel, that is it will not go in. Most probably, a userland library would need to be created which could cooperate with the fbdev driver. Friendly, Sven Luther |