Hi Ian, to upload the new site you have to tar it up, then do the following:
scp tarball.tar.gz [EMAIL PROTECTED]:/home/groups/d/dr/dri/htdocs/ Then login to dri.sf.net with ssh and your SF user id and untar the site into a temporary directory. Make sure its 'chmod a+r'. Cheers, - Frank On Sun, 2002-06-23 at 01:37, [EMAIL PROTECTED] wrote: > Send Dri-devel mailing list submissions to > [EMAIL PROTECTED] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/dri-devel > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Dri-devel digest..." > > > Today's Topics: > > 1. Re: radeon cvs problem (Keith Whitwell) > 2. Re: radeon cvs problem (Dieter =?iso-8859-1?q?N=FCtzel?=) > 3. radeon-20020621 install problem ([EMAIL PROTECTED]) > 4. Radeon driver problem ... X dont satart! (thork) > 5. website. (Ian Molton) > 6. Re: website. (Jens Owen) > 7. Re: How to trace switching to software rendering (Michael Schlueter) > 8. Re: radeon drivers (tcl vs. non-tcl) (Zilvinas Valinskas) > 9. Re: radeon drivers (tcl vs. non-tcl) (Zilvinas Valinskas) > 10. Re: radeon cvs problem ([EMAIL PROTECTED]) > 11. Mini HOWTO get extra ~30 fps with gears ... (Zilvinas Valinskas) > > --__--__-- > > Message: 1 > Date: Sat, 22 Jun 2002 20:41:33 +0100 > From: Keith Whitwell <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > CC: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: [Dri-devel] radeon cvs problem > > [EMAIL PROTECTED] wrote: > >>If you're running XFree86 4.1, > >> > > > > No, I'm running 4.2. Yesterday I bit the bullet and downloaded the > > entire source tree (quite an adventure down a phone line ...) and > > built from source. All worked fine this time, so there perhaps some > > problem with the binary packages on SF? Perhaps there's a dependence > > on an X11R6 module not included in the binary package? > > > > Anyhow, so now I have the radeon cvs built and working correctly, > > everything's wonderful (thanks to all the developers!) apart from an > > assertion failure I get repeatedly with our 3D ultrasound application > > (http://svr-www.eng.cam.ac.k/~rwp/stradx). It happens whenever I open > > a new window and make the new context current: > > > > radeon_vtxfmt.c:1039: radeonVtxfmtUnbindContext: Assertion `vb.context == ctx' >failed. > > > > It doesn't happen with _every_ context switch, just with a particular > > pair of windows in the application - but it is repeatable with these > > two windows. The problem goes away with RADEON_NO_TCL=1 or > > RADEON_NO_VTXFMT=1, and doesn't appear with any other GL > > implementation we've tried (including mga dri). > > > > I'd be happy to test patches if anyone's interested in this one .... > > This is interesting. The code to cope with multiple contexts there hasn't had > a huge amount of testing. If I download your code, how can I exercise this > problem? > > Keith > > > > > > > --__--__-- > > Message: 2 > From: Dieter =?iso-8859-1?q?N=FCtzel?= <[EMAIL PROTECTED]> > Organization: DN > To: Keith Whitwell <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > Subject: Re: [Dri-devel] radeon cvs problem > Date: Sat, 22 Jun 2002 21:55:15 +0200 > Cc: [EMAIL PROTECTED], > [EMAIL PROTECTED] > > > --------------Boundary-00=_30I4O4PKY8I7MKG15FFO > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: 8bit > > On Saturday 22 June 2002 21:41, Keith Whitwell wrote: > > [EMAIL PROTECTED] wrote: > > >>If you're running XFree86 4.1, > > > > > > No, I'm running 4.2. Yesterday I bit the bullet and downloaded the > > > entire source tree (quite an adventure down a phone line ...) and > > > built from source. All worked fine this time, so there perhaps some > > > problem with the binary packages on SF? Perhaps there's a dependence > > > on an X11R6 module not included in the binary package? > > > > > > Anyhow, so now I have the radeon cvs built and working correctly, > > > everything's wonderful (thanks to all the developers!) apart from an > > > assertion failure I get repeatedly with our 3D ultrasound application > > > (http://svr-www.eng.cam.ac.k/~rwp/stradx). It happens whenever I open > > > a new window and make the new context current: > > > > > > radeon_vtxfmt.c:1039: radeonVtxfmtUnbindContext: Assertion `vb.context == > > > ctx' failed. > > > > > > It doesn't happen with _every_ context switch, just with a particular > > > pair of windows in the application - but it is repeatable with these > > > two windows. The problem goes away with RADEON_NO_TCL=1 or > > > RADEON_NO_VTXFMT=1, and doesn't appear with any other GL > > > implementation we've tried (including mga dri). > > > > > > I'd be happy to test patches if anyone's interested in this one .... > > > > This is interesting. The code to cope with multiple contexts there hasn't > > had a huge amount of testing. If I download your code, how can I exercise > > this problem? > > What about the "cxbug.c" test posted here, lately? > > With the tdfx driver I get this with mode #5: > > Mesa/demos> ./cxbug 5 > X Error of failed request: BadMatch (invalid parameter attributes) > Major opcode of failed request: 144 (GLX) > Minor opcode of failed request: 10 (X_GLXCopyContext) > Serial number of failed request: 37 > Current serial number in output stream: 38 > > Manywin show bad textures with s >= 2 > > Mesa/xdemos> ./wincopy > glXMakeContextCurrent failed in Redraw() > glXMakeContextCurrent failed in Redraw() > glXMakeContextCurrent failed in Redraw() > glXMakeContextCurrent failed in Redraw() > glXMakeContextCurrent failed in Redraw() > [snip] > > -Dieter > > -- > Dieter N�tzel > Graduate Student, Computer Science > > University of Hamburg > Department of Computer Science > @home: [EMAIL PROTECTED] > > --------------Boundary-00=_30I4O4PKY8I7MKG15FFO > Content-Type: application/x-bzip2; > name="cxbug.c.bz2" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; filename="cxbug.c.bz2" > > QlpoOTFBWSZTWR7MNgkAAnXfgEgwWf//Xz//386/7//uYAdfe2e8ru7zzteq67t09s9CQdtrvZ8J > JJJ6ZGKabSNNqBk9Q0eoA00Bo0GjENABKJpNMQ1U/E1MTJqNBoPU00AyDagAABoNASnppRgRskaN > ANANAZAAAAGgSIRENUD1D1NGmagNAADIMmgaAABw00wQyGmmRkwgGmgDCaNMmABA0EiRARiNJp6E > 0myRqeKaYm0hoYgNNA9RhGmhJIoQkZviMwJLmY3MgDUMBttkoD/qhENExRN6FBZgU23MDcWZMq6X > MWlev55jLOQsirgSHiSLPQkA8JEqGBDDiQMLHR3+3QwwdhmPaMZAFPHiT/yVlPu5KO/+4+Wy1Gvy > 6gHY/iOQhwPzdgTRIkw/qsL2Fzvxxw5e+c/5lMDl+KwX+GkCyDAFyo6pCmlNU5oAIDmlqM0UJZGy > i6QbOCkV1XOlnduVpa4DHAVEVaUYq9+myDY1ThpWRvrwks8nN9nIZnoz4NjbB4OVLjll+7DKPayn > JHqpllpUqi06DJvM4kYhFK+Wdt8FV37XGUZxpqtG04pYMt8QKFmEGesLb3bAU0VPY6QpSdFLK7Wa > A4StrUBo1Z5YyWoEqrCjiZqULrERFSjgek1X2WnYMk898p1rm0TBdAZTWgv6Xj2G2II3MKivdBYf > UEzrrCjk3luZQrB6QaqgQTVIhAWLEe/jMC21FMFdj3QUitIDreuGAkL42jWXGWLbBlBEYzxWz7di > 1+uW1Ot146t1sTQNjbG2mNJR2YS45IzaHrwHtlpYx63CabEpXXn3P7ZvvSMcdXVy5HTrpJmL66G8 > 6BaKjhQSEujVYB35xITssE4ttfZkRlLEypOfHo/msRNvMHUTpq5Rb+sX8n0IqbDafhMluTJTO2gg > n6j8egJ0QDdCOOUbmTIzhygqGMimxys7W5+oKtGLiU2QBhhEzSgofEcPJkZvK7+jh0glTpgPTl1S > DqZa27GFTcboxF5hsDJOEF1KxaA8V93B8cyoxvC+cbk/QfAqO5dxScTMfeysOIzK0mUbpjgkNEgh > BWMLglgN/IIyg4eHBKF/EZioVGVAMxZQO7WppuB+9rmDPQHv7yMOcpZhuqJI8zpaXKYZCtGVjPOe > rnUuMECZonxmre2GCA5oIRTB6VFiPYixJWNrissTUgzllE9KrM2sNv2zFsFz5YcoOnmmYrjDcbA8 > 0MzsYwuENQm5PZRbQkec+vyhKkZIJobd5wOUrZmeVf6Zxbv1hUF5h5npMPovB+DHBxRh/UXQi5jr > sOBIDxgMbzGYTTVpI7uAqZeuJyTusSBg+pCb0oqDsXmMCInDBYwD0bHJuUenvVbnMt0VFy6UpWNI > NAMPdyqtFa6qENikqwYxpqzYl/vUalQUF9ZEh2wJFtySMqQ1JHuSdONmbnagjKhVa0SExRhfjAjD > BGcJaCqVDwLGAYkIoJioB6IRTNY0G1xbTUEfJg7iMOBMtdEvcGG20QvfaSq8BXNOUiRgy2QfIWNV > Ri+BCDzjNr2ei69zF/A0I2i/Q9owkSWrSBmJDCXHnfIK0c50MRnOpaw+LAQRiwiAZgCrpxiZamLc > S6E56fWhKutR2ypJwp7NFfdvL2keCq/xNRwfCJa9YOhVHCFnNJ0DMMQDtSo2SFrSGjffudns5ryb > bxzbu7VSatUMgpVb7DLyGfbtabMusetFG3H7igN+mMmMYUoTaQUjDpaXbIjoFibnrfps3670DkXP > xLwpZ7cTdmwy0oe+6KDlrKjZthVy0Fz9xAm2DAMYqkikrC3zkXKQLMlkvVKRgCc3qyKzQ1JhTGmi > aEQRdjtiyFHofKMJVaNZ8ooewMhqKyrBFoygp1tQ0NNNoj7FFcyLwpZnKGdxvuNGihFgYzaptlbh > 5zcjS0ihlrDIDWwPV2XcvsZnKSdxwwdpqLy5AqlN1sGMhjINZKTJELv4a1UHWVKkZPaldgTmEjMU > jCOzOGGARSRIisK8ouWUlAOCMiESwBGsZs+FHURWuShsyTKFwwWsBoU4p4WOHSehZSjRlom8tjCx > aAxMUi0Nw++/MdpMbkB7zIrA8h4OhA/GoK65xngp0YRVRAyhrodnfG4YMGlCQYmJUKIMK5BmFiRT > xe7UAtrPQQiErBkEYYrQmwyFekitXby2kCTnKVKmmF5FgIectKI+hiSFFr5EzQQeIX1gWolx0bS4 > yarsFeatFsg1KQ6YSyDLeJyKmNny2ptGJBi7nTpi1K0GCZsRJm9pqAsYDaAkNciHSJ7ZCLhcl6hJ > Fuqn4SgcoYhVVo8LD4gwyvU4l/F3JFOFCQHsw2CQ > > --------------Boundary-00=_30I4O4PKY8I7MKG15FFO-- > > > > --__--__-- > > Message: 3 > From: [EMAIL PROTECTED] > Date: Sat, 22 Jun 2002 15:14:53 -0500 > To: [EMAIL PROTECTED] > Reply-To: [EMAIL PROTECTED] > Subject: [Dri-devel] radeon-20020621 install problem > > Hoping I get a driver that works with my all-in-wonder 7500 card, I > downloaded > > radeon-20020621-linux.i386.tar > > but running ./install.sh exited with an error; dri.log is included > at the end of my message. > > My system: > > # cat /etc/redhat-release > Red Hat Linux release 7.3 (Valhalla) > > # rpm -q XFree86 kernel > XFree86-4.2.0-8 > kernel-2.4.18-5 > > Thx for any help; please note that I set the reply-to to > > [EMAIL PROTECTED] > > since I am not subscribed, > > Mate > -- > --- > Mate Wierdl | Dept. of Math. Sciences | University of Memphis > > cc -O2 -Wall -Wwrite-strings -Wpointer-arith -Wcast-align -Wstrict-prototypes >-Wnested-externs -Wpointer-arith -D__KERNEL__ -DMODULE -fomit-frame-pointer >-DEXPORT_SYMTAB -I0 -c radeon_drv.c -o radeon_drv.o > In file included from /usr/include/linux/module.h:20, > from drmP.h:43, > from radeon_drv.c:32: > /usr/include/linux/modversions.h:1:2: #error Modules should never use kernel-headers >system headers, > /usr/include/linux/modversions.h:2:2: #error but rather headers from an appropriate >kernel-source package. > /usr/include/linux/modversions.h:3:2: #error Change -I/usr/src/linux/include (or >similar) to > /usr/include/linux/modversions.h:4:2: #error -I/lib/modules/$(uname -r)/build/include > /usr/include/linux/modversions.h:5:2: #error to build against the currently-running >kernel. > In file included from /usr/include/linux/timex.h:152, > from /usr/include/linux/sched.h:14, > from /usr/include/linux/mm.h:4, > from /usr/include/linux/locks.h:5, > from /usr/include/linux/devfs_fs_kernel.h:6, > from /usr/include/linux/miscdevice.h:4, > from drmP.h:45, > from radeon_drv.c:32: > /usr/include/asm/timex.h:10:21: asm/msr.h: No such file or directory > In file included from /usr/include/linux/pagemap.h:15, > from /usr/include/linux/locks.h:8, > from /usr/include/linux/devfs_fs_kernel.h:6, > from /usr/include/linux/miscdevice.h:4, > from drmP.h:45, > from radeon_drv.c:32: > /usr/include/asm/pgtable.h:17:24: asm/fixmap.h: No such file or directory > In file included from /usr/include/linux/highmem.h:5, > from /usr/include/linux/pagemap.h:16, > from /usr/include/linux/locks.h:8, > from /usr/include/linux/devfs_fs_kernel.h:6, > from /usr/include/linux/miscdevice.h:4, > from drmP.h:45, > from radeon_drv.c:32: > /usr/include/asm/pgalloc.h:6:24: asm/fixmap.h: No such file or directory > In file included from radeon_drv.c:32: > drmP.h:61:25: asm/uaccess.h: No such file or directory > In file included from drm_dma.h:35, > from radeon_drv.c:85: > /usr/include/linux/interrupt.h:44:25: asm/hardirq.h: No such file or directory > /usr/include/linux/interrupt.h:45:25: asm/softirq.h: No such file or directory > make: *** [radeon_drv.o] Error 1 > > > --__--__-- > > Message: 4 > From: thork <[EMAIL PROTECTED]> > To: DRI-devel post <[EMAIL PROTECTED]> > Date: 22 Jun 2002 16:59:30 -0400 > Subject: [Dri-devel] Radeon driver problem ... X dont satart! > > Hi everybody!! > maybe this is not the right question for this list but ... > well here goes: > > I was using the radeon driver wich came with this package > radeon-20020525-linux.i386.tar.bz2, it was working right ... > well not too much right, just 400FPS on glxgears when some > peple say they get 1000FPS and more, well it was working > for me anyway and I have to thank your for the great job > you ar doing ... > well the thing is I've updated to > radeon-20020621-linux.i386.tar.bz2 > and X cant start, everything goes right until well, the last > lines of the log hehe :P > well these are some outputs: > > dmesg | grep agp: > agpgart: Maximum main memory to use for agp memory: 203M > agpgart: Detected Via Apollo Pro KT266 chipset > agpgart: AGP aperture is 64M @ 0xf8000000 > > dmesg | grep drm: > [drm] AGP 0.99 on VIA Apollo KT133 @ 0xf8000000 64MB > [drm] Initialized radeon 1.3.1 20020611 on minor 0 > > tail Xfree.icantrememberwhat.log: > (==) RADEON(0): Write-combining range (0xf0000000,0x4000000) > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 6, (OK) > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 6, (OK) > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 6, (OK) > > Fatal server error: > Caught signal 11. Server aborting > > does anybody know what can it be?? > > THANKS TO ALL OF YOU!!!, there is people at the end > of the world who like what you are doing! > if you look for Punta Arenas, Chile, my city you will > see :) > > Bye! > > thork > > > > > > --__--__-- > > Message: 5 > Date: Sat, 22 Jun 2002 22:39:20 +0100 > From: Ian Molton <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Organization: The Dragon Roost > Subject: [Dri-devel] website. > > Hey. > > I want to get started putting up the new site, but no-one has told me > how to access the webspace... > > I've given my sourceforge details and been added to the project... > > > --__--__-- > > Message: 6 > Date: Sat, 22 Jun 2002 15:38:12 -0600 > From: Jens Owen <[EMAIL PROTECTED]> > To: Ian Molton <[EMAIL PROTECTED]> > CC: [EMAIL PROTECTED] > Subject: Re: [Dri-devel] website. > > Ian Molton wrote: > > > > Hey. > > > > I want to get started putting up the new site, but no-one has told me > > how to access the webspace... > > > > I've given my sourceforge details and been added to the project... > > Ian, > > I can't help you with access details, but I'd like you to stage this > below the current main site until we've all had a chance to look at the > new format and get familiar with it. > > I use the current site quite a bit, and this would ease any transition > for me. > > Thanks, > Jens > > -- /\ > Jens Owen / \/\ _ > [EMAIL PROTECTED] / \ \ \ Steamboat Springs, Colorado > > > --__--__-- > > Message: 7 > Subject: Re: [Dri-devel] How to trace switching to software rendering > From: Michael Schlueter <[EMAIL PROTECTED]> > To: Jens Owen <[EMAIL PROTECTED]> > Cc: Brian Paul <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > Date: 23 Jun 2002 01:01:47 +0200 > > Am Sam, 2002-06-22 um 20.45 schrieb Jens Owen: > > Michael Schlueter wrote: > > > Hi Paul, > > His first name is Brian :-) > > Ups, sorry for that. > > > > So I've to do some printf into os-support/linux/drm/xf86drm.c to find > > > that problem first (or is that a known issure?). > > > > Make sure your DRM driver is recompiled for your kernel. Best to use > > the DRM driver in the DRI source tree. cd to > > xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel and make > > -f Makefile.linux > > yes, I did that and the install script of the precompiled did that also. > > After inclunding a few printf into > xc/programs/Xserver/hw/xfree86/os-support/linux/drmxf86drm.c and then > including a few more lines it crashed on a different spot. So I think > there is some wrong with my system and I have to take a deeper look into > it. > > Bye, Michael > > > > --__--__-- > > Message: 8 > From: Zilvinas Valinskas <[EMAIL PROTECTED]> > Date: Sun, 23 Jun 2002 02:01:26 -0400 > To: Jens Owen <[EMAIL PROTECTED]> > Cc: Zilvinas Valinskas <[EMAIL PROTECTED]>, > dri-devel <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > Subject: Re: [Dri-devel] radeon drivers (tcl vs. non-tcl) > > On Sat, Jun 22, 2002 at 08:15:30AM -0600, Jens Owen wrote: > > Zilvinas, > > > > Thanks for posting this data. It's nice to see confirmation of how > > things were intended to work. > > > > No problem Jens :)) I am glad you have found those results usefull ;) > > > -- /\ > > Jens Owen / \/\ _ > > [EMAIL PROTECTED] / \ \ \ Steamboat Springs, Colorado > > > > > > ------------------------------------------------------- > > Sponsored by: > > ThinkGeek at http://www.ThinkGeek.com/ > > _______________________________________________ > > Dri-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/dri-devel > > -- > Zilvinas Valinskas > > > --__--__-- > > Message: 9 > From: Zilvinas Valinskas <[EMAIL PROTECTED]> > Date: Sun, 23 Jun 2002 02:31:27 -0400 > To: Dieter N?tzel <[EMAIL PROTECTED]> > Cc: dri-devel <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > Subject: Re: [Dri-devel] radeon drivers (tcl vs. non-tcl) > > On Sat, Jun 22, 2002 at 04:57:49PM +0200, Dieter N?tzel wrote: > > On Saturday 22 June 2002 16:15, Jens Owen wrote: > > > Zilvinas, > > > > > > Thanks for posting this data. It's nice to see confirmation of how > > > things were intended to work. > > > > I'll second that. > > May I ask if Zilvinas could repeat with 60Hz? > > I know that this is a "bad number" but the RAMDAC clock has some influence. > > Most "official" benchmarks (Win) are made @60 Hz... > > Ok if there is a interest :) in that data I see no problem ;) I will do > that in a nearest future ;) I am wondering myself what (if any) > difference that would make ;) > > > > > Second: > > My dual Athlon MP 1900+ (MSI K7D Master-L, AMD 760MPX) with 512MB DDR-SDRAM (1 > > GB is comming soon) is up and running. > 512MB RAM > ABit KT7A-RAID (KT133A chipset) > Single CPU (sighs. ...) Athlon XP 1800+ SDRAM (PC133). > Radeon 7200 (QD model which is VIVO DDR 64MB ... another name for that.) > > > > > I can get my hands on a Radeon 8500 and maybe a 7500, tomorrow or Monday. > > I'll do some viewperf-6.1.2 numbers on my V5 5500 @24 bit tonight. > > I assume that these runs are done on Radeon (or it is V5 5500 ?) > > > > > Mesa/demos> ./gloss > > 596 frames in 5.006 seconds = 119.057 FPS <-- cylinder > > 764 frames in 5.003 seconds = 152.708 FPS > > 760 frames in 5.006 seconds = 151.818 FPS > > 758 frames in 5.001 seconds = 151.57 FPS > > > > 483 frames in 5.004 seconds = 96.5228 FPS > > 420 frames in 5.003 seconds = 83.9496 FPS > > 420 frames in 5 seconds = 84 FPS > > 421 frames in 5.008 seconds = 84.0655 FPS <-- teapot > That's very interesting ... > > $ ./gloss > radeonUpdatePageFlipping allow 1 current 0 > radeonUpdatePageFlipping allow 1 current 0 > 1485 frames in 5.001 seconds = 296.941 FPS <- cylinder > 1501 frames in 5 seconds = 300.2 FPS > 1496 frames in 5.003 seconds = 299.021 FPS > 1494 frames in 5.001 seconds = 298.74 FPS > 1501 frames in 5 seconds = 300.2 FPS > 1501 frames in 5.002 seconds = 300.08 FPS > radeonUpdatePageFlipping allow 1 current 0 > radeonUpdatePageFlipping allow 1 current 1 > 1150 frames in 5.013 seconds = 229.404 FPS <-- teapot > 146 frames in 5.017 seconds = 29.1011 FPS > 147 frames in 5.027 seconds = 29.2421 FPS > 146 frames in 5.011 seconds = 29.1359 FPS > 146 frames in 5 seconds = 29.2 FPS > 147 frames in 5.029 seconds = 29.2305 FPS > 146 frames in 5.018 seconds = 29.0953 FPS > 146 frames in 5.003 seconds = 29.1825 FPS > > there is a guite a difference here. > > Teapot is very slow ;) compared with your results :) > > > > > ipers is running @20-22 fps (~580.000 Poly/sec) > > 532771.7 (poly.sec) @19 - 20.60 fps .... > (not much slower ...) > > and here is isosurf ;) benchmark > $ ./isosurf > 7179 vertices, 7177 triangles > radeonUpdatePageFlipping allow 1 current 0 > Nr unique vertex/normal pairs: 2723 > num_tri_verts: 21531 > primitive (0x10000): GL_TRIANGLE_STRIP, > render style (0x100): glVertex, > enabling normal arrays > new flags (0xa93169): glVertex, GL_TRIANGLE_STRIP, lit, > radeonUpdatePageFlipping allow 1 current 0 > radeon_makeX86Normal3fv/195 CVAL 0 OFFSET 14 VAL 405dece0 > radeon_makeX86Normal3fv/196 CVAL 4 OFFSET 20 VAL 405dece4 > radeon_makeX86Normal3fv/197 CVAL 8 OFFSET 25 VAL 405dece8 > radeon_makeX86Normal3fv done > radeonUpdatePageFlipping allow 1 current 1 > Benchmarking... > Result: triangles/sec: 4.4483e+06 fps: 619.8 > Benchmarking... > Result: triangles/sec: 4.44974e+06 fps: 620 > Benchmarking... > Result: triangles/sec: 4.45172e+06 fps: 620.276 > Benchmarking... > Result: triangles/sec: 4.44974e+06 fps: 620 > > > If my memory serves me right - last time I've tried it was much slower > (well it was almost a have a year ago if not even more ;) T&L ? made > guite an improvement.) > > > > Desktop resolution is 1280x1024@24 as always ;-) > > Same here. > > > > We need the Mesa (p)thread stuff badly 'cause all numbers are from single > > theard/process mode (the second CPU was all the time 100% idle). > > > > Cheers, > > Dieter > > > > -- > > Dieter N?tzel > > Graduate Student, Computer Science > > > > University of Hamburg > > Department of Computer Science > > @home: [EMAIL PROTECTED] > > -- > Zilvinas Valinskas > > > --__--__-- > > Message: 10 > From: [EMAIL PROTECTED] > Date: Sun, 23 Jun 2002 09:12:08 +0100 > To: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: [Dri-devel] radeon cvs problem > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] > > Dear Keith - > > > This is interesting. The code to cope with multiple contexts there > > hasn't had a huge amount of testing. If I download your code, how > > can I exercise this problem? > > Thanks for offering to look at this. Here's how to reproduce the > problem. First download the i386 executable from: > > http://svr-www.eng.cam.ac.uk/~rwp/stradx/installing_stradx_lnx.html > > Should work out of box, though you'll need a libXm.so.1 from Lesstif > (included in most recent linux distros, but not older ones). > > Start stradx, then open the "Image correlation" window from the > "Calibration" menu, then open the "Segmentation controls" window from > the "Segmentation" menu. That's when I get the assertion > failure. Poking around in the source, the assertion failure happens in > the call to GLwDrawingAreaMakeCurrent (aka glxMakeCurrent) when the > second window is initialising. > > Anyone got any idea what's wrong with the SF binaries? I suspect there > would be much more useful testing of the CVS drivers if the binaries > worked! > > Cheers, > > Andrew > > > > > > > > --__--__-- > > Message: 11 > From: Zilvinas Valinskas <[EMAIL PROTECTED]> > Date: Sun, 23 Jun 2002 04:36:29 -0400 > To: [EMAIL PROTECTED] > Subject: [Dri-devel] Mini HOWTO get extra ~30 fps with gears ... > > Hello, > > I was playing with gears today (again) and this what I've noticed : > > $ gears > radeonUpdatePageFlipping allow 1 current 0 > (gears runs in the upper left corner ...) > 5310 frames in 5.0 seconds = 1062.000 FPS > 6488 frames in 5.0 seconds = 1297.600 FPS > 6496 frames in 5.0 seconds = 1299.200 FPS > 6490 frames in 5.0 seconds = 1298.000 FPS > 6486 frames in 5.0 seconds = 1297.200 FPS > 6498 frames in 5.0 seconds = 1299.600 FPS > radeonUpdatePageFlipping allow 1 current 0 > (now I move window to the center of the screen ;) ... ) > 5537 frames in 5.0 seconds = 1107.400 FPS > 6657 frames in 5.0 seconds = 1331.400 FPS > 6658 frames in 5.0 seconds = 1331.600 FPS > 6661 frames in 5.0 seconds = 1332.200 FPS > 6658 frames in 5.0 seconds = 1331.600 FPS > 6660 frames in 5.0 seconds = 1332.000 FPS > > and here we go ... extra 30fps :))))) Weird ;) ... > > If we follow the same 'instructions' with q3demo ;) how many extra fps > can we go faster now ? (LOL, the problem is q3demo runs fullscreen ... ;) > this trick won't work ;)) > > DRI Trunk (062002) xfree 4.2 > Radeon QD > linux kernel 2.4.18 (vanilla) > 512MB RAM, Athlon XP 1800+ > > -- > Zilvinas Valinskas > > > > --__--__-- > > _______________________________________________ > Dri-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dri-devel > > > End of Dri-devel Digest ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
