It would need to be more like the DRI than Xv. It needs a library that determines what underlying library needs to be used based on the X server driver. So something like: detect the X renderer, dlopen an XvMC### library based on that information, hook up a dispatch table from the XvMC symbols to the dlopened HW specific symbols and go.
I think the basics are not a big deal. If you wanted to handle any type of multi-head setup there are probably bigger problems to solve. -Matt -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Deucher Sent: Friday, January 16, 2004 10:44 AM To: [EMAIL PROTECTED] Subject: shared XvMC lib What does the future hold for XvMC? I've been playing around with the open source savageXvMC lib that S3/VIA released. As I understand it now, you have to explicitly link you application with the particular XvMC lib you want to use. Are there any plans to make this more like Xv? That way apps could just link against libXvMC.so.1 or whatever and be able to use whatever XvMC support is available. There are getting to be quite a few XvMC inplementations available. what is needed to move this forward? XvMC support: i810/15 (open source) savage (open source) via (open and closed libs) nvidia (closed libs) ati (closed libs) Alex __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
