[Dri-devel] Good Afternoon dri-devel, Free Money Secrets Revealed! jqvf
NO Selling! You make money 24/7 through our simple turnkey system You start earning money quickly! And you get paid over and over for work you've already done! Great support and training! Dear dri-devel, By now you've probably seen every opportunity on earth maybe even beyond. Everywhere from infomercialls on television to your E-mail box. But you will notice they all try to sell you something that makes them money on the backend. Do you notice when you go to the book store and you try to find great material on Internet Marketing, Website Design or the Internet in general there is nothing good. You ask why? The answer is simple everything changes so fast on the Internet there is not enough time to print it fast enough to make the information reliable and valuable. But that has changed now, whether you're interest is Internet Marketing, Website Design, Making Money or the Internet in general (for new users). We have put together the BEST Internet Package ever seen! If you're reading this message and think it is another "Junk E-mail" think again because you will never see another E-mail like this again. I will show you a copy of my bank statements showing my daily deposits totalling over $4,559.13 for the last week in February. And how others have learned much more from our on-line training course than any book or magazine in a bookstore. Also how others have used it as a business opportunity after learning from it to make $1,000's of dollars weekly, legitimately! Ok, You Got My Attention. Show Me The Details! "As a single mom, having a system like this is so important to me. Now, I can spend quality time with my son, and still work the business, focusing only on those activities that will increase my income, my lifestyle, and my sense of security" Delina Villa "The most affordable, doable business on the net! Thanks to this system, I now own a million dollar business that pays me regardless of whether I wake up and go work in the morning, or not!." William Smith "Three years ago I was waiting tables to make ends meet while I went to school part-time. Now I earn $10,000/month working just a couple hours a day." Tim Howsden To be Removed from our Opt-In mailing list. Simply Click Remove. Your email address to be immediately removed. +,~wzf¢+,¦ì¢·o$áyyézW(ëhç¤ æ¯zxm¶ÿ¶§Ê&þÇî'^½éfj)b b²ÐëׯzYb²Û,¢êÜyú+éÞ¶m¦Ïÿ+-²Ê.Ç¢¸ ë+-³ùb²Ø§~Ý®'^½é
Re: [Dri-devel] Mesa 4.1 branch
Brian Paul wrote: [...] I did some testing with the mesa-4-1-branch today on my r200. Compiling was less trouble than I expected, everything was pretty much straight forward ;-) > > I'd appreciate it if people could start testing this branch, esp the > drivers I haven't tested. One thing in particular to check is the > Mesa/demos/readpix program - make sure front/back buffer rendering is > working. That's something that I've had to change in all the drivers. > I don't know what exactly readpix is supposed to do, but I think it works fine. Switching between front and backbuffer doesn't affect the displayed pictures. The benchmark result is: Benchmarking... Result: 325 reads in 4.009000 seconds = 2956697.430781 pixels/sec My experiences from testing: Wolfenstein (single-player): works, about same speed as dri-trunk, but not completely stable (exited with Signal 4 in one run, and Signal 11 in another, and once I got a complete lockup of the system) Q3A: stable (at least for the time I tested), but not very fast. In fact it shows the same symptoms I got with earlier versions of DRI-trunk (before around 2002-10-11): poor overall speed, and a framerate that maxes out at 50 FPS. Is the r200-code in your branch from before that date? If yes, that would explain the behaviour. small stuff like gl-screensavers, mesa-demos seems to run fine one more thing: If I disable hardware-TCL (R200_NO_TCL=1), then some GL-apps won't start ( Signal 8 / FPE ). At least q3a, wolfsp and gears are affected, probably others too. Disabling hw-TCL does work with current trunk-code for me. My system is a AMD 1800+ on a KT266A-mobo, with a Radeon 8500 QL, linux-2.4.19, agpmode is set to 1, page-flipping is enabled [...] > -Brian > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mesa 4.1 branch
Stefan Lange wrote: > Brian Paul wrote: > > [...] > > I did some testing with the mesa-4-1-branch today on my r200. Compiling > was less trouble than I expected, everything was pretty much straight > forward ;-) > >> >> I'd appreciate it if people could start testing this branch, esp the >> drivers I haven't tested. One thing in particular to check is the >> Mesa/demos/readpix program - make sure front/back buffer rendering is >> working. That's something that I've had to change in all the drivers. >> > > I don't know what exactly readpix is supposed to do, but I think it > works fine. Switching between front and backbuffer doesn't affect the > displayed pictures. The benchmark result is: > > Benchmarking... > Result: 325 reads in 4.009000 seconds = 2956697.430781 pixels/sec If you saw the images in both front and back-buffer mode it's OK. A blank window would indicate a problem. > My experiences from testing: > > Wolfenstein (single-player): works, about same speed as dri-trunk, but > not completely stable (exited with Signal 4 in one run, and Signal 11 in > another, and once I got a complete lockup of the system) > > Q3A: stable (at least for the time I tested), but not very fast. In fact > it shows the same symptoms I got with earlier versions of DRI-trunk > (before around 2002-10-11): poor overall speed, and a framerate that > maxes out at 50 FPS. Is the r200-code in your branch from before that > date? If yes, that would explain the behaviour. I made the branch on Oct 9. I'll do a merge from the trunk in a bit. Hopefully that'll clear up the speed problem. > small stuff like gl-screensavers, mesa-demos seems to run fine > > one more thing: If I disable hardware-TCL (R200_NO_TCL=1), then some > GL-apps won't start ( Signal 8 / FPE ). At least q3a, wolfsp and gears > are affected, probably others too. Disabling hw-TCL does work with > current trunk-code for me. I'll test this after updating from the trunk. > My system is a AMD 1800+ on a KT266A-mobo, with a Radeon 8500 QL, > linux-2.4.19, agpmode is set to 1, page-flipping is enabled Thanks! -Brian --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mesa 4.1 branch
On Tue, 2002-10-15 at 10:01, Stefan Lange wrote: > Q3A: stable (at least for the time I tested), but not very fast. In fact > it shows the same symptoms I got with earlier versions of DRI-trunk > (before around 2002-10-11): poor overall speed, and a framerate that > maxes out at 50 FPS. Is the r200-code in your branch from before that > date? If yes, that would explain the behaviour. This speed problem is somehow related to displaying the players weapon, or status. If you are playing q3a, and switch to free fly mode, the fps jumps to around 100-250fps --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mesa 4.1 branch
Russ Dill wrote: > On Tue, 2002-10-15 at 10:01, Stefan Lange wrote: > > >>Q3A: stable (at least for the time I tested), but not very fast. In fact >>it shows the same symptoms I got with earlier versions of DRI-trunk >>(before around 2002-10-11): poor overall speed, and a framerate that >>maxes out at 50 FPS. Is the r200-code in your branch from before that >>date? If yes, that would explain the behaviour. >> > > This speed problem is somehow related to displaying the players weapon, > or status. If you are playing q3a, and switch to free fly mode, the fps > jumps to around 100-250fps That makes sense. The speed problem comes from agressively throttling glClear() operations. Q3 does multiple clears of the backbuffer for drawing the little floating head and I don't know what else in the status bar. So, I expect the speed to go up after a trunk merge. Keith --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Backing store on Radeon?
Warning: ignorant questions on the way... I've gotten some questions from a couple of people about backing store with DRI, on the R100 driver specifically. Because my background isn't firmly rooted in X-Windows, I wasn't really familiar with what that meant. :) I did a little searching, and I think I have a vauge idea now. In any case, as near as I can tell, when the Radeon DRI driver gets loaded, backing store is explicitly disabled. Why is that? Is it a hardware limitation or is it "just" to conserve memory? Something else? -- Smile! http://antwrp.gsfc.nasa.gov/apod/ap990315.html --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mesa 4.1 branch
Keith Whitwell wrote: > Russ Dill wrote: > >> On Tue, 2002-10-15 at 10:01, Stefan Lange wrote: >> >> >>> Q3A: stable (at least for the time I tested), but not very fast. In >>> fact it shows the same symptoms I got with earlier versions of >>> DRI-trunk (before around 2002-10-11): poor overall speed, and a >>> framerate that maxes out at 50 FPS. Is the r200-code in your branch >>> from before that date? If yes, that would explain the behaviour. >>> >> >> This speed problem is somehow related to displaying the players weapon, >> or status. If you are playing q3a, and switch to free fly mode, the fps >> jumps to around 100-250fps > > > That makes sense. The speed problem comes from agressively throttling > glClear() operations. Q3 does multiple clears of the backbuffer for > drawing the little floating head and I don't know what else in the > status bar. So, I expect the speed to go up after a trunk merge. > I just checked, that's exactly the case: With "cg_drawStatus 0" I'll get >50 FPS also with pre-October-11 code. It seems like those "on-screen-display" things are indeed causing this effect. Drawing or not drawing the gun doesn't make a change for me, however. > Keith > > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mesa 4.1 branch
Brian Paul wrote: > Stefan Lange wrote: > >> My experiences from testing: >> >> Wolfenstein (single-player): works, about same speed as dri-trunk, but >> not completely stable (exited with Signal 4 in one run, and Signal 11 >> in another, and once I got a complete lockup of the system) >> >> Q3A: stable (at least for the time I tested), but not very fast. In >> fact it shows the same symptoms I got with earlier versions of >> DRI-trunk (before around 2002-10-11): poor overall speed, and a >> framerate that maxes out at 50 FPS. Is the r200-code in your branch >> from before that date? If yes, that would explain the behaviour. > > I made the branch on Oct 9. I'll do a merge from the trunk in a bit. > Hopefully that'll clear up the speed problem. The merge is done. >> small stuff like gl-screensavers, mesa-demos seems to run fine >> >> one more thing: If I disable hardware-TCL (R200_NO_TCL=1), then some >> GL-apps won't start ( Signal 8 / FPE ). At least q3a, wolfsp and gears >> are affected, probably others too. Disabling hw-TCL does work with >> current trunk-code for me. > > > I'll test this after updating from the trunk. Setting R200_NO_TCL works for me - no signals or FP exceptions. However, with R200_NO_TCL I'm seeing some flashing/missing textures in RTCW. -Brian --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mesa 4.1 branch
Brian Paul wrote: > Brian Paul wrote: > >> Stefan Lange wrote: >> >>> My experiences from testing: >>> >>> Wolfenstein (single-player): works, about same speed as dri-trunk, >>> but not completely stable (exited with Signal 4 in one run, and >>> Signal 11 in another, and once I got a complete lockup of the system) >>> >>> Q3A: stable (at least for the time I tested), but not very fast. In >>> fact it shows the same symptoms I got with earlier versions of >>> DRI-trunk (before around 2002-10-11): poor overall speed, and a >>> framerate that maxes out at 50 FPS. Is the r200-code in your branch >>> from before that date? If yes, that would explain the behaviour. >> >> >> I made the branch on Oct 9. I'll do a merge from the trunk in a bit. >> Hopefully that'll clear up the speed problem. > > > The merge is done. > OK, so I just updated from CVS and recompiled. as expected: the speed problem in q3a is solved ;-) > >>> small stuff like gl-screensavers, mesa-demos seems to run fine >>> >>> one more thing: If I disable hardware-TCL (R200_NO_TCL=1), then some >>> GL-apps won't start ( Signal 8 / FPE ). At least q3a, wolfsp and >>> gears are affected, probably others too. Disabling hw-TCL does work >>> with current trunk-code for me. >> >> >> >> I'll test this after updating from the trunk. > > > Setting R200_NO_TCL works for me - no signals or FP exceptions. > However, with R200_NO_TCL I'm seeing some flashing/missing textures > in RTCW. > hmm, that's odd. I still get floating point exceptions for almost every GL-app. with TCL disabled. Demos that _do_ work with TCL disabled include: clearspd, drawpix, gamma, glinfo, lodbias, readpix, winpos Maybe this can give you a clue, why some are working and some aren't? Could I have messed something up during checking out/compiling/installing that is causing these FPE's? I attached the output of glxinfo, in case that's any helpful. Regards, and thanks for your quick help and patience, Stefan > -Brian > > glxinfo.bz2 Description: Binary data
Re: [Dri-devel] Mesa 4.1 branch
Stefan Lange wrote: > Brian Paul wrote: >> >> The merge is done. >> > > OK, so I just updated from CVS and recompiled. > as expected: the speed problem in q3a is solved ;-) Great. >> Setting R200_NO_TCL works for me - no signals or FP exceptions. >> However, with R200_NO_TCL I'm seeing some flashing/missing textures >> in RTCW. >> > > > hmm, that's odd. I still get floating point exceptions for almost every > GL-app. with TCL disabled. > > Demos that _do_ work with TCL disabled include: > clearspd, drawpix, gamma, glinfo, lodbias, readpix, winpos > > Maybe this can give you a clue, why some are working and some aren't? > > Could I have messed something up during checking > out/compiling/installing that is causing these FPE's? Can you run with gdb and find where the FP exception is happening? -Brian --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mesa 4.1 branch
> hmm, that's odd. I still get floating point exceptions for almost every > GL-app. with TCL disabled. > > Demos that _do_ work with TCL disabled include: > clearspd, drawpix, gamma, glinfo, lodbias, readpix, winpos > > Maybe this can give you a clue, why some are working and some aren't? > > Could I have messed something up during checking > out/compiling/installing that is causing these FPE's? Try running under gdb & posting a strack trace. Note that there will be an initial fpe during sse detection -- this is normal and you have to hit 'c' to continue past it. Keith --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Backing store on Radeon?
On Die, 2002-10-15 at 20:30, Ian Romanick wrote: > Warning: ignorant questions on the way... > > I've gotten some questions from a couple of people about backing store with > DRI, on the R100 driver specifically. Because my background isn't firmly > rooted in X-Windows, I wasn't really familiar with what that meant. :) I > did a little searching, and I think I have a vauge idea now. > > In any case, as near as I can tell, when the Radeon DRI driver gets loaded, > backing store is explicitly disabled. Why is that? Is it a hardware > limitation or is it "just" to conserve memory? Something else? I was going to guess something like 'because there can't be backing store for direct rendered windows?', but are you actually sure about this? I just started a server with DRI enabled and +bs, and both the log and xdpyinfo indicated that backing store was enabled. If you have more questions about backing store, you should probably post to Xpert. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] r200 and libxaa
I've seen ppl mention the libxaa.a from Fonseca seems to fix the problem with the screen blanking. Thing is I can't seem to find this libxaa.. Can anyone point me in the right direction for this? And can anyone confirm that this does seem to fix the screen blanking problem with the Radeon 8500. --- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
