A better patch without whitespace changes...
--- lib/GL/mesa/src/drv/mga/mgatexmem.c Sun Jan 27 12:59:37 2002
+++ lib/GL/mesa/src/drv/mga/mymgatexmem.c Sun Jan 27 13:12:48 2002
@@ -254,8 +254,18 @@
idx != MGA_NR_TEX_REGIONS nr MGA_NR_TEX_REGIONS ;
idx =
Panagiotis Papadakos wrote:
A better patch without whitespace changes...
--- lib/GL/mesa/src/drv/mga/mgatexmem.c Sun Jan 27 12:59:37 2002
+++ lib/GL/mesa/src/drv/mga/mymgatexmem.c Sun Jan 27 13:12:48 2002
@@ -254,8 +254,18 @@
idx != MGA_NR_TEX_REGIONS nr
On Son, 2002-01-27 at 13:01, Keith Whitwell wrote:
I'm having real trouble applying some of the patches I'm getting off the
mailing list - I'm not sure if it's me, or what.
What I'm doing is:
- saving the message from netscape (eg to ~/mgapat)
[ I assume you meant to follow up to the list as well ]
On Sam, 2002-01-26 at 19:15, Peter Surda wrote:
So I looked at the code: pid 0 doesn't exist, and r128 driver seems to be
using it for optimizing searches for free buffer. So I added a
buf-pid 0
[cut]
Further
On Fre, 2002-01-25 at 14:53, Alexander Stohr wrote:
1) The document XAA.HOWTO describes nicely the functionality
of the low-level hooks. Where can i find documentation on the
mid-level and GC-level hooks and flags?
I don't know, and I also think the Xpert list is probably a better place
to
Dear DRI developers,
I've updated the DRI-Devel-FAQ, now in
http://jrfonseca.tripod.com/dri/faq/html/ because my server has been down
all weekend due to (frustrating) network problems.
At this moment the FAQ is pretty close of what I had idealized that it
should be. It's still needing some
On Sun, Jan 27, 2002 at 06:03:42PM +0100, Michel Dnzer wrote:
[ I assume you meant to follow up to the list as well ]
yes it is possible I failed to do so.
The first one definitely wasn't correct. A process of pid 0 doesn't exist, but
it has been handled as if it existed.
The test (
On Sun, Jan 27, 2002 at 06:03:42PM +0100, Michel Dnzer wrote:
After digging around the code a bit, my current theory is that the
indirect buffer is incorrectly reused after the start of a new server
generation. The only difference I see in the radeon driver (which I
assume doesn't have the
On Sun, Jan 27, 2002 at 08:15:29PM -0300, Davor Buvinic wrote:
Works for me: ATI Xpert 128, XFree86 4.2.0, your patch against GATOS ATI
drivers sources. No more messages in the kernel log like the following:
[drm:r128_cce_indirect] *ERROR* process 1668 using buffer owned by 0
Yes this was
On Sun, 27 Jan 2002, Davor Buvinic wrote:
On Sunday 27 January 2002 16:53, you wrote:
On Sun, Jan 27, 2002 at 06:03:42PM +0100, Michel Dänzer wrote:
After digging around the code a bit, my current theory is that the
indirect buffer is incorrectly reused after the start of a new server
On Sunday 27 January 2002 20:43, you wrote:
On Sun, Jan 27, 2002 at 08:15:29PM -0300, Davor Buvinic wrote:
Works for me: ATI Xpert 128, XFree86 4.2.0, your patch against GATOS ATI
drivers sources. No more messages in the kernel log like the following:
[drm:r128_cce_indirect] *ERROR*
Hardware: Dell Inspiron 4100, Mobile Pentium III-M 1.0 GHz, Intel 830MP chipset
ATI Radeon Mobility LY (AGP), 16 Mb RAM
Software: SuSE 7.3, kernel 2.4.16 with devfs, XFree86-4.2.0 (WithPam and
WithPamMisc), management by xdm.
agpgart.o has two patches, see URL below for details.
On Sunday 27 January 2002 21:59, you wrote:
On Sun, 27 Jan 2002, Davor Buvinic wrote:
[...]
Works for me: ATI Xpert 128, XFree86 4.2.0, your patch against GATOS ATI
drivers sources. No more messages in the kernel log like the following:
[drm:r128_cce_indirect] *ERROR* process 1668 using
13 matches
Mail list logo
