Re: [Dri-devel] ATI Mach64 Driver
Jon Pennington wrote: > > On Sun, Apr 22, 2001 at 03:07:22AM -0500, Frank C . Earl wrote: > > > > No, it's not dead. Right now as I type this, I'm starting to sort through > > the process of learning how to get the build process for DRI drivers going. > > Once I've got that done, I plan on picking up the work done by Gareth > > followed by Richard Cognot to get RagePRO support under the DRI. > > I, too, am interested in the status of this project. I have a perfectly > good Xpert98 AGP sitting here collecting dust :). Frank, did you ever try the aligned-DMA-descriptors fix? -- Gareth ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] ATI Mach64 Driver
On Sun, Apr 22, 2001 at 03:07:22AM -0500, Frank C . Earl wrote: > On Friday 20 April 2001 10:36, Markus Kohls wrote: > > > I wonder, if there's anyone working on the mach64-driver yet? After Gareth > > stopped working on it, there seems to be noone, who is further working on > > it. Is the development on the mach64 dead? > > No, it's not dead. Right now as I type this, I'm starting to sort through > the process of learning how to get the build process for DRI drivers going. > Once I've got that done, I plan on picking up the work done by Gareth > followed by Richard Cognot to get RagePRO support under the DRI. I, too, am interested in the status of this project. I have a perfectly good Xpert98 AGP sitting here collecting dust :). -- -=|JP|=-"I'm not unemployed, my career's just in a holding pattern" Jon Pennington | Debian 2.4 -o) [EMAIL PROTECTED] | Auto Enthusiast/\\ Kansas City, MO, USA| Proud Husband and Father _\_V ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] ATI Radeon specs update
Pekka Kujansuu wrote: > > Hi! > > I noticed on flipCode, that ATI has updated their developer docs. Quote > from flipCode: "ATI's developer site has been updated with new > presentations on Vertex Shading, and Curved PN Triangles, as well as > new/updated Radeon SDK docs." The URL is > http://www.ati.com/na/pages/resource_centre/dev_rel/whatsnew.html I hope > it's of any use for the ATI-driver developers. :-) Well... they probably > have noticed the update aldready, but I thought I still should post it, > just to be sure. :-) It's part of their SDK for application developers. We know all about the features they are showing off here... -- Gareth ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] RADEON VE patch
David Konerding wrote: > > How are you guys handling the fat that the Radeon VE lacks the 3D capabilities > that the rest of the Radeon line has? Don't you have to avoid the 3D caps and > fall back to Mesa-in-XFree86? The DRI driver doesn't make use of the features that are missing from the VE, so it's not an issue. -- Gareth ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] ATI all in wonder PCI works
Thomas Herault wrote: > > - it wasn't clear at a first time where the DRM was located, so > I loose some time trying to find patch for kernel module in linux-kernel > archive before I finally tried > xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/ > (maybe it would be fine if it were more documented) If I ever get around to writing the DRI Developer's Guide, this kind of information will be included. In fact, I might take a crack at that today... > - LOCALE is broken with your revision of the libX11 (04/21 CVS) : > I had to use the binary version of libX11 of 4.0.2 for netscape, emacs > and other applications to work. It doesn't seem to introduce problems > with DRI : OpenGL applications still work. If you are using the DRI CVS as your main X install, you need to build the nls subdirectory to get the locale stuff. It's detailed in the Compilation Guide, Section 9.3. -- Gareth ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] RADEON VE patch
Buddy Smith wrote: > On Sat, Apr 21, 2001 at 12:50:19PM -0700, David Konerding wrote: > > > How are you guys handling the fat that the Radeon VE lacks the 3D capabilities > > that the rest of the Radeon line has? Don't you have to avoid the 3D caps and > > fall back to Mesa-in-XFree86? > > > > My patch was a 10-20minute hack to make the card at least function. > I've not had any issues w/ the small amount of 3D stuff that i've tried to > do. > > --buddy OK, great. I'll take a look at it since I have a VE and I would like to use it with XFree86. I had already played around with adding the PCI identifiers (there has been a patch floating around for a few weeks) but didn't have much luck. I'm going to see if compiling the DRI cvs with the VE patch and see what I get. ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] RADEON VE patch
David Konerding wrote: > > Brian Paul wrote: > > > Buddy Smith wrote: > > > > > > Hi. > > > > > > This is a patch i made to add the RADEON VE chipset to the DRI source. > > > > > > It's available at > > > > > > http://foobar.resnet.gatech.edu/~nullset/radeon_ve-DRI-patch > > > > > > I did not post it to the patch list, because i'm not sure if the format is > > > correct. i generated it using diff -u -r > > > > > > It changes: > > > > > > xc/lib/GL/mesa/src/drv/radeon/radeon_screen.c > > > xc/programs/Xserver/hw/xfree86/common/xf86PciInfo.h > > > xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c > > > xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_probe.c > > > > > > It simply adds the PCI_CHIP_RADEON_VE to the .h files, and appropriate > > > entries to the 'switch' statements in the above files. > > > > > > Please review it and if you feel so inclined, apply it to the source. i > > > mainly made it for my own use, but i hope this trivial patch helps others > > > :) > > > > > How are you guys handling the fat that the Radeon VE lacks the 3D capabilities > that the rest of the Radeon line has? Don't you have to avoid the 3D caps and > fall back to Mesa-in-XFree86? To be honest, I really don't know anything about the VE. The patch seemed to be useful, however. -Brian ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Matrox Dualhead and ClonTV under XFree86
German Gomez Garcia wrote: > I've finally make TV out and dualhead work under 2.4.3-ac11 and > matroxfb, my question is if there is any possibility to use the code on > matrox framebuffer dualhead capabilities in XFree86. Wrong list, there were (pointers to) solutions for this floating around on the Xpert list a while ago. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] RADEON VE patch
On Sat, Apr 21, 2001 at 12:50:19PM -0700, David Konerding wrote: > How are you guys handling the fat that the Radeon VE lacks the 3D capabilities > that the rest of the Radeon line has? Don't you have to avoid the 3D caps and > fall back to Mesa-in-XFree86? > My patch was a 10-20minute hack to make the card at least function. I've not had any issues w/ the small amount of 3D stuff that i've tried to do. --buddy ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] RADEON VE patch
Brian Paul wrote: > Buddy Smith wrote: > > > > Hi. > > > > This is a patch i made to add the RADEON VE chipset to the DRI source. > > > > It's available at > > > > http://foobar.resnet.gatech.edu/~nullset/radeon_ve-DRI-patch > > > > I did not post it to the patch list, because i'm not sure if the format is > > correct. i generated it using diff -u -r > > > > It changes: > > > > xc/lib/GL/mesa/src/drv/radeon/radeon_screen.c > > xc/programs/Xserver/hw/xfree86/common/xf86PciInfo.h > > xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c > > xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_probe.c > > > > It simply adds the PCI_CHIP_RADEON_VE to the .h files, and appropriate > > entries to the 'switch' statements in the above files. > > > > Please review it and if you feel so inclined, apply it to the source. i > > mainly made it for my own use, but i hope this trivial patch helps others > > :) > > How are you guys handling the fat that the Radeon VE lacks the 3D capabilities that the rest of the Radeon line has? Don't you have to avoid the 3D caps and fall back to Mesa-in-XFree86? ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] RADEON VE patch
Buddy Smith wrote: > > Hi. > > This is a patch i made to add the RADEON VE chipset to the DRI source. > > It's available at > > http://foobar.resnet.gatech.edu/~nullset/radeon_ve-DRI-patch > > I did not post it to the patch list, because i'm not sure if the format is > correct. i generated it using diff -u -r > > It changes: > > xc/lib/GL/mesa/src/drv/radeon/radeon_screen.c > xc/programs/Xserver/hw/xfree86/common/xf86PciInfo.h > xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c > xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_probe.c > > It simply adds the PCI_CHIP_RADEON_VE to the .h files, and appropriate > entries to the 'switch' statements in the above files. > > Please review it and if you feel so inclined, apply it to the source. i > mainly made it for my own use, but i hope this trivial patch helps others > :) > I've applied your patch to the DRI trunk. -Brian ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: SiS DRI driver fix!!!
Frank wrote: > > Don't hesitate to send any messages to the mailing lists! If you are > interested in development subscribe to the dri-devel list. > > I've forwarded your message to the list. > > - Frank > > - Original Message - > From: "David Gaarenstroom" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, April 19, 2001 8:14 AM > Subject: SiS DRI driver fix!!! > > > I don't want to mix up the DRI-development, so I 'm just mailing this > > single message: > > > > If someone just adds the line "#include " to "sis_mm.c", > > the sis dri-driver can be re-inserted to the DRI project. > > > > Tnx, > > David I've committed this fix, though I can't test the driver. -Brian ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] ATI Mach64 Driver
On Friday 20 April 2001 10:36, Markus Kohls wrote: > I wonder, if there's anyone working on the mach64-driver yet? After Gareth > stopped working on it, there seems to be noone, who is further working on > it. Is the development on the mach64 dead? No, it's not dead. Right now as I type this, I'm starting to sort through the process of learning how to get the build process for DRI drivers going. Once I've got that done, I plan on picking up the work done by Gareth followed by Richard Cognot to get RagePRO support under the DRI. -- Frank Earl ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI under FreeBSD
Build "XFree86-4" from a very very recent FreeBSD ports tree. It's based on XFree86-4.0.3 but I believe building of the tdfx and mga kernel modules is turned on for FreeBSD-4.x. You'll need to get glide-3 up and running to build and drive Voodoo3/4/5. Another "port" for glide3 for the voodoo3 was also recently added. On Sat, 21 Apr 2001, Brian Paul wrote: > Simon Cahuk wrote: > > > > Hi! > > Does DRI work under FreeBSD? Can I compile glide under it (my chip is > > banshee)? > > It was working at one time, with 3dfx hardware and the G400, I think. > I'm not sure what the status is. I don't think anyone is actively > maintaining FreeBSD support. > > I suggest giving it a try anyway. > > -Brian > > ___ > Dri-devel mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/dri-devel > ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI under FreeBSD
Simon Cahuk wrote: > > Hi! > Does DRI work under FreeBSD? Can I compile glide under it (my chip is > banshee)? It was working at one time, with 3dfx hardware and the G400, I think. I'm not sure what the status is. I don't think anyone is actively maintaining FreeBSD support. I suggest giving it a try anyway. -Brian ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] G400 and blending
On Fri, 20 Apr 2001, Jon Pennington wrote: > On Fri, Apr 20, 2001 at 04:43:55PM -0600, Brian Paul wrote: > > Pasi Kärkkäinen wrote: > > > > > > Hello! > > > > > > Are there known blending bugs in the mga-driver (g400)? When I render many > > > additive polygons on the top of each other with small alpha-value > > > (something like 0.05) the result is something it shouldn't be with g400. > > > With software-mesa it's correct as well as with nvidia's drivers. > > > > > > If this is not a known issue, I might do little app that demonstrates > > > this.. > > > > I've found that the accuracy of blending isn't always very good on > > some hardware. Not much can be done about that. > > > > -Brian > > Pasi, does this happen if you're running Windows drivers on the same card? > Well that's something I didn't think about :) I'll try it (maybe tomorrow) and post the results. - Pasi Kärkkäinen ^ . . Linux /-\ Choice.of.the .Next.Generation. ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
RE: [Dri-devel] ATI Rage Mobility, for Robert Johansson
I used the ATI Rage Mobility 4P i think it was (4mb chip) with the Utah- glx drivers and it worked fantastically and faster than ATI's Winblows drivers thanks to the efforts of Gareth Hughes. I am not sure if it's supported under the DRI framework at all, but Utah- glx was good enough for what i needed, and basically for what that super- crappy chipset from ATI can do. Don't expect miracles, it's a piece of shit chip. A voodoo1 blows it away easily. I used it primarily for working on some GL apps on the go (laptop) and occasional relaxation with Q3A on the go again ... good luck PS. letme know if i am mistaken about DRI support for it ... Free, encrypted, secure Web-based email at www.hushmail.com
RE: [Dri-devel] SiS DRI Support and Ademar de Souza Reis Jr.
Ademar, looking at your pasted info I see: I'm using: kernel 2.4.3 SiS 6326 chipset and OpenGL vendor string: Brian Paul OpenGL renderer string: SiS 300/630/530 DR Mode OpenGL version string: 1.2 Mesa 3.4 As far as I know the Sis 6326 is not the same as the Sis 630. I don't know this with 100% confidence, but I know that I had to install different drivers under Wincrap and also under linux I used the Utah-GLX drivers for the Sis 6326 chips, not the DRI. I have the Sis 630 and have not been able to get it working with the DRI. The last thing i remember getting is a Seg. Fault of some sort. I will look at it again soon, as well as the fix that you pasted. If you are interested i also posted a kinda Off Topic message on this devels list which has a URL with the PDF's for the Sis chipsets!! I don't know how these people in Ukraine (i think) got it, but I certainly couldn't find it on Sis' site, and certainly got no responses whatsoever from their tech/sales/managerial emails .. Anyways, if you do have any success with the said DRI driver, could you email me at adoniz_at_hushmail.com ( replace _at_ with @ ). I'd be interested to know the results. Also if you get a chance to go over those PDF's then please look at the sis 630 and tell me if i am confused or not, but I didn't see any specific mention on the 3D registers of that chipset. I can see all the 2D registers, but none of the 3D. I might have missed it because i have not had the time to print it out and read it, but had to skim it using Acrobat ... Anyways, good luck tony PS. I am using X 4.0.2, because Alan Hourihane told me that the last working SiS driver was done for 4.0.1a and also in some docs I saw that it was working for 4.0.2 .. somewhere. i forget right now. Kernel 2.2.19 and 2.4.3 with respective agpgart. Free, encrypted, secure Web-based email at www.hushmail.com
[Dri-devel] ATI Radeon specs update
Hi! I noticed on flipCode, that ATI has updated their developer docs. Quote from flipCode: "ATI's developer site has been updated with new presentations on Vertex Shading, and Curved PN Triangles, as well as new/updated Radeon SDK docs." The URL is http://www.ati.com/na/pages/resource_centre/dev_rel/whatsnew.html I hope it's of any use for the ATI-driver developers. :-) Well... they probably have noticed the update aldready, but I thought I still should post it, just to be sure. :-) -- Pekka Kujansuu - [EMAIL PROTECTED] "Codito, ergo sum" - "I code, therefore I am" - "Koodaan, siispä olen" ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: OpenGL (followup and a question)
I'll ask the core xfree86 developers first: Is there any possibility of having glut added to the standard xfree86 sources? Would be nice to have a toolkit for OpenGL distributed with xfree86, and the maintainer of glut appears to have moved on to something else. (nvidia) I believe the build instructions for glut on Linux are pretty much out of date. For Alex: Note that if you built x from cvs sources, (and probably 4.0.3?) libGLU is already in the sources. You also need to build the kernel module from the xfree86 sources to enable DRM. The drm module in the std. kernel tree is often out of date. I have a matrox card and a k6 and thus use this host.def (in xc/config/cf/ when building xfree86 for Linux: #define DefaultGcc2i386Opt -O2 -march=k6 -pipe #define XF86CardDrivers mga fbdev v4l #define DriDrivers mga #define LinuxDistribution LinuxUnknown #define DefaultCCOptions -ansi GccWarningOptions -pipe -O2 #define BuildXF86DRI YES #define BuildXF86DRM YES #define BuildGLULibrary YES #define SharedLibFont NO #define ProjectRoot /usr/X11R6 #define MesaUse3DNow YES #define Has3DNowSupport YES #define HasKatmaiSupport NO #define Freetype2Dir /usr #define DefaultUserPath /bin:/usr/bin:/usr/local/bin:/usr/X11/bin #define BuildDebug NO #define BuildFonts NO #define XInputDrivers mouse #define HasLinuxInput YES #define XF1BppNO #define XF4BppNO #define StripInstalledPrograms YES #define TermcapLibrary -lncurses #define ForceNormalLib YES #define HaveMatroxHal YES #define UseMatroxHal YES You'll probably want to edit this to suit you. YMMV Unsure if you need to edit site.def for host.def to be read... The kernel module is not built automatically. You need to go to: ./programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/ and do: make -f Makefile.linux The resulting module should be placed in /lib/modules/... somewhere Regards, Dag B ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] ATI all in wonder PCI works
Hello, I'm using a dual head X configuration, with an ASUS GeForce2 as AGP card, and ATI All in wonder PCI with 32 Mb memory. NVidia drivers never wanted to work on my station, but since yesterday, (didn't tried for a long time), the All in Wonder PCI card works perfectly with OpenGL applications. Thanks a lot for your work. 2 little problems : - it wasn't clear at a first time where the DRM was located, so I loose some time trying to find patch for kernel module in linux-kernel archive before I finally tried xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/ (maybe it would be fine if it were more documented) - LOCALE is broken with your revision of the libX11 (04/21 CVS) : I had to use the binary version of libX11 of 4.0.2 for netscape, emacs and other applications to work. It doesn't seem to introduce problems with DRI : OpenGL applications still work. If you want some testing with this card, I can do them. ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Matrox Dualhead and ClonTV under XFree86
Hello, I've finally make TV out and dualhead work under 2.4.3-ac11 and matroxfb, my question is if there is any possibility to use the code on matrox framebuffer dualhead capabilities in XFree86. I know that we have that propietary libHAL but it is working quite bad for me, for example the brightness goes up and down randomly and other nasty things make it useless for TV output. In the other hand, I'm able to see DivX and DVDs on my TV using matroxfb and mplayer. Regards, - german - German Gomez Garcia | "This isn't right. This isn't even wrong." <[EMAIL PROTECTED]> | -- Wolfgang Pauli ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Dri-devel digest, Vol 1 #740 - 15 msgs
Today, Janne Pänkälä wrote:
>>From: "John X" <[EMAIL PROTECTED]>
>>Subject: [Dri-devel] Radeon SDR provlems fixed (for me at least)
>
>>My Radeon SDR is now working perfectly. I haven't yet had a crash or
>>sonsole corruption (or serious visual glitch) with the radeon-20010418
>>drivers. uptime is 1 day and 6 hours so far. I had GL demos
>>(xscreensaver modules) running for an entire night with no problems.
>
>>Whatever you guys did to fix the Radeon SDR drivers they work great now.
>>You guys are great!
>
>I also updated to the CVS veriosn 20010418 and for a while it seemed
>really good. gears program was rotating quite long before it hang but in
>the end it hang to the
>--
>radeonWaitForFrameCompletion (rmesa=0x80761e8) at radeon_ioctl.c:402
>402 for ( i = 0 ; i < 1024 ; i++ ) {
>(gdb) p radeon_ioctl.c:400
>No symbol "radeon_ioctl" in current context.
>(gdb) b radeon_ioctl.c:400
>Breakpoint 1 at 0x40509428: file radeon_ioctl.c, line 400.
>--
>
>like so many times before :(
>--
>(gdb) list
>395 frame = INREG( RADEON_LAST_FRAME_REG );
>396 #endif
>397 if ( sarea->last_frame - frame <= RADEON_MAX_OUTSTANDING ) {
>398 break;
>399 }
>400 wait++;
>401 /* Spin in place a bit so we aren't hammering the bus */
>402 for ( i = 0 ; i < 1024 ; i++ ) {
>403 delay();
>404 }
>--
>
>This time frame == 3 and does not change and sarea->last_frame == 65002
>I was following the INREG() macro and it seems to do some 32bit MMIO?
>
>I'm still clueless as to what causes this. I'm ruling out broken
>motherboard since there was never any problems with Voodoo3000 card. Or
>could this be that Radeon is not compatible with my mobo? (their customer
>support is VERY SLOW). I finally managed to get the board to work somehow
>in windows (2000 this time) but it's not stable there either but can't say
>is this because of games or what (3DMark2000 goes trough properly). (and
>no I'm not overclocking)
Unfortunately you cannot rule out broken AGP on your motherboard. The
Voodoo3 would work fine because it doesn't use any of the extra features
that AGP has over PCI, it doesn't need any sort of agpgart. I had similar
problems with my radeon which were rectified by upgrading my motherboard's
BIOS.
Hope this helps...
Regards,
Philip Willoughby
--
echo [EMAIL PROTECTED] | tr "bizndfohces" "pwgd9ociaku"
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] [OT] a taste of Glasnost :) Okay kidding, here are some PDF's that might help developers
I know this is a bit off topic (not totally because there's info on the SiS 540/630 etc chipsets), but I wanted to share this info because I am sure some of you might have been looking for it like i was ... I found this site and it had quite a few PDF's that I was unable to get my hands on from the companies themselves. So fsck them for not giving us docs. Here they are thanks to the boys in Ukraine (?): http://ic.doma.kiev.ua/pdf/chip/cpu.htm Free, encrypted, secure Web-based email at www.hushmail.com
