I will do my best to write a patch. But dont have that much experience in directfb. What would be the best place to dig in?
Should just be a matter of finding out what the API change was and changing the calls to match. I never got round to finding out what had changed. BTW is it possible to
findout and hardcode the surface hardware address in xine_decoder.c? I know it is not nice but at least I can have it working.
No, xine allocates up to 15 frame buffers for its display pipeline -- all these are allocated through DirectFB and it would be hard to hack this to work another way. I am going to try DirectFB-1.0.0-rc1. However, what would be the compatible
DFB++ and DirectFB-extra packages in order to compile xine-plugin? At least I want to play with a working device.
I think you'll need 1.0.0-rc1 versions of each. The xine output plugin (in DirectFB-extra) that the unichrome decoder plug-in uses changed completely soon after I think and my decoder plug-in doesn't work with the new one. Two more little questions if you don't mind:
1. Is libcle266 also incompatible with the latest DirectFB packages?
If you mean libcle266mpegdec, that doesn't use any DirectFB libraries itself. Use at least 0.4. 2. I have another topic about xine and hardware-osd problem which
has "df_xine-hrwOSD and viafb" topic in the directfb users mailing list. Any idea?
Yes, but you know that :-) Cheers, Mark
_______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
