Re: [Dri-devel] savage-2-0-0 test notes
On Mon, 23 Feb 2004 14:18:53 -0600 Steve Holland [EMAIL PROTECTED] wrote: Felix Kühling wrote: If the span stuff is all that's needed then it should be working. Incidentally I tested the drawpix demo yesterday. It worked ok as long as it drew to the back buffer. Drawing to the front buffer was broken, though. It started scribbling all over the screen. Maybe that's all that needs to be fixed. drawpix does NOT work for me when drawing to the back buffer (just black window, no scribbling). Drawing to the front buffer causes scribbling all over the screen. (SuperSavage IX/C SDR) I'm at 16bit 1400x1050. Strange. It works on ProSavageDDR and SavageIX here. But I tested with the new driver on the DRI/Mesa trunk. Could you try updating? (question of # of args to do_unmap) Must be something about how fedora patches their kernels. I didn't need this to build on a stock 2.4.21 kernel from kernel.org. Unless you know a safe way to detect a fedora-patched kernel at build time I'm not going to change it in CVS. But it's good to know in case others stumble over the same problem. How about #ifdef DO_MUNMAP_4_ARGS (this is set by Makefile.linux)? Ok. I'll use that macro then. - The 'make install' does not create TLS versions of libGL, so it is necessary under Fedora Core 1 to remove the copies of libGL in /usr/X11R6/lib/tls/ to prevent using the old libGL (glxinfo reports indirect rendering even with DRI enabled). This should be added to the new building guide (see below) if it's not there already. It's not in there right now. Might it be better to have the 'make install' do this, or remove/rename the tls versions? I'm not an expert for this kind of problem. Personally I think this would be too much intelligence for a make install. As this is not a savage-specific problem, what do other developers think? Thanks again, Steve Felix --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] [Bug 881] 3D acceleration doesn't work
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=881 --- Additional Comments From [EMAIL PROTECTED] 2004-02-24 08:41 --- Anything new? -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA cvs: Compile problem with gcc-2.95.4
On Tue, Feb 24, 2004 at 03:29:01PM +0100, Martijn Uffing wrote: Ave people DRI/MESA won't compile with gcc 2.95.4 My system is debian stable with gcc 2.95.4 as system compiler. I get the error only with 2.95.4. If I use gcc 3.3.3 the whole buildtree compiles fine. I get the exact same error (and no error with gcc 3.3.3) on the savage-2-0-0 branch . The buildtree is DRI CVS with MESA CVS and both were updated minutes ago. The error is in the file DRI-CVS/xc/programs/Xserver/hw/xfree86/drivers/savage/savage_accel Part of buildlog: savage_accel.c: In function `SavageInitAccel': savage_accel.c:1391: parse error before `int' savage_accel.c:1395: `scanlines' undeclared (first use in this function) savage_accel.c:1395: (Each undeclared identifier is reported only once savage_accel.c:1395: for each function it appears in.) make[6]: *** [savage_accel.o] Error 1 Thanks for the report, I've just checked in the fix. Alan. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA cvs: Compile problem with gcc-2.95.4
--- Martijn Uffing [EMAIL PROTECTED] wrote: Ave people DRI/MESA won't compile with gcc 2.95.4 My system is debian stable with gcc 2.95.4 as system compiler. I get the error only with 2.95.4. If I use gcc 3.3.3 the whole buildtree compiles fine. I get the exact same error (and no error with gcc 3.3.3) on the savage-2-0-0 branch . The buildtree is DRI CVS with MESA CVS and both were updated minutes ago. The error is in the file DRI-CVS/xc/programs/Xserver/hw/xfree86/drivers/savage/savage_accel Part of buildlog: savage_accel.c: In function `SavageInitAccel': savage_accel.c:1391: parse error before `int' savage_accel.c:1395: `scanlines' undeclared (first use in this function) savage_accel.c:1395: (Each undeclared identifier is reported only once savage_accel.c:1395: for each function it appears in.) try declaring 'scanlines' at the top of the function rather than where it is now. perhaps 2.95 is stricter about mixed declarations and code. Alex make[6]: *** [savage_accel.o] Error 1 make[6]: Leaving directory `/mnt/schijf2/cvs-build/DRI-CVS/xc/programs/Xserver/hw/xfree86/drivers/savage' make[5]: *** [all] Error 2 make[5]: Leaving directory `/mnt/schijf2/cvs-build/DRI-CVS/xc/programs/Xserver/hw/xfree86/drivers' make[4]: *** [all] Error 2 make[4]: Leaving directory `/mnt/schijf2/cvs-build/DRI-CVS/xc/programs/Xserver/hw/xfree86' make[3]: *** [hw/xfree86] Error 2 make[3]: Leaving directory `/mnt/schijf2/cvs-build/DRI-CVS/xc/programs/Xserver' make[2]: *** [all] Error 2 make[2]: Leaving directory `/mnt/schijf2/cvs-build/DRI-CVS/xc/programs' make[1]: *** [all] Error 2 make[1]: Leaving directory `/mnt/schijf2/cvs-build/DRI-CVS/xc' make: *** [all] Error 2 [EMAIL PROTECTED]:~/cvs-build/DRI-CVS/xc$ Greetz Mu __ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Hardware TexSubImage
Ville Syrjälä wrote: Maybe this isn't what the the question was about but but we could try to upload only the changed parts of the texture. We'd just have to maintain dirty regions in addition to the simple dirty bits we now have. That would be useful, but it won't solve the problem Chris was seeing. I'm pretty sure that when TexSubImage is used to update a dynamic lightmap, the entire texture is replaced. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA cvs: Compile problem with gcc-2.95.4
On Tue, 24 Feb 2004, Alan Hourihane wrote: On Tue, Feb 24, 2004 at 03:29:01PM +0100, Martijn Uffing wrote: Ave people DRI/MESA won't compile with gcc 2.95.4 My system is debian stable with gcc 2.95.4 as system compiler. I get the error only with 2.95.4. If I use gcc 3.3.3 the whole buildtree compiles fine. I get the exact same error (and no error with gcc 3.3.3) on the savage-2-0-0 branch . The buildtree is DRI CVS with MESA CVS and both were updated minutes ago. The error is in the file DRI-CVS/xc/programs/Xserver/hw/xfree86/drivers/savage/savage_accel Part of buildlog: savage_accel.c: In function `SavageInitAccel': savage_accel.c:1391: parse error before `int' savage_accel.c:1395: `scanlines' undeclared (first use in this function) savage_accel.c:1395: (Each undeclared identifier is reported only once savage_accel.c:1395: for each function it appears in.) make[6]: *** [savage_accel.o] Error 1 Thanks for the report, I've just checked in the fix. Alan. Ave Alan. Hereby comfirmation of the fix. It compiles fine now. And thanx for the extremely fast response. Greetz Mu --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Mesa3d-dev] Re: [Dri-devel] [r200] regression in ipers wireframe do not work with fog
Dieter Nützel wrote: Am Montag, 23. Februar 2004 22:11 schrieb Brian Paul: Keith Whitwell wrote: Dieter Nützel wrote: Cheers, Dieter Probably worth posting this on Mesa lists as it is likely to pertain to the changes Brian's made recently to the fog code. As is, the ipers demo's fog settings aren't very effective (toggling fog on/off has little/no apparent effect). Very true. The scene is only somewhat brighter or darker ;-) Is the r200 driver producing different results than software rendering? Yes. Software rendering is OK. Sorry, I haven't tested before. r200 show wireframe mode only when fog is disabled, now (after your latest patches). OK, I've checked in a change which might fix things. Let me know. -Brian --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] savage-2-0-0 test notes
Gregory Davis wrote: On Sunday 22 February 2004 03:15 pm, Steve Holland wrote: I downloaded and tested the savage-2-0-0 branch yesterday. This is on an IBM ThinkPad T23 with a SuperSavage IX/C SDR. It works really well! Congratulations and thanks, guys! A few notes (savage-2-0-0 branch 2/21/04): - tuxracer runs great! Well, glFog() seems to be screwed up for me, 2/23/04 from trunk. I built according to the new build instructions and pointed to the Mesa cvs tree in host.def. However, tuxracer foreground stuff is all white when fog is turned on (sometimes I can see a little texture, so its almost like the fog factor is set way too high). Tuxracer is linked against the current X11R6 GL and GLU libraries. The code is in src/fog.c of the tuxracer-0.61 tarball. The chip is a Savage4 on a creative labs motherboard: ... (II) SAVAGE(0): [agp] Mode 0x1b000213 [AGP 0x10b9/0x1647; Card 0x5333/0x8a22] ... Greg Davis In the savage driver, after the calls to _swrast_allow_pixel/vertex_fog(), put in corresponding calls to _tnl_allow_pixel/vertex_fog() and see what happens. I checked in this change to the r200 driver as an experiment. If it works there then the other drivers should be updated too. -Brian --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] host.def config
Ave people In a lot of emails regarding building DRI CVS with Mesa CVS it's mentioned that you should define something like this in host.def: #define MesaSrcDir /path/to.Mesa However,I'm using the next entry in host.def #define MesaSrcDir $(TOP)/Mesa-newtree De directory Mesa-newtree refers to Buildtree/xc/Mesa-newtree Is this supposed to work, or does it just work by accident? If it's supposed to work, maybe another entry in the build manual would be helpful. Because using with the latter configuration, buildtrees are easily moveable to other directories without changing the hard coded path in host.def Greetz Mu --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] host.def config
Martijn Uffing wrote: Ave people In a lot of emails regarding building DRI CVS with Mesa CVS it's mentioned that you should define something like this in host.def: #define MesaSrcDir /path/to.Mesa However,I'm using the next entry in host.def #define MesaSrcDir $(TOP)/Mesa-newtree De directory Mesa-newtree refers to Buildtree/xc/Mesa-newtree Is this supposed to work, or does it just work by accident? If it's supposed to work, maybe another entry in the build manual would be helpful. Because using with the latter configuration, buildtrees are easily moveable to other directories without changing the hard coded path in host.def If you have a copy of the Mesa tree at that location, it would be no different than having it at /usr/local/src/Mesa-newtree. I don't understand what's special about it. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA cvs: Compile problem with gcc-2.95.4
On Tue, 2004-02-24 at 14:40, Alan Hourihane wrote: On Tue, Feb 24, 2004 at 03:29:01PM +0100, Martijn Uffing wrote: Ave people DRI/MESA won't compile with gcc 2.95.4 My system is debian stable with gcc 2.95.4 as system compiler. I get the error only with 2.95.4. If I use gcc 3.3.3 the whole buildtree compiles fine. I get the exact same error (and no error with gcc 3.3.3) on the savage-2-0-0 branch . The buildtree is DRI CVS with MESA CVS and both were updated minutes ago. Thanks for the report, I've just checked in the fix. I update savage-2-0-0 branch minutes ago and with gcc 3.3.x now give me a bunch of warnings! yesterday I almost sure that I haven't so many warnings How can I know? what has been updated since yesterday ? -- Sérgio M. B. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA cvs: Compile problem with gcc-2.95.4
On Tue, Feb 24, 2004 at 05:57:34PM +, Sérgio Monteiro Basto wrote: On Tue, 2004-02-24 at 14:40, Alan Hourihane wrote: On Tue, Feb 24, 2004 at 03:29:01PM +0100, Martijn Uffing wrote: Ave people DRI/MESA won't compile with gcc 2.95.4 My system is debian stable with gcc 2.95.4 as system compiler. I get the error only with 2.95.4. If I use gcc 3.3.3 the whole buildtree compiles fine. I get the exact same error (and no error with gcc 3.3.3) on the savage-2-0-0 branch . The buildtree is DRI CVS with MESA CVS and both were updated minutes ago. Thanks for the report, I've just checked in the fix. I update savage-2-0-0 branch minutes ago and with gcc 3.3.x now give me a bunch of warnings! yesterday I almost sure that I haven't so many warnings How can I know? what has been updated since yesterday ? Use cvs's -D yesterday and see what changed. Other than that. Post your warning messages and let's take a look, as I've not currently get gcc 3.3.x installed. Alan. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA cvs: Compile problem with gcc-2.95.4
On Tue, 2004-02-24 at 14:40, Alan Hourihane wrote: Thanks for the report, I've just checked in the fix. Alan. Now DRI/MESA won't compile with gcc 3.3 the output of make World have 3 megas bytes ! mapr.c:56: warning: ISO C90 does not support `long long' mmapr.c: In function `main': mmapr.c:226: warning: ISO C90 does not support `long long' mmapw.c:56: warning: ISO C90 does not support `long long' mmapw.c: In function `main': mmapw.c:97: warning: ISO C90 does not support `long long' mmapw.c:194: warning: ISO C90 does not support `long long' mmapw.c:195: warning: ISO C90 does not support `long long' macro in not recognized -- ignoring xdriinfo.c: In function `main': xdriinfo.c:60: warning: pointer targets in passing arg 1 of `glXGetProcAddress' differ in signedness xdriinfo.c:61: warning: pointer targets in passing arg 1 of `glXGetProcAddress' differ in signedness -- Sérgio M. B. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA cvs: Compile problem with gcc-2.95.4
On Tue, Feb 24, 2004 at 06:09:06PM +, Sérgio Monteiro Basto wrote: On Tue, 2004-02-24 at 14:40, Alan Hourihane wrote: Thanks for the report, I've just checked in the fix. Alan. Now DRI/MESA won't compile with gcc 3.3 the output of make World have 3 megas bytes ! mapr.c:56: warning: ISO C90 does not support `long long' mmapr.c: In function `main': mmapr.c:226: warning: ISO C90 does not support `long long' mmapw.c:56: warning: ISO C90 does not support `long long' mmapw.c: In function `main': mmapw.c:97: warning: ISO C90 does not support `long long' mmapw.c:194: warning: ISO C90 does not support `long long' mmapw.c:195: warning: ISO C90 does not support `long long' macro in not recognized -- ignoring xdriinfo.c: In function `main': xdriinfo.c:60: warning: pointer targets in passing arg 1 of `glXGetProcAddress' differ in signedness xdriinfo.c:61: warning: pointer targets in passing arg 1 of `glXGetProcAddress' differ in signedness This has nothing to do with the change I checked in. Alan. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] savage-2-0-0 test notes
On Tue, 24 Feb 2004 09:56:29 -0700 Brian Paul [EMAIL PROTECTED] wrote: Gregory Davis wrote: [snip] Greg Davis In the savage driver, after the calls to _swrast_allow_pixel/vertex_fog(), put in corresponding calls to _tnl_allow_pixel/vertex_fog() and see what happens. I just tried this. Now there is no fog at all in tuxracer. I checked in this change to the r200 driver as an experiment. If it works there then the other drivers should be updated too. -Brian Felix --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] savage-2-0-0 test notes
On Tue, 24 Feb 2004 19:33:16 +0100 Felix Kühling [EMAIL PROTECTED] wrote: On Tue, 24 Feb 2004 09:56:29 -0700 Brian Paul [EMAIL PROTECTED] wrote: Gregory Davis wrote: [snip] Greg Davis In the savage driver, after the calls to _swrast_allow_pixel/vertex_fog(), put in corresponding calls to _tnl_allow_pixel/vertex_fog() and see what happens. I just tried this. Now there is no fog at all in tuxracer. But fog looks ok in flightgear now. So this fix is ok but there's probably another problem with fog in tuxracer. With Mesa 5.0 (on the savage-2-0-0-branch) fog was ok in tuxracer too. Felix --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA cvs: Compile problem with gcc-2.95.4
Sérgio Monteiro Basto wrote: On Tue, 2004-02-24 at 14:40, Alan Hourihane wrote: Thanks for the report, I've just checked in the fix. Now DRI/MESA won't compile with gcc 3.3 the output of make World have 3 megas bytes ! Does the build fail or just give a bunch of warnings? I've been building with GCC 3.3.1 for months with no problems. The warnings, particularly the ones about C89 does not allow or C90 does not allow are pretty irritating, though. I just did a fresh build from current CVS. It generated 3.2MB of log file, and 1195 lines with the string 'warning:'. Ouch. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] savage-2-0-0 test notes
Felix Kühling wrote: On Tue, 24 Feb 2004 19:33:16 +0100 Felix Kühling [EMAIL PROTECTED] wrote: On Tue, 24 Feb 2004 09:56:29 -0700 Brian Paul [EMAIL PROTECTED] wrote: Gregory Davis wrote: [snip] Greg Davis In the savage driver, after the calls to _swrast_allow_pixel/vertex_fog(), put in corresponding calls to _tnl_allow_pixel/vertex_fog() and see what happens. I just tried this. Now there is no fog at all in tuxracer. But fog looks ok in flightgear now. So this fix is ok but there's probably another problem with fog in tuxracer. With Mesa 5.0 (on the savage-2-0-0-branch) fog was ok in tuxracer too. I don't have tuxracer handy - I'll have to download it later. Do you happen to know which fog mode is used, and if the GL_FOG_HINT is set? -Brian --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] host.def config
On Tue, 24 Feb 2004, Ian Romanick wrote: Martijn Uffing wrote: Ave people In a lot of emails regarding building DRI CVS with Mesa CVS it's mentioned that you should define something like this in host.def: #define MesaSrcDir /path/to.Mesa However,I'm using the next entry in host.def #define MesaSrcDir $(TOP)/Mesa-newtree De directory Mesa-newtree refers to Buildtree/xc/Mesa-newtree Is this supposed to work, or does it just work by accident? If it's supposed to work, maybe another entry in the build manual would be helpful. Because using with the latter configuration, buildtrees are easily moveable to other directories without changing the hard coded path in host.def If you have a copy of the Mesa tree at that location, it would be no different than having it at /usr/local/src/Mesa-newtree. I don't understand what's special about it. Well,it's easier to move buildtrees around. Just a move of xc to /whatever/xc will work and keeps Mesa building. But indeed,if you keep Mesa in a fixed location like /usr/local/Mesa-newtree and move the xc dir, the buildtree keeps building with the standard host.def entry and breaks with my solution. So never mind my solution. Greetz Mu --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] savage-2-0-0 test notes
On Tue, Feb 24, 2004 at 02:01:39PM -0700, Brian Paul wrote: Felix Kühling wrote: On Tue, 24 Feb 2004 19:33:16 +0100 Felix Kühling [EMAIL PROTECTED] wrote: On Tue, 24 Feb 2004 09:56:29 -0700 Brian Paul [EMAIL PROTECTED] wrote: Gregory Davis wrote: [snip] Greg Davis In the savage driver, after the calls to _swrast_allow_pixel/vertex_fog(), put in corresponding calls to _tnl_allow_pixel/vertex_fog() and see what happens. I just tried this. Now there is no fog at all in tuxracer. But fog looks ok in flightgear now. So this fix is ok but there's probably another problem with fog in tuxracer. With Mesa 5.0 (on the savage-2-0-0-branch) fog was ok in tuxracer too. I don't have tuxracer handy - I'll have to download it later. Do you happen to know which fog mode is used, and if the GL_FOG_HINT is set? Brian, It uses NICEST. Alan. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA cvs: Compile problem with gcc-2.95.4
One reboot to computer has resolved the problem. Sorry for my mistake and thanks for your support. -- Sérgio M. B. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] savage-2-0-0 test notes
On Tue, 24 Feb 2004 14:01:39 -0700 Brian Paul [EMAIL PROTECTED] wrote: Felix Kühling wrote: On Tue, 24 Feb 2004 19:33:16 +0100 Felix Kühling [EMAIL PROTECTED] wrote: On Tue, 24 Feb 2004 09:56:29 -0700 Brian Paul [EMAIL PROTECTED] wrote: Gregory Davis wrote: [snip] Greg Davis In the savage driver, after the calls to _swrast_allow_pixel/vertex_fog(), put in corresponding calls to _tnl_allow_pixel/vertex_fog() and see what happens. I just tried this. Now there is no fog at all in tuxracer. But fog looks ok in flightgear now. So this fix is ok but there's probably another problem with fog in tuxracer. With Mesa 5.0 (on the savage-2-0-0-branch) fog was ok in tuxracer too. I don't have tuxracer handy - I'll have to download it later. Do you happen to know which fog mode is used, and if the GL_FOG_HINT is set? I don't know which fog mode it uses. The Savage driver can only do vertex for ATM. I tried --fog-fastest and --fog-nicest in flightgear, both looked the same. -Brian Felix --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] test report on savage twister k
Well I test the savage-2-0-0-0 branch and the trunk cvs I test this games foobillard q3demo with (cvs) wineX: Max Payne and CM 03/04 Pinball Tux Racer chromium and it is amazing !! better than ever. For WineX (see http://ting.homeunix.org/) and in case of OS use prelink please read: http://www.transgaming.com/showthread.php?msg=33759forum=1018thread=33637 Last note: If you want try savage-2-0-0-0-branch you have to compile module in xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel, from same tree or 2D doesn't work. In other words: Savage-2-0-0-0-branch doesn't work with kernel module of savage of main cvs and/or of savage-snapshot. thanks -- Sérgio M. B. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56alloc_id438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA
Hi, I thought I read earlier in the week that the Savage driver moved to the trunk and the console corruption problem had been fixed. I pulled the source via CVS and recompiled but I still have my consoles all showing corrupted text. Did I miss something in compiling? -- George Lengel (Worm) Kohli head. You could have been lava bones. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage driver in DRI/MESA
--- George Lengel [EMAIL PROTECTED] wrote: Hi, I thought I read earlier in the week that the Savage driver moved to the trunk and the console corruption problem had been fixed. I pulled the source via CVS and recompiled but I still have my consoles all showing corrupted text. Did I miss something in compiling? I don't show any corruption on the savages I have access to (IX, savage4). What chip are you running on? Did you follow the instructions here: http://dri.sourceforge.net/cgi-bin/moin.cgi/Building Alex __ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
