[Dri-devel] Your buglist for The XFree86 Project's Bugzilla needs attention.
[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 them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the Reassign bug to owner of selected component option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Just use the Accept bug command. To get a list of all NEW bugs, you can use this URL (bookmark it if you like!): http://bugs.xfree86.org//cgi-bin/bugzilla/buglist.cgi?bug_status=NEW[EMAIL PROTECTED] Or, you can use the general query page, at http://bugs.xfree86.org//cgi-bin/bugzilla/query.cgi. Appended below are the individual URLs to get to all of your NEW bugs that haven't been touched for a week or more. You will get this message once a day until you've dealt with these bugs! http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=25 http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=62 http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=78 http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=98 http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=118 http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=131 http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=185 http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=271 http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=314 http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=344 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] disabling debugging from binaries?
There are many places in code like: if (R200_DEBUG DEBUG_PRIMS) but I don't see how to disable debugging at all from binaries. Should not these ifs be in: #ifdef DEBUG #endif ? It's always few CPU cycles less... -- Free Software - find interesting programs and change them NetHack - meet interesting creatures, kill them and eat their bodies Usenet - meet interesting people from all over the world and flame them Decopter - unrealistic helicopter simulator, get it from http://decopter.sf.net --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Xi Graphics claiming we ...lack skill.... XFree and ATI, too.
Some numbers: http://www.xig.com/Pages/Atop/Summit-Linux-vsWindows.html http://www.xig.com/Pages/Atop/SummitBenchmarks-CARDS.html Regards, Dieter --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Error compiling - DRI Driver Installation
After I see this: Compiling... ERROR: Kernel modules did not compile I get the following in dri.log, when I try sh install.sh make -f Makefile.linux DRM_MODULES=radeon.o modulesmake[1]: Entering directory `/home/john/dripkg/drm'make -C /lib/modules/2.4.20-8/build SUBDIRS=`pwd` DRMSRCDIR=`pwd` modulesmake[2]: Entering directory `/usr/src/linux-2.4.20-8'make -r -f tmp_include_depends allmake[3]: Entering directory `/usr/src/linux-2.4.20-8'touch: creating `/usr/src/build/231485-i386/install/usr/src/linux-2.4.20-8/fs/jfs/jfs_debug.h': No such file or directorymake[3]: *** [/usr/src/build/231485-i386/install/usr/src/linux-2.4.20-8/fs/jfs/jfs_debug.h] Error 1make[3]: Leaving directory `/usr/src/linux-2.4.20-8'make[2]: *** [tmp_include_depends] Error 2make[2]: Leaving directory `/usr/src/linux-2.4.20-8'make[1]: *** [modules] Error 2make[1]: Leaving directory `/home/john/dripkg/drm'make: *** [radeon.o] Error 2 I have RedHat 9 and an ATI Radeon 64MB DDR VIVO. Yes, I do have the kernel source installed. --John
[Dri-devel] When is next XFree86 merger
Reason I ask is, DRI (xc cvs) no-longer supports myRadeon 9000 PCI (withor without DRI enabled), but did 6-8 months) ago. XFree86 (xc cvs) doeshave2D support for it atleast, although a little too brightly. The issue is with the DDC not being detected in DRI but it is in XFree86. Even setting the DCC mode in the config doesn't work. This results in DRI's 2D driver setting lower horizontal and vertical sync rates for the monitorand ignores the ones in the config, and eventually failing because the modes in the config don't match up for the sync rates it tries to use. The same config works for XFree86 xc cvs.
Re: [Dri-devel] disabling debugging from binaries?
On Sun, 2003-06-29 at 15:51, Jacek Popawski wrote: There are many places in code like: if (R200_DEBUG DEBUG_PRIMS) but I don't see how to disable debugging at all from binaries. Should not these ifs be in: #ifdef DEBUG #endif ? It's always few CPU cycles less... It should be easy to make the existing tests compile time and measure the difference. I doubt it's significant. -- Earthling Michel Dnzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] disabling debugging from binaries?
On Sunday 29 June 2003 07:51 am, Jacek Popawski wrote: There are many places in code like: if (R200_DEBUG DEBUG_PRIMS) but I don't see how to disable debugging at all from binaries. Should not these ifs be in: Just: #define R200_DEBUG 0 #define DEBUG_PRIMS 0 The compiler should optimize out the dead code. --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Only normal DRI and Mesa CVS access asdeveloper, now?
José Fonseca wrote: On Sat, Jun 28, 2003 at 04:18:15PM +0200, Dieter Nützel wrote: Mesa3d seems to be affected, too. No mesa CVS update for 10 days, now ;-( My DRI CVS is 12 days old... No chance from old Europe anymore? I've just checked and the tarballs in http://cvs.sourceforge.net/cvstarballs/projectname-cvsroot.tar.gz for DRI and Mesa3d are just as old as the anonymous CVS server, and from the SF documents there is no other way to directly access the repository (except contact the SF team, but you can't put that in a cron job, can you? ;-) Basically this means that CVS mirroring is impossible and the only solution to the current problem is to move the repository elsewhere. Is there a solid alternative to sourceforge? One with better backing that will keep it going if large numbers of projects start using it? I don't know why the silence from the DRI SF project admins - I'm CC'ing to them now (at least those currently in the active) in the hope to hear what they have to say about this. Not so much silence as a lack of answers... I remind again that this issue should be presented to the SF team to know what's their position and what to expect from the future. This issue [of the unreliable CVS anonymous serving] together with the recent news of closing inactive and old projects may well be a sign that SF is saturating again, but this time the saturation appears to be fought not by further investment, but degrading the quality of the services. If true then it's a matter of time to collapse, or at least be unusable for big projects such as DRI. This is a reasonable proposition -- let's start putting a draft together, then. --- SF admins, We're concerned about the recent changes to anonymous cvs access, in particular the way in which changes committed by developers take an extended period (upto days) to become visible to anonymous cvs users. As we rely heavily on a test/debug/fix cycle that includes input and interaction from anonymous cvs users, this delay represents a real roadblock for our development efforts. Can you outline the reasons that this has started happening, whether it will be resolved and if so on what timescale? DRI project developers Keith Whitwell ... --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] disabling debugging from binaries?
On Sun, Jun 29, 2003 at 03:43:43PM -0600, Nicholas Leippe wrote: Just: #define R200_DEBUG 0 #define DEBUG_PRIMS 0 The compiler should optimize out the dead code. Right, and I was wrong, there is way to disable it. In r200_context.h: #define DO_DEBUG1 #if DO_DEBUG extern int R200_DEBUG; #else #define R200_DEBUG 0 #endif -- Free Software - find interesting programs and change them NetHack - meet interesting creatures, kill them and eat their bodies Usenet - meet interesting people from all over the world and flame them Decopter - unrealistic helicopter simulator, get it from http://decopter.sf.net --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Only normal DRI and Mesa CVS access =?iso-8859-15?q?as developer?=, now?
On Sun, Jun 29, 2003 at 11:04:47PM +0100, Keith Whitwell wrote: José Fonseca wrote: On Sat, Jun 28, 2003 at 04:18:15PM +0200, Dieter Nützel wrote: Mesa3d seems to be affected, too. No mesa CVS update for 10 days, now ;-( My DRI CVS is 12 days old... No chance from old Europe anymore? I've just checked and the tarballs in http://cvs.sourceforge.net/cvstarballs/projectname-cvsroot.tar.gz for DRI and Mesa3d are just as old as the anonymous CVS server, and from the SF documents there is no other way to directly access the repository (except contact the SF team, but you can't put that in a cron job, can you? ;-) Basically this means that CVS mirroring is impossible and the only solution to the current problem is to move the repository elsewhere. Is there a solid alternative to sourceforge? One with better backing that will keep it going if large numbers of projects start using it? I don't know why the silence from the DRI SF project admins - I'm CC'ing to them now (at least those currently in the active) in the hope to hear what they have to say about this. Not so much silence as a lack of answers... I remind again that this issue should be presented to the SF team to know what's their position and what to expect from the future. This issue [of the unreliable CVS anonymous serving] together with the recent news of closing inactive and old projects may well be a sign that SF is saturating again, but this time the saturation appears to be fought not by further investment, but degrading the quality of the services. If true then it's a matter of time to collapse, or at least be unusable for big projects such as DRI. This is a reasonable proposition -- let's start putting a draft together, then. --- SF admins, We're concerned about the recent changes to anonymous cvs access, in particular the way in which changes committed by developers take an extended period (upto days) to become visible to anonymous cvs users. As we rely heavily on a test/debug/fix cycle that includes input and interaction from anonymous cvs users, this delay represents a real roadblock for our development efforts. Can you outline the reasons that this has started happening, whether it will be resolved and if so on what timescale? Reading the SF master bug database, the only workaround for this problem is to create nightly CVS snapshots of the trunk for people to download who are not members of the project. That's the SF admins response on the master bug database for now anyway. Alan. --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Building from Savage-1_0_0-branch
and virge too possibly :) Speaking of which if anyone wants a virge board for testing/porting, I've got an old GX (and possibly a DX as well) sitting around. Alex --- Ian Romanick [EMAIL PROTECTED] wrote: 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 will be to do all three (even if the SiS driver doesn't get any testing) at the same time. I think the people that did the original 3.4-to-4.x conversion have long since forgotten what was done. That was before I even joined the project! :) --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
