You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
(25) |
Apr
(38) |
May
(9) |
Jun
(39) |
Jul
(64) |
Aug
(73) |
Sep
(86) |
Oct
(91) |
Nov
(112) |
Dec
(90) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(158) |
Feb
(178) |
Mar
(305) |
Apr
(269) |
May
(302) |
Jun
(126) |
Jul
(171) |
Aug
(143) |
Sep
(146) |
Oct
(96) |
Nov
(105) |
Dec
(100) |
2002 |
Jan
(112) |
Feb
(50) |
Mar
(91) |
Apr
(88) |
May
(99) |
Jun
(217) |
Jul
(95) |
Aug
(129) |
Sep
(107) |
Oct
(283) |
Nov
(261) |
Dec
(153) |
2003 |
Jan
(203) |
Feb
(129) |
Mar
(125) |
Apr
(159) |
May
(120) |
Jun
(165) |
Jul
(185) |
Aug
(181) |
Sep
(149) |
Oct
(165) |
Nov
(199) |
Dec
(165) |
2004 |
Jan
(121) |
Feb
(155) |
Mar
(246) |
Apr
(132) |
May
(113) |
Jun
(59) |
Jul
(146) |
Aug
(58) |
Sep
(96) |
Oct
(150) |
Nov
(143) |
Dec
(66) |
2005 |
Jan
(194) |
Feb
(193) |
Mar
(127) |
Apr
(53) |
May
(74) |
Jun
(43) |
Jul
(45) |
Aug
(83) |
Sep
(72) |
Oct
(74) |
Nov
(103) |
Dec
(79) |
2006 |
Jan
(129) |
Feb
(116) |
Mar
(124) |
Apr
(97) |
May
(44) |
Jun
(48) |
Jul
(22) |
Aug
(38) |
Sep
(23) |
Oct
(68) |
Nov
(62) |
Dec
(41) |
2007 |
Jan
(41) |
Feb
(27) |
Mar
(22) |
Apr
(19) |
May
(17) |
Jun
(11) |
Jul
(5) |
Aug
(6) |
Sep
(13) |
Oct
(21) |
Nov
(13) |
Dec
(18) |
2008 |
Jan
(25) |
Feb
(7) |
Mar
(19) |
Apr
|
May
(12) |
Jun
(12) |
Jul
(3) |
Aug
(14) |
Sep
(5) |
Oct
|
Nov
(5) |
Dec
(4) |
2009 |
Jan
|
Feb
(4) |
Mar
|
Apr
(2) |
May
(2) |
Jun
(3) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(7) |
2010 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
From: Christoph H. <hal...@gm...> - 2000-06-08 19:26:05
|
An answer to your second question: The DGA mouse support seems to be broken in XFree86 4.0 I heard that in various newsgroups. They also told me, that that will be fixed in Xfree86 4.0.1, the next version. There's currently no fix out. Don't you think that 46 fps is enough? In fact, your eye cannot see if there are 24 or 46 fps ----- Original Message ----- From: <de...@ze...> To: "DRI problemy" <dri...@li...> Sent: Thursday, June 08, 2000 10:53 AM Subject: [Dri-users] quake3 > Hi. Two Quaestions. > 1. Why does quake3 run so slowly (maybe not slowly, but at weak performance: 46 frames per second is not much). > At the same graphics settings it worked with 60 fps (it was Glide2x with Mesa3.2and Voodoo 3) > 2. Why can't I enable DGA ? Without DGA-mouse in quake3 there is no sense to play (if anyone played, then he knows what i am talking) > > > _______________________________________________ > Dri-users mailing list > Dri...@li... > http://lists.sourceforge.net/mailman/listinfo/dri-users > |
From: <de...@ze...> - 2000-06-08 14:56:03
|
Hi. Two Quaestions. 1. Why does quake3 run so slowly (maybe not slowly, but at weak performance: 46 frames per second is not much). At the same graphics settings it worked with 60 fps (it was Glide2x with Mesa3.2and Voodoo 3) 2. Why can't I enable DGA ? Without DGA-mouse in quake3 there is no sense to play (if anyone played, then he knows what i am talking) |
From: Adam \teferi\ G. <te...@pf...> - 2000-06-08 01:51:36
|
Finally got it working - all I had to do was rebuild X. One question, though - anyone have any idea when the mga_dri driver will su= pport higher color depths than 16bpp? On Wed, Jun 07, 2000 at 08:11:13PM -0400, Adam teferi Glasgall wrote: > glxinfo tells me dri is not enabled. > I am definitely using the correct libGL. >=20 > On Wed, Jun 07, 2000 at 10:59:53AM +0200, marco ghidinelli wrote: > > On Tue, Jun 06, 2000 at 10:11:23PM -0400, Adam teferi Glasgall wrote: > > > Well, I finally got the modules to compile. > > > However, although I have mga.o loaded and mga_dri.so in the right pla= ce (/usr/X211R6.4/lib/modules/dri, for me), and have followed all the instr= uctions in the DRI User's Guide and the Compilation Guide, I still can't ge= t DRI to work - xdpyinfo doesn't even report the XFree86-DRI extension. > > > Any advice? > > >=20 > > > --=20 > > > -teferi > > > <Adam Glasgall> > >=20 > > try the glxinfo program from dri.sourceforge.net/resources/resources.ht= ml > >=20 > > are you sure that you are using the correct libGL?? > > bye! > >=20 > > --=20 > > minds are like parachutes... they work best when open. >=20 > --=20 > -teferi > <Adam Glasgall> --=20 -teferi <Adam Glasgall> |
From: Adam \teferi\ G. <te...@pf...> - 2000-06-08 00:14:10
|
glxinfo tells me dri is not enabled. I am definitely using the correct libGL. On Wed, Jun 07, 2000 at 10:59:53AM +0200, marco ghidinelli wrote: > On Tue, Jun 06, 2000 at 10:11:23PM -0400, Adam teferi Glasgall wrote: > > Well, I finally got the modules to compile. > > However, although I have mga.o loaded and mga_dri.so in the right place= (/usr/X211R6.4/lib/modules/dri, for me), and have followed all the instruc= tions in the DRI User's Guide and the Compilation Guide, I still can't get = DRI to work - xdpyinfo doesn't even report the XFree86-DRI extension. > > Any advice? > >=20 > > --=20 > > -teferi > > <Adam Glasgall> >=20 > try the glxinfo program from dri.sourceforge.net/resources/resources.html >=20 > are you sure that you are using the correct libGL?? > bye! >=20 > --=20 > minds are like parachutes... they work best when open. --=20 -teferi <Adam Glasgall> |
From: marco g. <ma...@at...> - 2000-06-07 21:39:19
|
On Wed, Jun 07, 2000 at 01:56:22AM +0200, de...@ze... wrote: > Hi > I've got a lame question I think, but I read FAQ and didn't find anything. > I've got Voodoo 3 and XFree4 with tdfx installed and it works, but i can't run xscreensaver GL demos correctly. > Everything works in a window mode, but with -root switch it runs, but screen is blinking or it goes extremly slow. Why doesn't it work fine in a fullscreen ? > try to download the glxinfo program from http://dri.sourceforge.net/resources/resources.html and look if you are running in Indirect rendering mode... -- minds are like parachutes... they work best when open. |
From: Adam \teferi\ G. <te...@pf...> - 2000-06-07 02:14:14
|
Well, I finally got the modules to compile. However, although I have mga.o loaded and mga_dri.so in the right place (/u= sr/X211R6.4/lib/modules/dri, for me), and have followed all the instruction= s in the DRI User's Guide and the Compilation Guide, I still can't get DRI = to work - xdpyinfo doesn't even report the XFree86-DRI extension. Any advice? --=20 -teferi <Adam Glasgall> |
From: <de...@ze...> - 2000-06-06 23:58:59
|
Hi I've got a lame question I think, but I read FAQ and didn't find anything. I've got Voodoo 3 and XFree4 with tdfx installed and it works, but i can't run xscreensaver GL demos correctly. Everything works in a window mode, but with -root switch it runs, but screen is blinking or it goes extremly slow. Why doesn't it work fine in a fullscreen ? deresz<at>polsl.gliwice.pl |
From: <al...@sg...> - 2000-06-06 22:59:00
|
Hi dri-users, Since a number of you use Performer atop the DRI for 3D development or simply as a DRI testing platform, I hope you won't mind a very brief commercial message: We've just released a new version (Performer 2.3.1) updated for XFree86 4.0 and the latest Mesa versions. Here's the release announcement with links to the download site: http://reality.sgi.com/performer/mongoose-2.3.1.html We're particularly interested in hearing if you come across any problems using 2.3.1 with the latest DRI bits. If so, mail us at: mon...@co..., or post to dri-devel or dri-users as appropriate (we're subscribed to both). Thanks, Allan ---- Allan Schaffer al...@sg... Silicon Graphics http://reality.sgi.com/allan |
From: Tasslehof <fa...@ur...> - 2000-06-05 11:11:37
|
Hi. A week ago I installed XFree 4.0 and upgraded kernel to 2.3.99-pre3. Everything is well, except for DRI support. I mean : X startup is OK (No error || warning found in log messages), /proc/dri/0 is there etc... I have installed glide V3 (DRI) v 3.10.6 and double-checked every symbolic link... Anyway, starting pure OGL applications (NO glut or else) - as xmms spectrum analyzer applet and some code I wrote using only glx support) - produces this error message (I have LIBGL_DEBUG on) : libGL error: dlopen failed: /usr/X11R6/lib/modules/dri/tdfx_dri.so: undefined symbol: _glapi_Context . What's wrong ? Is the "tdfx_dri" module ? I have run ldconfig and checked it doesn't mess up things : it's al OK, symbolic links are OK and ldd says tdfx_dri is linked against libglide3.so.3 (which is there !) and my apps are all linked against /usr/X11R6/lib/libGL.so.1 ... What in the hell can I do ? Thanx in advance, |~~~~~~| |(O> |\ Fabio Cavaliere (Homebrew apprentice & GLUG member) |//\ | | e-mail > fa...@ur... |V_/_ | | e-mail2 > cav...@se... |######|- GLUG on the Web : http://genova.linux.it +------+ |
From: Adam \teferi\ G. <te...@pf...> - 2000-06-03 20:36:17
|
Well, that solved part of the problem - I'm only getting the parse errors f= rom /usr/src/linux/include/asm/spinlock.h now... Still doesn't compile, though. On Sat, Jun 03, 2000 at 03:00:31PM +0200, Evaldas Darcianovas wrote: >=20 > Again and again this happens. You should add > "-I/usr/src/linux/include" to your compile options. >=20 >=20 > On Fri, 2 Jun 2000, Adam "teferi" Glasgall wrote: >=20 > > My system is running Debian Linux woody (glibc 2.1), kernel 2.4.0-test1= , XFree86 4.0. My video card is a Matrox G400 MAX. > > The problem is that I can't build the kernel module for mga DRI. Whethe= r through make World or make -f Makefile.linux in build/xc/programs/Xserver= /hw/xfree86/os-support/linux/drm/kernel, I get several screensful of parse = errors, in /usr/include/asm/pci.h, /usr/include/asm/spinlock.h, /usr/includ= e/linux/spinlock.h, drm.h, and drmP.h > >=20 > > Anyone have any idea how to fix this? I'd really love to take full adva= ntage of this great card... > >=20 > > --=20 > > -teferi > > <Adam Glasgall> > >=20 >=20 >=20 > _______________________________________________ > Dri-users mailing list > Dri...@li... > http://lists.sourceforge.net/mailman/listinfo/dri-users --=20 -teferi lord of the plane. or not. <Adam Glasgall> |
From: Evaldas D. <ev...@so...> - 2000-06-03 13:03:33
|
Again and again this happens. You should add "-I/usr/src/linux/include" to your compile options. On Fri, 2 Jun 2000, Adam "teferi" Glasgall wrote: > My system is running Debian Linux woody (glibc 2.1), kernel 2.4.0-test1, XFree86 4.0. My video card is a Matrox G400 MAX. > The problem is that I can't build the kernel module for mga DRI. Whether through make World or make -f Makefile.linux in build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel, I get several screensful of parse errors, in /usr/include/asm/pci.h, /usr/include/asm/spinlock.h, /usr/include/linux/spinlock.h, drm.h, and drmP.h > > Anyone have any idea how to fix this? I'd really love to take full advantage of this great card... > > -- > -teferi > <Adam Glasgall> > |
From: Adam \teferi\ G. <te...@pf...> - 2000-06-03 01:27:42
|
My system is running Debian Linux woody (glibc 2.1), kernel 2.4.0-test1, XF= ree86 4.0. My video card is a Matrox G400 MAX. The problem is that I can't build the kernel module for mga DRI. Whether th= rough make World or make -f Makefile.linux in build/xc/programs/Xserver/hw/= xfree86/os-support/linux/drm/kernel, I get several screensful of parse erro= rs, in /usr/include/asm/pci.h, /usr/include/asm/spinlock.h, /usr/include/li= nux/spinlock.h, drm.h, and drmP.h Anyone have any idea how to fix this? I'd really love to take full advantag= e of this great card... --=20 -teferi <Adam Glasgall> |
From: Emil O. <em...@mi...> - 2000-05-22 00:38:21
|
Hello, I tried compiling and running the X server for my G400 as described the howto. Everything seemed to compile fine, but when I ran it, the server was ridiculously slow. I ran dmesg and found the following: [drm:mga_dma_quiescent] *ERROR* irqs: 0 wanted 0 [drm:mga_dma_quiescent] *ERROR* lockup This message appeared many times. Is this a bug in the driver or do I have configuration issues? (BTW, I'm running 2.3.99-pre8 with a G400 and I didn't see any other errors; all the modules seemed to load just fine. I tried before with 2.3.99-pre5 and got the same problems.) Thanks, Emil |
From: Hermann 'm. G. <mr...@gm...> - 2000-05-19 15:19:26
|
hello > 2 seperate XServers work fine :0 and :1 :-O how do you start this ?? :-) > > which leads me to question2: > > if you have managed to get Xfree 4 up and running in dual headed mode, > could you please sendd me your (hardware) configuration ? i am using the binary disrtibution from the xfree ftp server and redhat 6.1 voodoo2 banshee agp + a matrox mill. 1 pci with only the voodoo2, the server dies every day, now, with the second card, he is up for 10 days :-) my xfree86config-file: http://members.aon.at/mrq1/xfree.txt mfg mrq1 -- linux 2.2.15 on a dual pentium iii 500 384mb 5:00pm up 14 days, 3:10, 1 user, load average: 2.07, 2.06, 2.02 |
From: Gerhard d. H. <ge...@ja...> - 2000-05-19 09:58:25
|
Im havign a massive amount of problems getting dual head up and running on XFree 4 (even before getting into DRI stuff). Q1: Is there a mailinglist for XF4 specific questions ? Anyway, some of my findings: (2.3.51 machine is my main machine, Suse6.2 w/ 2.3.51 kernel, XFree 4 from source (and Xfree 4 with DRI stuff from a few weeks ago) XF4s -> XFree 4, compiled from source XF4r -> XFree 4, from Susue 6.4 CD rpm G200 AGP/Voodoo3/2.3.51/XF4s -> works fine G200 AGP/Voodoo3/2.2.14/XF4r -> XServer crashed on dual head 2 seperate XServers work fine :0 and :1 G400 AGP/Voodoo3 -> freezes the machine hard G400 AGP in a machine with a voodoo3 PCI card running single headed on the G400 freezes the machine half .. I can telnet in and do stuff, but when I type reboot nothing happens G400 AGP/G200 -> as above Also tried all this on a redhat 6.2 box with XFree4 from source G400 AGP/G200 -> as above G400 AGP/Voodoo 3 -> as above After sticking in a second card Redhats auto hardware detection (kudzu i think it's called) got confused .. sax2,the new suse x configurator didn't work either .. which leads me to question2: if you have managed to get Xfree 4 up and running in dual headed mode, could you please sendd me your (hardware) configuration ? Thanks Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O In Italy, for thirty years under the Borgias, they had warfare, =`\<, terror, murder and bloodshed, but they produced Michelangelo, (=)/(=) Leonardo da Vinci, and the Renaissance. In Switzerland they had brotherly love, they had five hundred years of democracy and peace, and what did they produce? The cuckoo clock. |
From: Gerhard d. H. <ge...@ja...> - 2000-05-18 12:00:09
|
I've installed a nnew linux box (AGP/G400, 3dfsx voodoo3 3000 installed a clean Suse 6.4 on itm installed the unsorted Xfre86 (sand Sax2) rpms tried to startx -- /usr/X11R6/bin/XFree86 and it dies on me with [snip] (--) MGA(1): Display dimensions: (32, 24) cm (--) MGA(1): DPI set to (101, 108) Symbol strlen from module /usr/X11R6/lib/modules/libddc.a is unresolved! (II) Loading /usr/X11R6/lib/modules/librac.a (II) Module rac: vendor="The XFree86 Project" compiled for 4.0, module version = 1.0.0 (==) TDFX(0): Write-combining range (0xde000000,0x2000000) (II) TDFX(0): Textures Memory 7.93 MB This should not happen! An unresolved function was called! Fatal server error: Any ideas ? Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) gde...@ja... POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam "TeamWare" for finding Oil & Gas...The Smart Way The Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message. |
From: Honza S. <ran...@nu...> - 2000-05-16 14:11:56
|
Is there any way (except with two matrox cards) to have dual hw accelerated displays on linux? I prefer DRI, but some other appoach would also work for me. From the achive I found that dual voodoo 3 does not work because there is some problem in the main server code. Anyone knows a fix for this problem? Honza |
From: marco g. <ma...@at...> - 2000-05-06 16:44:32
|
On Fri, May 05, 2000 at 05:41:48PM +0200, Morten Brix Pedersen wrote: > Hi, > > I use kernel 2.2.15, patched with the utah-glx agpgart module. > I tried compiling DRI with the instructions on the DRI compilation page, but it > doesn't make the "mga.o" kernel driver. you obtain compilation errors or what? |
From: Morten B. P. <mo...@re...> - 2000-05-05 15:41:44
|
Hi, I use kernel 2.2.15, patched with the utah-glx agpgart module. I tried compiling DRI with the instructions on the DRI compilation page, but it doesn't make the "mga.o" kernel driver. Can anyone help me with this? Morten. -- http://loststar.wiktor.dk/ "The nice thing about Windows is - It does not just crash, it displays a dialog box and lets you press 'OK' first." - Arno Schaefer |
From: Jeff H. <jha...@pr...> - 2000-05-02 15:20:38
|
Evaldas Darcianovas wrote: > > Hello > > Here goes the problem. I'm owner of i810-dc100 video chipset, updating > CVS mga-0-0-3 branch every day but never succeed to enable DRI :-) > Line 161 in programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/i810_dma.c > gives compile error about VM_DONTCOPY undefined: > vma->vm_flags |= (VM_IO | VM_DONTCOPY); > > I tried VM_LOCKED or VM_DENYWRITE instead of VM_DONTCOPY.. Don't know if > the following error on ./XFree86 is related to these changes: > > (0): [drm] created "i810" driver at busid "PCI:0:1:0" > (0): [drm] added 4096 byte SAREA at 0xc3545000 > (0): [drm] mapped SAREA 0xc3545000 to 0x40014000 > (0): [drm] framebuffer handle = 0xd0000000 > (0): [drm] added 1 reserved context for kernel > (II) I810(0): [drm] Registers = 0xd6000000 > (II) I810(0): GART: Found 4096K Z buffer memory > (II) I810(0): Bound backbuffer memory > (II) I810(0): GART: Allocated 4K for mouse cursor image > (II) I810(0): Allocated Scratch Memory > Not enough memory for dma buffers > > Any hints please? Kernel version is 2.3.99-pre5 with agpgart module and > dri disabled, distribution debian slink. > > Sincerely, > Evaldas Darcianovas > > _______________________________________________ > Dri-devel mailing list > Dri...@li... > http://lists.sourceforge.net/mailman/listinfo/dri-devel You need kernel 2.3.99-pre6 or higher. -Jeff |
From: Evaldas D. <ev...@so...> - 2000-05-02 10:18:08
|
Hello Here goes the problem. I'm owner of i810-dc100 video chipset, updating CVS mga-0-0-3 branch every day but never succeed to enable DRI :-) Line 161 in programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/i810_dma.c gives compile error about VM_DONTCOPY undefined: vma->vm_flags |= (VM_IO | VM_DONTCOPY); I tried VM_LOCKED or VM_DENYWRITE instead of VM_DONTCOPY.. Don't know if the following error on ./XFree86 is related to these changes: (0): [drm] created "i810" driver at busid "PCI:0:1:0" (0): [drm] added 4096 byte SAREA at 0xc3545000 (0): [drm] mapped SAREA 0xc3545000 to 0x40014000 (0): [drm] framebuffer handle = 0xd0000000 (0): [drm] added 1 reserved context for kernel (II) I810(0): [drm] Registers = 0xd6000000 (II) I810(0): GART: Found 4096K Z buffer memory (II) I810(0): Bound backbuffer memory (II) I810(0): GART: Allocated 4K for mouse cursor image (II) I810(0): Allocated Scratch Memory Not enough memory for dma buffers Any hints please? Kernel version is 2.3.99-pre5 with agpgart module and dri disabled, distribution debian slink. Sincerely, Evaldas Darcianovas |
From: Nicholas V. <vi...@pa...> - 2000-04-30 04:42:44
|
OK, here's one for you zealots out there. As I have a very little amount of space on my HD (1.5 gigs, including swap partitions), I combined: -- Linux Kernel 2.3.51 -- the tdfx_drm code off of linux.3dfx.com (needed because 2.3.51 seems to have something broken in the module code... an inability to find tdfx_create and tdfx_destroy, I believe... or something like that) -- the latest Glide version 3 -- XFree86 4.0, the standard release which should have yielded DRI.... it does (glxinfo reports "yes"), but: -- gears crashes -- SDL applications sometimes run as accelerated, sometimes not Anybody ever heard of anybody trying this before? I am loathe to upgrade my way up to 2.3.99-pre5, as my net connection sucks... this seems to "semi" work, and I'm wondering if anybody has actually tried this mad juryrigging before with any more success. System is an AMD K62-500, 64 MB RAM, Voodoo3 3000 AGP, running the aforementioned software. Cheers, Nicholas |
From: <tl...@se...> - 2000-04-26 21:52:50
|
Hello, all. I recently reinstalled my box with a new distribution, and when I did, I broke my 3dfx XFCOM installation. I posted in the 3dfx private newsgroup, and they suggested that I ask the DRI people for help, and so here I am. It looks like a silly mistake on my part, and so if someone could just give me a tip or two, I should be able to take care of the problem. I posted my problem to the support forum on the sourceforge web site, but since mine was the only posting, I thought that I would mention it here to see if I could get some kind soul to take a look at and hopefully respond to my post. You can find it at: http://sourceforge.net/support/?func=detailsupport&support_id=101273&group_id=387 TIA. -- Todd Lewis tl...@se... |
From: Georg S. <ste...@ea...> - 2000-04-26 06:45:01
|
On Mon, Apr 17, 2000 at 09:02:00AM +0200, Rémy Baudet wrote: > I want to buy a graphic card and I need good hardware acceleration and a > lot of texture memory (64Mo or more). > So, what's the best card for OpenGL under Linux, what about the Elsa > Gloria II (based on nVidia Quadro) ? > > Remy. > Content-Description: Card for Rémy Baudet At the moment nVidia is no good, because they haven't released their specs. I am not sure how good the G400 driver is. I use an Voodoo3 2000, but that has only 16MB and only small textures...but that will change with the Voodoo4 and you can be quite sure that the Voodoo4 will be supported by DRI. Georg -- main(O){10<putchar(5^(O<0?-(++O):--O)?75-((7&19700>>3*abs(O))^(O<0?-1:0)):10)&&(2&abs(O)+1?main(-(2+abs(O))):main(2+abs(O)));} ------------------------------------------------------------------------------ | Georg Steffers | | EMail: ste...@in... | ------------------------------------------------------------------------------ -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/O d- s:+>: a- C+++>++++ UL/I+++$ !P--- L+++>++++ !E--- W+>+++ N++ o? K? w--- O M- V-- PS+ PE++ Y+ PGP>+ t++ 5++ x- R tv+ b+++ DI+ D+ G>++ e* h! r- y+ ------END GEEK CODE BLOCK------ |
From: Georg S. <ste...@ea...> - 2000-04-26 06:35:42
|
On Tue, Apr 25, 2000 at 09:23:42PM +0200, Gerhard den Hollander wrote: > fROm Randall Hopper (on Mon, Apr 17, 2000 at 03:56:18PM -0400): > > >|> From: Georg Steffers <ste...@ea...> > >|> for hardware acceleration of 3D i think you need direct access to the > >|> Hardware the OGL lib is written for and not only communication over the > >|> X-Protocol (only a guess, perhaps someone can correct me...). > >| > >|I've been doing this ever since Utah GLZ was released. > >| > >|You can run GLx aware programs on an SGI, and display on a Linux box, and > >|get accelerated performance , because the GLX protocol is hardware > >|accelerated .. > > > I think you might have misspoken. There is no hardware acceleration > > inherent in the protocol itself AFAIK. > > I might not have been totally clear .., > an example I've seen with our own software > If I have a large 2D section (basically a huge set of textures, > that is too large to fit in one screen, so I get a window, with a part f > the section, and sliders/scrollbars to scroll through it) > running remotely from Sun to Linux box, the linux box caches the textures > in the hardware and you can rapidly scroll. > Running from Sun to Sun (or from SGI to SGI) the textures are not cached > locally and scrolling means that the enwly exposed area of the screen has > to be Xferred over the network > > > >|if you run remotely from 1 SGi box to another you will get no > >|acceleration .. > > > Are you kidding? :-) Or is there some specific app you're talking about? > > See above .. > > Also, try running any of the xscreensaver GLhacks locally vs remote, > locally you get the full GL acceleration, running remotely it's slow as > mollases in februari. > > > > Randall > > > > Gerhard, (@jasongeo.com) == The Acoustic Motorbiker == > -- > __O This isn't just a dream! > =`\<, Yes it is, it's only just a dream, > (=)/(=) Life is just a dream, > Life is just. > > > _______________________________________________ > Dri-users mailing list > Dri...@li... > http://lists.sourceforge.net/mailman/listinfo/dri-users Hi, as i understand it the protocol sends well defined requests to the server and then its up to the server how he handles the request, so i think there might be some hardware-acceleration with OpenGL-Apps running remotely, depends on what the server understands and how it handles the requests. So i was definetly mistaken with my above statement that you need direct hardware-access. But there seem to be a lot of difficulties in practice that slows down a remote running GL-app...probably programming mistakes within that apps. Georg -- main(O){10<putchar(5^(O<0?-(++O):--O)?75-((7&19700>>3*abs(O))^(O<0?-1:0)):10)&&(2&abs(O)+1?main(-(2+abs(O))):main(2+abs(O)));} ------------------------------------------------------------------------------ | Georg Steffers | | EMail: ste...@in... | ------------------------------------------------------------------------------ -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/O d- s:+>: a- C+++>++++ UL/I+++$ !P--- L+++>++++ !E--- W+>+++ N++ o? K? w--- O M- V-- PS+ PE++ Y+ PGP>+ t++ 5++ x- R tv+ b+++ DI+ D+ G>++ e* h! r- y+ ------END GEEK CODE BLOCK------ |