Hi!
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
This file is linked from xf86ScanPci.c and should be deleted. Done.
Alan.
On Fri, Oct 25, 2002 at 12:53:24AM +0200, Dieter Nützel wrote:
dri-trunk/xc diff xc/programs/Xserver/hw/xfree86/scanpci/xf86PciData.c
xc/programs/Xserver/hw/xfree86/scanpci/xf86PciData.c.Dieter
1c1
/* $XFree86:
On Don, 2002-10-24 at 14:25, David Dawes wrote:
On Thu, Oct 24, 2002 at 02:00:48PM +0200, Michel Dänzer wrote:
On Don, 2002-10-24 at 13:52, Alan Hourihane wrote:
On Thu, Oct 24, 2002 at 01:47:01PM +0200, Michel Dänzer wrote:
That certainly shouldn't be needed for shared entities. Where
After the merge, *_dri.so doesn't work with the libGL from 4.2 anymore.
I suspect this is the same problem that has been fixed in the DRI tree
before. Unfortunately, I can't find it on a quick scan, hopefully
someone remembers.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc)
On Fri, Oct 25, 2002 at 05:11:17 +0200, Michel Dänzer wrote:
After the merge, *_dri.so doesn't work with the libGL from 4.2 anymore.
I suspect this is the same problem that has been fixed in the DRI tree
before. Unfortunately, I can't find it on a quick scan, hopefully
someone remembers.
I've
Do you know of any way I could enable the PCI slot in the ATI driver. I
have an embedded AGP Mach64 in a Dell Optiplex gx1pro. The AGP slot is not
available and I would like to use a Radeon 7500 PCI. I'm using XF86 4.2 and the
Radeon will work as a generic but nothing above 16-bit color and
On Fre, 2002-10-25 at 17:51, Alan Hourihane wrote:
On Fri, Oct 25, 2002 at 05:11:17 +0200, Michel Dänzer wrote:
After the merge, *_dri.so doesn't work with the libGL from 4.2 anymore.
I suspect this is the same problem that has been fixed in the DRI tree
before. Unfortunately, I can't find
Brian Paul wrote:
I've checked in a bunch of changes to Mesa CVS but haven't yet updated
the DRI mesa-4-1 branch to compensate - so it won't compile. I'll check
in my fixes (plus a new R200 feature) tomorrow.
OK, the mesa-4-1 branch should compile and work again.
I've implemented hardware
Keith,
I've heard you and others talk about triple buffering a few times, and
I'm wondering if you can fill me in on a few details. Is the primary
motivation for a 3rd buffer to aliviate delays associated with vertical
refresh? Using a page swapping method, I would guess the pointers for
W licie z pi, 25-10-2002, godz. 13:24, Michel Dnzer 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
On Fri, Oct 25, 2002 at 10:39:23AM -0600, Jens Owen wrote:
I've heard you and others talk about triple buffering a few times, and
I'm wondering if you can fill me in on a few details. Is the primary
motivation for a 3rd buffer to aliviate delays associated with vertical
refresh? Using a
I have posted message to [Dri-devel] and they asked me to provide more
info about xawtv (attached message). What I came upon is that xawtv
renders images directly into framebuffer, at address obtained form
'v4l-conf'. Am I right.
Well, not xawtv, but the grabber card (by PCI-PCI xfer).
Ian Romanick wrote:
On Fri, Oct 25, 2002 at 10:39:23AM -0600, Jens Owen wrote:
I've heard you and others talk about triple buffering a few times, and
I'm wondering if you can fill me in on a few details. Is the primary
motivation for a 3rd buffer to aliviate delays associated with vertical
Ian Romanick wrote:
On Fri, Oct 25, 2002 at 06:19:14PM +0100, Keith Whitwell wrote:
Ian Romanick wrote:
On Fri, Oct 25, 2002 at 10:39:23AM -0600, Jens Owen wrote:
I've heard you and others talk about triple buffering a few times, and
I'm wondering if you can fill me in on a few details.
On Fri, Oct 25, 2002 at 10:34:35AM -0700, Ian Romanick wrote:
Time step 1:
- Buffer 0 is being displayed (front buffer / display buffer).
- Buffer 1 is the render buffer (back buffer).
...
Time step 3:
- Finish rendering to buffer 2, and queue it to be displayed on the next
frame (front
On Thu, 24 Oct 2002 06:24:28 -0700
Ian Romanick [EMAIL PROTECTED] wrote:
On Thu, Oct 24, 2002 at 01:53:01PM +0200, Felix Kühling wrote:
Hi,
I tried all the mesa demos last night. The glutfx demo got a segfault
when exiting. I got this backtrace:
[snip]
I checked
Keith, Ian,
Thanks for educating me on the issues.
--
/\
Jens Owen/ \/\ _
[EMAIL PROTECTED] /\ \ \ Steamboat Springs, Colorado
---
This sf.net email is sponsored by: Influence the
Charl P. Botha wrote:
Dear list,
This bug has so far been reproduced on my M7 (mobile 7500) laptop with DRI
CVS as well as on a TiBook (i.e. PPC) with 7500 (thanks Wouter).
Download http://cpbotha.net/thingies/glthreads.c and compile it with
something like:
gcc -I../include -O3 -ansi -pedantic
Am Freitag, 25. Oktober 2002 22:22 schrieb Brian Paul:
Charl P. Botha wrote:
Dear list,
This bug has so far been reproduced on my M7 (mobile 7500) laptop with
DRI CVS as well as on a TiBook (i.e. PPC) with 7500 (thanks Wouter).
Download http://cpbotha.net/thingies/glthreads.c and
Am Montag, 14. Oktober 2002 22:36 schrieb Felix Kühling:
Hi,
here is a new set of frame throttling patches for the radeon and r200
drivers. It implements a second chance strategy to avoid ping-ponging
between busy waiting and IRQ waiting with very high frame rates.
Any results, yet?
I give
On Fri, 25 Oct 2002 23:44:21 +0200
Dieter Nützel [EMAIL PROTECTED] wrote:
Am Montag, 14. Oktober 2002 22:36 schrieb Felix Kühling:
Hi,
here is a new set of frame throttling patches for the radeon and r200
drivers. It implements a second chance strategy to avoid ping-ponging
between
On Fri, Oct 25, 2002 at 11:36:50PM +0200, Dieter Nützel wrote:
TaskParallelism: r200_vtxfmt.c:925: r200FlushVertices: Assertion `vb.context
== ctx' failed.
I think I have an idea about this, but I won't be able to try it out for a
bit. Doesn't radeonUnbindContext get called before
On Fri, Oct 25, 2002 at 01:15:15PM +0200, Michel Dänzer wrote:
On Don, 2002-10-24 at 14:25, David Dawes wrote:
On Thu, Oct 24, 2002 at 02:00:48PM +0200, Michel Dänzer wrote:
On Don, 2002-10-24 at 13:52, Alan Hourihane wrote:
On Thu, Oct 24, 2002 at 01:47:01PM +0200, Michel Dänzer wrote:
Am Freitag, 25. Oktober 2002 23:36 schrieb Dieter Nützel:
Am Freitag, 25. Oktober 2002 22:22 schrieb Brian Paul:
Charl P. Botha wrote:
Dear list,
This bug has so far been reproduced on my M7 (mobile 7500) laptop with
DRI CVS as well as on a TiBook (i.e. PPC) with 7500 (thanks
24 matches
Mail list logo
