New libXvMC wrapper.

[Thomas Hellstrom]

Hi!

Sérgio Monteiro Basto wrote:

>Hi ,
>I read somewhere in this tread, that this wrapper might work with Savage
>drive, I still have the source for xvmc from VIA savage drive but never
>worked in earlier versions of X, and I don't know if ever works , but I
>like to try this wrapper on my laptop.
>
>So what I have to do? to try it out? :)
>
You'd need the savage XvMC code from http://www.linux.org/~alan/S3.zip
and the savage DRM from dri.sourceforge.net.

However, the wrapper is a convenience lib for packagers and player 
developers. You need to make
the player link to either the savage XvMC lib _OR_ the wrapper lib, but 
the wrapper won't make
it easier for you to make it work.

I've never heard of anybody making savage XvMC work, though.

/Thomas


>
>
>thanks ,
>
>On Tue, 2004-09-21 at 23:34, Thomas Hellstrom wrote:
>  
>
>>Hi, list!
>>
>>Anybody opposed to this going in it's current form? If not, it will be
>>enabled for
>>linux and gcc, where I know the -nostartfiles option will work.
>>
>>/Thomas
>>
>>
>>
>>Thomas Hellström wrote:
>>    
>>
>>>Hi! 
>>>
>>>I've attached a patch for a proposal of a libXvMC wrapper. 
>>>The purpose of the wrapper is to allow XvMC clients to link to
>>>different 
>>>hardware-specific dynamic XvMC libraries runtime. Contrary to the
>>>situation with libGL.so and the dri 3D drivers there is no builtin
>>>mechanism for this. 
>>>
>>>Current available XvMC libs include 
>>>libI810XvMC.so                       (in the Xorg tree) 
>>>libXvMCNVIDIA.so                  (Closed-source from Nvidia site) 
>>>libviaXvMC.so                         (With a nonstandard VLD
>>>extension available from the unichrome project) 
>>>and the savage XvMC code, which I haven't looked closer at. 
>>>
>>>Up to now the option has been to link to either of these (Xine, for
>>>example, links to the Nvidia driver) and this will mean the lib has
>>>to be present at runtime and the code will only work with Nvidia
>>>hardware. 
>>>
>>>The proposed solution eliminates this problem by providing a
>>>libXvMCW.so, which, at runtime, dlopens the library listed in the
>>>file <configdir>XvMCConfig and resolves the  necessary symbols,
>>>including , if present, the nonstandard VLD extension. This will
>>>make it possible for codes implementing this extension to also
>>>runtime link to libraries not including it. 
>>>
>>>Packagers wanting to include XvMC support for a media player can
>>>easily do so for all hardware that supports it, without having to
>>>include the HW specific libraries. 
>>>
>>>I've tested it with with linux, xine and the via (xine-xxmc) and
>>>Nvidia (xine-xvmc) drivers and it works as expected. It also loads
>>>and fires up the I810 driver but unfortunately I have no hardware to
>>>test it against. 
>>>
>>>Caveats could be portability: linking the lib requires the
>>>-nostartfiles gcc flag. I'm also not sure which implementations of
>>>dlopen supports library wrapping in this way. 
>>>
>>>Comments / Opinions would be appreciated. The diff is against
>>>current Xorg CVS, and also includes the 
>>>VLD extension header. 
>>>
>>>Thomas Hellström 
>>>The Unichrome project 
>>>
>>>
>>>____________________________________________________________________
>>>_______________________________________________
>>>xorg mailing list
>>>xorg at freedesktop.org
>>>http://freedesktop.org/mailman/listinfo/xorg
>>>  
>>>      
>>>
>>
>>______________________________________________________________________
>>_______________________________________________
>>xorg mailing list
>>xorg at freedesktop.org
>>http://freedesktop.org/mailman/listinfo/xorg
>>    
>>