[Dri-devel] glLightfv() bug

2004-03-07 Thread Robert F Merrill
Bug in mesa's glLightfv() (src/mesa/main/light.c): When you send a 4-float array to glLightfv with GL_POSITION, the fourth float indicates whether the light is directional or positional. 1 is positional, 0 is directional. However, mesa checks for this after it does a matrix transform on the

[Dri-devel] Re: [Mesa3d-dev] glLightfv() bug

2004-03-07 Thread Robert F Merrill
Robert F Merrill wrote: Bug in mesa's glLightfv() (src/mesa/main/light.c): When you send a 4-float array to glLightfv with GL_POSITION, the fourth float indicates whether the light is directional or positional. 1 is positional, 0 is directional. However, mesa checks for this after it does a

[Dri-devel] Building DRM for 2.6.3. And mach64 randr.

2004-03-07 Thread Mike Mestnik
I was building mach64 drm for 2.6.3. I had the worst time convincing Makefile.linux and inturn Makefile.kernel that it was not lessthan25 and lessthan2552. I finaly gave up once I saw I had to gointo all the .h and .c files and add #defines there as well. Also I don't have a mach64 pro so I

[Dri-devel] 2D lossage when dri enabled

2004-03-07 Thread Tyler Retzlaff
I've been trying to get DRI (mga400/agp on NetBSD) working for a little while now and I have encountered a dead end. Sources being used are those tagged as xfree86 release 4.4 in the xfree cvs. The symptoms: When DRI is enabled (glxinfo says Direct Rendering: yes) my normal 2D in x11 is a

Re: [Dri-devel] Building DRM for 2.6.3. And mach64 randr and Kconf.

2004-03-07 Thread Mike Mestnik
I never got gatos to work on 2.6 but atitvout workes if I set X to 1024x768 or 800x600 or 640x480. It has problems with regard to VT switching and video mode changing. On a VT I run atitvout ntsc detect then switch to X running the mode I use 1024x768 for movies and 640x480 for nintendo games.

Re: [Dri-devel] suspend/resume ati igp 320M

2004-03-07 Thread Alex Deucher
--- Cristiano De Michele [EMAIL PROTECTED] wrote: Hi Michel, I'm using your dri-trunk debian packages on a compaq evo n1015v laptop with ati radeon IGP320M graphic adapter and all works fine concerning suspend/resume (swsusp 2.0.0.10+linux 2.4.25) as long as I don't use agpgart module. I

Re: [Dri-devel] suspend/resume ati igp 320M

2004-03-07 Thread Cristiano De Michele
Il dom, 2004-03-07 alle 17:13, Alex Deucher ha scritto: --- Cristiano De Michele [EMAIL PROTECTED] wrote: Hi Michel, I'm using your dri-trunk debian packages on a compaq evo n1015v laptop with ati radeon IGP320M graphic adapter and all works fine concerning suspend/resume (swsusp

Re: [Swsusp-devel] Re: [Dri-devel] suspend/resume ati igp 320M

2004-03-07 Thread Michael Frank
On Sun, 7 Mar 2004 08:13:14 -0800 (PST), Alex Deucher [EMAIL PROTECTED] wrote: --- Cristiano De Michele [EMAIL PROTECTED] wrote: Hi Michel, I'm using your dri-trunk debian packages on a compaq evo n1015v laptop with ati radeon IGP320M graphic adapter and all works fine concerning suspend/resume

Re: [Dri-devel] mach64 dri on freebsd 5.2

2004-03-07 Thread Leif Delgass
On Sun, 7 Mar 2004, Dave Airlie wrote: What is the status of mach64 dri support on freebsd 5.2 ? nobody has tested it for a while, so I say it suffers from bitrot... mach64-0-0-7 is the DRI branch to go with, and Mesa head, the code should all be there, just needing some updates for

Re: [Dri-devel] Building DRM for 2.6.3. And mach64 randr and Kconf.

2004-03-07 Thread Leif Delgass
On Sun, 7 Mar 2004, Mike Mestnik wrote: I never got gatos to work on 2.6 but atitvout workes if I set X to 1024x768 or 800x600 or 640x480. It has problems with regard to VT switching and video mode changing. On a VT I run atitvout ntsc detect then switch to X running the mode I use

Re: [Dri-devel] mach64 dri on freebsd 5.2

2004-03-07 Thread llewelly
Leif Delgass [EMAIL PROTECTED] writes: On Sun, 7 Mar 2004, Dave Airlie wrote: What is the status of mach64 dri support on freebsd 5.2 ? nobody has tested it for a while, so I say it suffers from bitrot... mach64-0-0-7 is the DRI branch to go with, and Mesa head, the code should

Re: [Dri-devel] Re: BillardGL problems

