[Dri-devel] Maybe fixed shared texture object problem

2002-01-26 Thread Panagiotis Papadakos
I had the same problem with a G400 when I was using stereo with the Maverik lib.So I tried to find differences between the radeon_texmem.c and mgatexmem.c.And this is a small patch which has solved many of my problems.No my screen won't lock up and stereo views will work.I really don't know

Re: [Dri-devel] Bugfix for br0ken DMA on r128 and possibly radeonDMA functions

2002-01-26 Thread Michel Dänzer
On Sam, 2002-01-26 at 06:13, Peter Surda wrote: Sorry that I'm not sending a patch, but I don't know if my solution is correct. A patch might help to make a judgement. ;) Problem description (both with dri from CVS dri and CVS gatos): on r128 when I KDE is starting, display is corrupt and

Re: [Dri-devel] New Developer

2002-01-26 Thread Mike Westall
I, personally, found it useful to install the sources and incrementally turn on and/or add new diagnostic type print statements to gain an understanding of top to bottom control and information flow in a simple operation such as drawing a single triangle. gdb can also be useful in just gaining

Re: [Dri-devel] Bugfix for br0ken DMA on r128 and possibly radeon DMA functions

2002-01-26 Thread Peter Surda
On Sat, Jan 26, 2002 at 05:22:17PM +0100, Michel Dnzer wrote: On Sam, 2002-01-26 at 06:13, Peter Surda wrote: Sorry that I'm not sending a patch, but I don't know if my solution is correct. A patch might help to make a judgement. ;) Ok, here goes: --- drm-kernel/r128_state.c Thu Dec 13

Re: [Dri-devel] [PATCH] 2.4.17 DRM(ioremap) oops fix

2002-01-26 Thread Bjorn Helgaas
On Friday 25 January 2002 10:16 am, I wrote: When I start X on a kernel where agpgart is included but no gart device is found, X oopses on a null pointer dereference in radeon_ioremap. The attached patch avoids the oops, but should be reviewed by someone more knowledgeable about DRM than I.