> > That looks like a bug in the S3 driver, it seems to use the virtual > > address (i.e. what mmap() returns), not the physical one. That might > > break the v4l module too. > > Arg, grumble gumble... I will check what address XFree86-3 returned > in the past and work with that, just using 0xe0000000 gives me a interleaved > overlay immage all over the place :( try -bpp 24/32, the autodetect of that doesn't work allways correctly, it's just a guess based on the pixmap formats supported by the X-Server. Thats also one of the small annonying things which is fixed by using Xvideo + the v4l module (it _knows_ what the X-Server uses internally). > Gerd, am I right in assuming your card gives out a DGA frameadress > inside the cards PCI address? Yes. Matrox G200, mga driver. > When using the v4l module, it also sets (but now at X server starttime > - obvious) a frameaddress as DGA did. Same bug or it uses the same > address :( Exactly. > > The other one are image scaling ports. These can be used to give the > > X-Server a yuv image and let the gfx card conversion + scaling. This is > > what the movie players are using (and xawtv tries to use in grabdisplay > > mode). -scale / -noscale enables/disabled this one. > > > > Are VIDEO_PALETTE_YUYV + VIDEO_PALETTE_YUV422 the same? > > The Zoran does: (all 8 bit values) > Y1 V0 Y0 U0 > I'm not sure what format corresponds with this. I choose > VIDEO_PALETTE_YVYU Ok, looks like it's the same. xawtv uses VIDEO_PALETTE_YUV422. Try make that a alias for VIDEO_PALETTE_YUYV in the driver, xawtv should use the hw scaling in grabdisplay mode then. > (and YUYV when I reverse some register bit) 16bit or 32bit byteswap? 32bit I assume? Gerd -- Damn lot people confuse usability and eye-candy.