2004-03-07 Thread Sérgio Monteiro Basto
On Sun, 2004-03-07 at 01:37, Felix Kühling wrote: Program received signal SIGSEGV, Segmentation fault. 0x40757507 in generic_interp (ctx=0x0, t=0.918080449, edst=96, eout=21, ein=22, force_boundary=0 '\0') at t_vertex.c:736 736 a[0].insert[4-1]( a[0], vdst,

Re: [Dri-devel] [patch] Testing a theory about Savage lockups

2004-03-07 Thread Felix Kühling
On Sun, 7 Mar 2004 17:35:45 -0300 Paulo R. Dallan [EMAIL PROTECTED] wrote: Em Qui 04 Mar 2004 19:20, Felix Kühling escreveu: [snip] Hello Felix, Installed the new tree; Haven't tested it fully with wolf3d-et yet, but in Vegastrike, and, at a certain moment, had a similar error, already

Re: [Dri-devel] Savage XvMC

2004-03-07 Thread Sérgio Monteiro Basto
On Thu, 2004-03-04 at 20:15, Alex Deucher wrote: For those of you messing with XvMC support on savage, I just checked in a fix for the missing extension problem. I had forgotten to port over the setup code from S3's driver. I tested it briefly on savage4, but I only got an blue window. It's

[Dri-devel] [Fwd: [Fwd: xlibmesa-gl1-dri-trunk SIGFPE]]

2004-03-07 Thread Roberto Pariset
hello, last (few days ago) xlibmesa-gl1-dri-trunk was really great on my box (SiS + sid), but the one from yesterday makes dri program crash. here is an output from glxgears: Program received signal SIGFPE, Arithmetic exception. [Switching to Thread 1076844768 (LWP 3563)] 0x4043c56c in

Re: [Dri-devel] Re: BillardGL problems

2004-03-07 Thread Felix Kühling
On Sun, 07 Mar 2004 22:44:45 + Sérgio Monteiro Basto [EMAIL PROTECTED] wrote: On Sun, 2004-03-07 at 01:37, Felix Kühling wrote: [snip] Found it. I had already fixed this problem yesterday, but not committed it yet, because it didn't fix the problem I was actually hunting. ;-) I've

Re: [Dri-devel] Re: BillardGL problems

2004-03-07 Thread Sérgio Monteiro Basto
On Sun, 2004-03-07 at 23:34, Felix Kühling wrote: Found it. I had already fixed this problem yesterday, but not committed it yet, because it didn't fix the problem I was actually hunting. ;-) I've committed it now. A patch is attached for your convenience. Apply it in

Re: [Dri-devel] Assertion failure in savageBindTexture (was: Testing a theory about Savage lockups)

2004-03-07 Thread Felix Kühling
On Mon, 8 Mar 2004 00:05:37 +0100 Felix Kühling [EMAIL PROTECTED] wrote: On Sun, 7 Mar 2004 17:35:45 -0300 Paulo R. Dallan [EMAIL PROTECTED] wrote: Em Qui 04 Mar 2004 19:20, Felix Kühling escreveu: [snip] Hello Felix, Installed the new tree; Haven't tested it fully with wolf3d-et

Re: [Dri-devel] mach64 dri on freebsd 5.2

2004-03-07 Thread Dave Airlie
Thank you! It dies in xc/programs/Xserver/GL/mesa/X/xf86glx.c : xf86glx.c: In function `__MESA_setVisualConfigs': xf86glx.c:481: error: `kernel8' undeclared (first use in this function) xf86glx.c:481: error: (Each undeclared identifier is reported only once xf86glx.c:481: error: for each

Re: [Dri-devel] Building DRM for 2.6.3. And mach64 randr.

2004-03-07 Thread Dave Airlie
I was building mach64 drm for 2.6.3. I had the worst time convincing Makefile.linux and inturn Makefile.kernel that it was not lessthan25 and lessthan2552. I finaly gave up once I saw I had to gointo all the .h and .c files and add #defines there as well. Also I don't have a mach64 pro

Re: [Dri-devel] mach64 dri on freebsd 5.2

2004-03-07 Thread llewelly
Thank you for your time and your replies. Dave Airlie [EMAIL PROTECTED] writes: Thank you! It dies in xc/programs/Xserver/GL/mesa/X/xf86glx.c : xf86glx.c: In function `__MESA_setVisualConfigs': xf86glx.c:481: error: `kernel8' undeclared (first use in this function) xf86glx.c:481:

[Dri-devel] AGP and radeon driver

2004-03-07 Thread Jon Smirl
I'm trying to merge some of the functions from the radeon DRM and FB device drivers into a single driver. I've been working on the code for a week trying to get AGP working but I can't seem to figure out what is wrong. In drm/radeon_cp.c, radeon_cp_init_ring_buffer() there is a test to see if the

Re: [Dri-devel] mach64 dri on freebsd 5.2

2004-03-07 Thread Leif Delgass
I forgot to bring in the drm_linux_list.h for bsd that was added on the mach64-0-0-6-branch. I just added it and it is included from drmP.h. With any luck that should fix the compile errors in the kernel module. Leif On 7 Mar 2004 [EMAIL PROTECTED] wrote: Thank you for your time and your