Re: DRI - Voodoo3 - confusion
On Saturday 09 June 2001 00:03, Michael P. Soulier wrote: It's in both. X provides the DRI API, but to make use of it, you need a module for your video card. I'm using kernel 2.4.4, with a Voodoo3. The tdfx module is included with kernel 2.4.4. So, running at 16 bpp, I have 3D accel. You need to have the tdfx module loaded in the kernel (or compiled in for that matter) before you can use DRI. You'll also need libglide3. ii libglide3 2001.01.26-1 Graphics library for 3Dfx Voodoo based cards Ok, now I see things a bit clearer. I think (and hope) this is also possible with a 2.2. kernel. I found CONFIG_DRM and CONFIG_DRM_TDFX in the character devices section of the kernel configuration. Is that the same or equivalent what you have in your 2.4 kernel? I did not compile these options in my 2.2.19 kernel at the time because I didn't know what it was. And what about the device3dfx-source package? Is that needed for hardware accelleration or DRI? From the Makefile it appears that it compiles a module called 3dfx.o. What's that?
Re: DRI - Voodoo3 - confusion
Michael P. Soulier wrote: On Fri, Jun 08, 2001 at 09:52:06PM +0200, Robert Voigt wrote: I want DRI for my Voodoo3 card. But I'm confused. Somewhere I read DRI is included in XFree86 4.0.1. Somewhere else I read it's in the 2.4. kernel. And in /var/log/XFree.0.log I found the line: (EE) TDFX(0): DRIScreenInit failed, disabling DRI. (This is with 16bpp) Do I have DRI already and it just doesn't work? The reason why I want it is I want to use mplayer, and mplayer gives an error message when I run it. The FAQ of mplayer says I should update my driver if I get this error message. I don't know what driver they mean, but I found this http://www.geocrawler.com/archives/3/10464/2001/5/250/5777677/ That guy got DRI 0.6. But there is no DRI 0.6 I could download. Now, where is DRI? It's in both. X provides the DRI API, but to make use of it, you need a module for your video card. I'm using kernel 2.4.4, with a Voodoo3. The tdfx module is included with kernel 2.4.4. So, running at 16 bpp, I have 3D accel. You need to have the tdfx module loaded in the kernel (or compiled in for that matter) before you can use DRI. You'll also need libglide3. ii libglide3 2001.01.26-1 Graphics library for 3Dfx Voodoo based cards Works great for me. With mplayer? I think he's referring to the Xvideo Extension ouput of mplayer. To use the HW acceleration the card need to support the YUY2 packed and YV12 planar pixel format, and with similar configuration here (kernel 2.4.5 XFree86 4.0.3-4 and same libglide3), the output of xvinfo is: X-Video Extension version 2.2 screen #0 Adaptor #0: 3dfx Accelerated Video Engine number of ports: 1 port base: 74 operations supported: PutImage supported visuals: depth 16, visualID 0x23 ... depth 16, visualID 0x32 no port attributes defined maximum XvImage size: 1024 x 0 Number of image formats: 2 id: 0x32315659 (YV12) guid: 59563132--0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) id: 0x30323449 (I420) guid: 49343230--0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) so not YUY2 packed... Any hints? Andrea
Re: DRI - Voodoo3 - confusion
On Saturday 09 June 2001 13:02, Andrea Vettorello wrote: With mplayer? I think he's referring to the Xvideo Extension ouput of mplayer. To use the HW acceleration the card need to support the YUY2 packed and YV12 planar pixel format, and with similar configuration here (kernel 2.4.5 XFree86 4.0.3-4 and same libglide3), the output of xvinfo is: X-Video Extension version 2.2 screen #0 Adaptor #0: 3dfx Accelerated Video Engine number of ports: 1 port base: 74 operations supported: PutImage supported visuals: depth 16, visualID 0x23 ... depth 16, visualID 0x32 no port attributes defined maximum XvImage size: 1024 x 0 Number of image formats: 2 id: 0x32315659 (YV12) guid: 59563132--0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) id: 0x30323449 (I420) guid: 49343230--0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) so not YUY2 packed... Any hints? Andrea I get the same output. I think the problem is that YUV2 is not enabled/included in the Debian version of XFree86. On http://www.geocrawler.com/archives/3/10464/2001/5/250/5777677/ I read: Xfree-4.0.3 does not include YUY2 support. Then I had to get a new version of the DRI driver on http://dri.sourceforge.net. But on that website threre is nothing to download. They just say: The latest DRI drivers are included with XFree86 4.1.0. Does that mean I'll have to wait until XFree86 4.1.0 is packaged for Debian. Will YUV2 support be enabled then? Or do I have to compile XFree86 4.1.0?
Re: DRI - Voodoo3 - confusion
On Sat, Jun 09, 2001 at 11:32:45AM +0200, Robert Voigt wrote: Ok, now I see things a bit clearer. I think (and hope) this is also possible with a 2.2. kernel. I found CONFIG_DRM and CONFIG_DRM_TDFX in the character devices section of the kernel configuration. Is that the same or equivalent what you have in your 2.4 kernel? I did not compile these options in my 2.2.19 kernel at the time because I didn't know what it was. And what about the device3dfx-source package? Is that needed for hardware accelleration or DRI? From the Makefile it appears that it compiles a module called 3dfx.o. What's that? I never did get it working in the 2.2 kernel. I found all the documentation confusing as hell. But, I recall reading that it was done via a 3dfx device that needed to be created on the system. Oh wait, here it is. With X4, apparently the 3dfx device is not necessary. See here. http://dri.sourceforge.net/doc/DRIbeginner.html But if you're running XFree 3.3.X, then you need the 3dfx device. The details are apparently at http://www.linuxvoodoo.com/ Mike -- Michael P. Soulier [EMAIL PROTECTED] With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925 pgpp8RjcOFGKm.pgp Description: PGP signature
DRI - Voodoo3 - confusion
I want DRI for my Voodoo3 card. But I'm confused. Somewhere I read DRI is included in XFree86 4.0.1. Somewhere else I read it's in the 2.4. kernel. And in /var/log/XFree.0.log I found the line: (EE) TDFX(0): DRIScreenInit failed, disabling DRI. (This is with 16bpp) Do I have DRI already and it just doesn't work? The reason why I want it is I want to use mplayer, and mplayer gives an error message when I run it. The FAQ of mplayer says I should update my driver if I get this error message. I don't know what driver they mean, but I found this http://www.geocrawler.com/archives/3/10464/2001/5/250/5777677/ That guy got DRI 0.6. But there is no DRI 0.6 I could download. Now, where is DRI?
Re: DRI - Voodoo3 - confusion
On Fri, Jun 08, 2001 at 09:52:06PM +0200, Robert Voigt wrote: I want DRI for my Voodoo3 card. But I'm confused. Somewhere I read DRI is included in XFree86 4.0.1. Somewhere else I read it's in the 2.4. kernel. And in /var/log/XFree.0.log I found the line: (EE) TDFX(0): DRIScreenInit failed, disabling DRI. (This is with 16bpp) Do I have DRI already and it just doesn't work? The reason why I want it is I want to use mplayer, and mplayer gives an error message when I run it. The FAQ of mplayer says I should update my driver if I get this error message. I don't know what driver they mean, but I found this http://www.geocrawler.com/archives/3/10464/2001/5/250/5777677/ That guy got DRI 0.6. But there is no DRI 0.6 I could download. Now, where is DRI? It's in both. X provides the DRI API, but to make use of it, you need a module for your video card. I'm using kernel 2.4.4, with a Voodoo3. The tdfx module is included with kernel 2.4.4. So, running at 16 bpp, I have 3D accel. You need to have the tdfx module loaded in the kernel (or compiled in for that matter) before you can use DRI. You'll also need libglide3. ii libglide3 2001.01.26-1 Graphics library for 3Dfx Voodoo based cards Works great for me. Mike -- Michael P. Soulier [EMAIL PROTECTED] With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925 pgpgKKzyE0WIP.pgp Description: PGP signature
