[Dri-devel] Mach64 DRI. Any progress?
Hello. Once again I try to get any answer about Mach64 DRI development. Is there any work in progress? Is the development for the Mach64 dead? It's really sad, but I've been waiting for one year and no progress have been made or I haven't been told about it. Has anybody merged the main trunk into the mach64 branch? I know that the Mach64 is no state-of-art, but a lot of laptops are still wearing one of these cards. Is there any way to help in the development of this driver? I've never coded a driver and the huge XFree trunk afraids me, but, anyway, I should try to help if somebody could help me with the first steps: Where to find information about the chip? Where to find some templates or architectural information about DRI,... I think the DRI development group is making a good work. It's a pitty I can't see the results in my old graphic card. Best regards. ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 DRI. Any progress?
Manuel Teira wrote: Hello. Once again I try to get any answer about Mach64 DRI development. Is there any work in progress? Is the development for the Mach64 dead? Having heard no sign of those who expressed an interest in pursuing development themselves on this list, and the original author now on a (hopefully!) rejuvenating longish break :), it seems it is indeed dead for now. I know that the Mach64 is no state-of-art, but a lot of laptops are still wearing one of these cards. The problem is VA has *really* more important things to do (AFAIK), so unless someone from the community steps forward to continue development, we're out of luck. Is there any way to help in the development of this driver? I've never coded a driver and the huge XFree trunk afraids me, but, anyway, I should try to help if somebody could help me with the first steps: Where to find information about the chip? Where to find some templates or architectural information about DRI,... Since I looked this up myself: ATI gives docs to Xfree86 developers. You can become one if you send a fix to some X problem to Xfree86.org (the appropriate places there). If you don't want to since you only want to hack DRI (definitely possible, read up on the archives here: DRI is *very* much isolated from the huge rest of Xfree), you can get the Utah-GLX code which had ATI Mach64 working. I think the DRI development group is making a good work. It's a pitty I can't see the results in my old graphic card. Also consider buying a new graphics card from a supportive vendor (Ati, Matrox, ...) which I'll likely do. However, this doesn't help alleviate your laptop troubles :-) Good luck (esp. if you do want to code!) Yours Malte #8-) ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 DRI. Any progress?
Hey, I have mach64 (or technically rage pro! why'd he call it mach64??) in my desktop, and I will be getting a k6-2 550 tomarrow so I'll have a better test platform (with kernel.org messing up cyrix arr, and 3dnow so essential...). I've actually had the code working on this platform twice, and I will try testing it out again sometime next week. Carl Busjahn Jeremy W. Bean wrote: On Sunday 17 June 2001 09:58, you wrote: Hello. Once again I try to get any answer about Mach64 DRI development. Is there any work in progress? Is the development for the Mach64 dead? It's really sad, but I've been waiting for one year and no progress have been made or I haven't been told about it. Has anybody merged the main trunk into the mach64 branch? I know that the Mach64 is no state-of-art, but a lot of laptops are still wearing one of these cards. Is there any way to help in the development of this driver? I've never coded a driver and the huge XFree trunk afraids me, but, anyway, I should try to help if somebody could help me with the first steps: Where to find information about the chip? Where to find some templates or architectural information about DRI,... I think the DRI development group is making a good work. It's a pitty I can't see the results in my old graphic card. Best regards. ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel Manuel, I know the feeling. There are quite a few laptops that still use Mach64 chips. And for a laptop which doesn't need amazing high-end graphics, it works very nice. As well consider the fact that it is not common to upgrade a video card in a laptop, which kind of implies that if you want the latest and greatest in accelerated gaming you would more commonly buy a new laptop every six months or so. From what I can tell there has not been any progress. I have the trunk and the mach64 branch both checked out. I have been attempting to learn as much as I can from ground up so that I can eventually help out in some way. In fact I had planned to merge the trunk into my copy of the mach64 branch this weekend but never got the time. I have many other things going on and only get a chance to tinker with things in my spare time. Agreed, having chip specs would be very nice. But from what I can tell ati requires you to register with them as a company and this is just me doing this for fun, there is no company involved and no profit involved. Does anyone else know how to get specs from ATI without a hastle? Am I wrong in my preception of how to get the specs? There are some real good documentation pointers off the DRI website, that give the general workings of the architecture and what is going on. In theory with all of that and with the actual code, it should not be too difficult to learn. That is what I am doing. Starting from the bottom, reading all the documentation, and checking out the code to fill in the blanks of how things are working. But like I said, progress has been slow. Right now, I am mostly just reading and trying to learn. And I am doing this is spare time between other things. I can definitly understand why development isn't funded for Mach64; but I am amazed that someone hasn't picked this code up yet and attempted to hack something together that works decently well. I suppose the learning curve and lack of Mach64 documentation are large deterents. Hopefully eventually Mach64 will be accelerated. Let's just hope the chip isn't truly obsolete before then :) Sincerely, Jeremy Bean ___ 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
[Dri-devel] DRI kernel modules
I've been browsing the FAQ comments and mailing lists and it appears one of the main problems in getting the DRI to run for newbies is the confusion between which kernel modules to use. The ones from the kernel or the XFree86 ones? Most people don't realize that the modules also get provided by XFree86 and that the ones from XFree86 are the ones you should use. Usually people just grab the latest kernel and then don't understand why their modules are outdated. So, my question is: wouldn't it be easier to remove the DRI stuff completely from the stock kernel? Then there would be only one source for the modules and we wouldn't have this confusion. The modules could be made into a kernel patch that can then be downloaded from the DRI website, just like the install packages. Really it already is integrated into the install patches anyway. Has anybody thought about this before? - Frank ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] pls update Status page to show that Radeon PCI cards unsupported
Michel Dänzer [EMAIL PROTECTED] writes: It's basically already there but disabled because there have been problems with it. Someone posted a patch to this list or to the patch tracker which apparently fixes it for him. I'm not sure if it's the right fix but you might be desperate enough to try it. :) I tried it and it does sort of work. It's not reliable, in the sense that sometimes (more often than not, maybe) when entering DRI mode I get these weird artifacts, usually composed of thick vertical bands displaying the wrong thing. I'm also getting an EINVAL error whenever a program tries to do anything with textures. I'm still trying to track that down, but right now it looks like an invalid (no function) ioctl is being called. It's using the code for a function (blit) that was valid for the r128, but doesn't exist for the radeon. I suppose I might have some sort of version skew problem. Does anyone have the technical docs for the radeon board? --Mike -- Mike Coleman, [EMAIL PROTECTED] Windows XP http://www.mathdogs.com Linux :) problem solving, expert software development ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 DRI. Any progress?
On Sun, Jun 17, 2001 at 12:33:29PM -0500, Jeremy W . Bean wrote: I can definitly understand why development isn't funded for Mach64; but I am amazed that someone hasn't picked this code up yet and attempted to hack something together that works decently well. I suppose the learning curve and lack of Mach64 documentation are large deterents. Have you looked at the new driver template code? I'm not a developer, but this sounds like the most logical place to start. Using the template code and changing the registers appropriately to suit the mach64 seems like the best way to avoid duplicate code while getting the core of the driver up to where all of the other drivers are. And it'd be pretty cool to have your name in the CHANGELOG as the primary developer for v0.99.0 :) Hopefully eventually Mach64 will be accelerated. Let's just hope the chip isn't truly obsolete before then :) You know as well as anyone else does that video cards are like mayflies; they're only around for about three days :) -- -=|JP|=-Compared to racing, heroine is a strong urge for something salty. Jon Pennington | Debian 2.3 -o) d r e n @ w h a c k . o r g | Auto Enthusiast /\\ Kansas City, MO, USA | ICQ UIN 6 9 6 7 2 9 3 1 _\_V ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
