That all sounds like I was thinking apart from the whole frame being
sent to the encoder twice: is this by DirectFB or internal to the
encoder chip?
It's a hardware thing -- don't worry about it.
I'm just having a quick look through the source code for softdevice and
FIELD_PARITY does probe directfb to see if it is supported
Stefan has described what softdevice does -- apparently this is only checked if you're using the Matrox TVout.
Do your patches to viafb and DirectFB introduce FIELD_PARITY behaviour
but not advertise it as such?
Yeah, kind of. I'm happy to go the whole hog and do it properly but I need some advice as to what to do about the fact that doing it properly creates a dependency on a modified 'viafb' and needs a spec for an ioctl that we can agree on.
Mark
_______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
