> Such a capability needs to be in the client side, since different >applications have different needs regarding the accuracy of the >Y'CbCr->RGB conversion for optimization. So, really here we just >need a method where Xv can tell a client 'I only support one >overlay at a time'.
Then make the interface smarter. Pass a flag to force a fail when the software would be needed. 90% of the apps will just want consistent behavior and won't want to full with fallback code. Forcing the client to implement alternate rendering methods is just going to make for a lot of mostly broken clients that work for some people some of the time (i.e. what we have now), if the client is smart enough to have another "better" software renderer then they should be smart enough to pass another flag. >I'm curious why the i810 driver would allow his code to get as >far as he did. >Sounds like a bug to me. He probably didn't call XvGrabPort(). Which would have prevented the second use of Xv. -Matt _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
