W liście z pią, 25-10-2002, godz. 13:24, Michel Dänzer pisze:
> On Fre, 2002-10-25 at 09:15, Jacek Rosik wrote:
> >
> > Yesterday I've checked out latest CVS code from trunk an I've discovered
> > problems with motv (xawtv).
> >
> > http://stud.ics.p.lodz.pl/~paproch/dri/motv.jpeg
> >
> > Everything is ok with code before merge (tag: trunk-20021022). Any
> > clues?
> >
> > My TV board is Aver TV GO on bttv-v4l2 drivers, kernel 2.4.19. If
> > eanything other would be helpful just let me know.
>
> How does it render the TV image? Apparently not using the video overlay
> but directly to the framebuffer, maybe with DGA? It might be related to
> the RandR merge, what pitch is the driver using?
I think it renders directly into framebuffer. It uses v4l-conf to get
neccesary info. Here is description from manpage:
--
v4l-conf is a small helper tool. It figures out the video
mode and framebuffer base address of the graphics board
and configures a video4linux driver like bttv. This is
needed for drivers which can DMA the video over PCI
directly to the into the video memory.
--
--
v4l-conf knows tree ways to get the informations:
* Query the X-Server using the XF86 DGA extention. This
is the default if the DISPLAY environment variable is
set.
* Query the framebuffer driver. This is the default if
DISPLAY is not set.
* Query the console driver. This is used on mklinux
only
--
That is what I've found out for now. I have send an email to the author
of xawtv for further explanations.
> > BTW: When watching tv with page flipping enabled and GL app running. Tv
> > is rendered only to one 'page' no matter which is the curent one.
>
> Probably also because it renders directly to the framebuffer and doesn't
> know about the pageflipping.
>
>
> --
> Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
> XFree86 and DRI project member / CS student, Free Software enthusias
Some new info.
When I add '-shift n' option which shifts framebufer by 'n' bytes with
n=[1..8192] it is OK. Only strange behaviour when resizing, window
flickers for a second or two and then it's OK.
With new code when I run some OpneGL app when xawtv is running, xawtv
exits with error message.
When i start glgears with new code when xawtv is running it exits
displaying error message.
--
X Error of failed request: BadAlloc (insufficient resources for
operation)
Major opcode of failed request: 141 (XVideo)
Minor opcode of failed request: 19 ()
Serial number of failed request: 687
Current serial number in output stream: 687
--
Oh and my card is Radeon if it is of any use.
- Jacek
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
