> I'm installing the patcher2k version now. Then I apply your patch. If > everything > works I'll create a working version with all benefits based on the latest VIA > release and push it back to them :)
That sounds an ideal solution. I've done a bit more work on viafb since the version I sent to this list: there was a race condition in determining the field parity when the framebuffer is opened: I've solved that by resetting the TV chip just after the CRTC starts a new field. I can send the new patch on Monday. > Didn't check yet which chip is used in the CN400. Do you think that your > patches will work on CN400, too? I've only changed the settings for the TV encoder, the way it gets reset and the implementation of the vsync ioctl. Since I only have access to the VT1622A encoder, I have only patched the tables for that chip. I think Nicolas Huillard was eventually able to create similar settings for the VT1622 (they are very similar). The TV encoder is a separate chip from the north bridge so I guess the changes should be equally applicable to the CN400. > I just need to grab all bits for this: patcher2k viafb, no scale patch and > field parity patch. Am I missing something? Just the latest version. I can let you have the patches I've made in DirectFB too if you like if this would help your testing. However, this code is not ready for inclusion. > Hmm, sounds like I should test on CLE266 first? That's what I've been working on. > But CLE266 has hw mpeg acceleration though? It does, but it's not supported yet. If you can implement it in xine-lib, that would be wonderful :-) Regards, Mark _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
