Hi,
I'm using X 4.3 (a backport on debian woody) with the precompiled
drivers from dri.sf.net and a radeon 9200. I currently have 3 issues
which I think may be down to the drivers:
1. In tuxracer, noegnud and some other programs, it seems that when 2D
bitmaps are drawn adjacent to each other,
Alan Cox wrote:
On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
The savage-1_0_0-branch wont work until the 3D driver is fixed up for
Mesa 4.x - it's still based on Mesa 3.4.
Is there any good info on doing this since the CLE266 driver has the
same problem
And the SiS driver. :) Our best bet w
Andreas Stenglein wrote:
diff -ru trunk_20030619/xc/xc/lib/GL/mesa/src/drv/radeon/radeon_tcl.c
tex3_20030619/xc/xc/lib/GL/mesa/src/drv/radeon/radeon_tcl.c
--- trunk_20030619/xc/xc/lib/GL/mesa/src/drv/radeon/radeon_tcl.cFri May 2
13:01:54 2003
+++ tex3_20030619/xc/xc/lib/GL/mesa/src/drv/
Ian,
thanks a lot for having a look at it.
Am 2003.06.27 03:19:00 +0200 schrieb(en) Ian Romanick:
> Andreas Stenglein wrote:
> > here is a patch that works at least for multiarb.c
> > It is against HEAD from 19 June 2003
> > (I cleaned it up a bit but its not ready for merge:
> > still some ques
Alex Deucher wrote:
--- Alan Cox <[EMAIL PROTECTED]> wrote:
On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
The savage-1_0_0-branch wont work until the 3D driver is fixed up
for
Mesa 4.x - it's still based on Mesa 3.4.
Is there any good info on doing this since the CLE266 driver has the
same
On Fri, Jun 27, 2003 at 06:53:08PM +0100, Alan Cox wrote:
> On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
> > The savage-1_0_0-branch wont work until the 3D driver is fixed up for
> > Mesa 4.x - it's still based on Mesa 3.4.
>
> Is there any good info on doing this since the CLE266 driver has
--- Alan Cox <[EMAIL PROTECTED]> wrote:
> On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
> > The savage-1_0_0-branch wont work until the 3D driver is fixed up
> for
> > Mesa 4.x - it's still based on Mesa 3.4.
>
> Is there any good info on doing this since the CLE266 driver has the
> same pro
On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
> The savage-1_0_0-branch wont work until the 3D driver is fixed up for
> Mesa 4.x - it's still based on Mesa 3.4.
Is there any good info on doing this since the CLE266 driver has the
same problem
> I think I've fixed up enough of the 2D driver t
On Fri, Jun 27, 2003 at 02:05:03PM -0300, Maximo wrote:
> At 01:52 PM 27/6/2003, Alan Cox wrote:
> >On Gwe, 2003-06-27 at 17:07, Maximo wrote:
> >> Hi,
> >>
> >> I got the Savage-1_0_0-branch from CVS e tried to compile it and i got no
> >> error but when I copied the drm modules do its place at
>
At 02:16 PM 27/6/2003, Alan Cox wrote:
> When your modifications will be available on Savage-1_0_0-branch?
I've no idea what people want to do about that. My cleaned up stuff wont
work with
2.2 or older 2.4 for example
Could you send me a diff with your changes?
-
At 01:52 PM 27/6/2003, Alan Cox wrote:
On Gwe, 2003-06-27 at 17:07, Maximo wrote:
> Hi,
>
> I got the Savage-1_0_0-branch from CVS e tried to compile it and i got no
> error but when I copied the drm modules do its place at /lib/modules/.
> e tried to load the module into memory i got this unre
On Gwe, 2003-06-27 at 18:05, Maximo wrote:
> >I've done some cleanup of the drm modules in the -ac tree, the ones they
> >included plain wont work
>
>
> When your modifications will be available on Savage-1_0_0-branch?
I've no idea what people want to do about that. My cleaned up stuff wont work
On Gwe, 2003-06-27 at 17:07, Maximo wrote:
> Hi,
>
> I got the Savage-1_0_0-branch from CVS e tried to compile it and i got no
> error but when I copied the drm modules do its place at /lib/modules/.
> e tried to load the module into memory i got this unresolved symbol error:
>
> /lib/modul
Hi,
I got the Savage-1_0_0-branch from CVS e tried to compile it and i got no
error but when I copied the drm modules do its place at /lib/modules/.
e tried to load the module into memory i got this unresolved symbol error:
/lib/modules/2.4.21/kernel/drivers/char/drm/savage.o: unresolved sy
I am browsing Mesa and r200 source, and I found small typo :-)
xc/lib/GL/mesa/src/drv/r200/r200_tex.c:125
_mesa_problem(NULL, "bad S wrap mode in %s", __FUNCTION__);
I think it should be:
_mesa_problem(NULL, "bad T wrap mode in %s", __FUNCTION__);
--
Free Software - find interesting programs
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugs.xfree86.org/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at th
16 matches
Mail list logo
