R300 driver update
Hi, I decided to commit what I have in terms of an R300 driver so far. You can find You can find it in th r300 project on SourceForge in the r300_driver module: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/r300 checkout r300_driver As you can easily see I started with the R200 driver. Since I didn't know what to rip out and what to keep in at first, I decided to take the extra time and separate stuff out into Radeon generic and R200/R300 code. So in theory, the driver should still work on R200 hardware, although a) I couldn't tested this and b) it's not quite uptodate (about a week old). I have written state emission code which works, and I have started implementing hardware accelerated clear. Something does happen on the screen, but immediately afterwards I get a hard lockup for now. I'll let you know when the driver is more usable. cu, Nicolai pgpsE6JTPWXag.pgp Description: PGP signature
Re: R300 driver update
On Tue, 28 Sep 2004, Nicolai Haehnle wrote: Hi, I decided to commit what I have in terms of an R300 driver so far. You can find You can find it in th r300 project on SourceForge in the r300_driver module: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/r300 checkout r300_driver As you can easily see I started with the R200 driver. Since I didn't know what to rip out and what to keep in at first, I decided to take the extra time and separate stuff out into Radeon generic and R200/R300 code. So in theory, the driver should still work on R200 hardware, although a) I couldn't tested this and b) it's not quite uptodate (about a week old). I have written state emission code which works, and I have started implementing hardware accelerated clear. Something does happen on the screen, but immediately afterwards I get a hard lockup for now. I'll let you know when the driver is more usable. cu, Nicolai Hi Nicolai, you can just rename the driver so it produces r300_dri.so - the 2d driver is in fact configured to tell DRI clients to use that binary. best Vladimir Dergachev --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 driver update
On Tuesday 28 September 2004 15:02, Vladimir Dergachev wrote: On Tue, 28 Sep 2004, Nicolai Haehnle wrote: Hi Nicolai, you can just rename the driver so it produces r300_dri.so - the 2d driver is in fact configured to tell DRI clients to use that binary. Well, it does produce r300_dri.so right now. The reason I am doing the work in an r300/ subdirectory is that development is going on in a different CVS repository, and I really don't fancy worrying about complicated merges with Mesa CVS (across file renames, at that!). Or maybe I somehow misunderstood what you meant? On a more happy note, Clear doesn't lock up anymore, but the coordinate calculation seems to be all wrong. cu, Nicolai pgpF6IkHKYM9k.pgp Description: PGP signature
Re: R300 driver update
On Tue, 28 Sep 2004 16:28:45 +0200, Nicolai Haehnle [EMAIL PROTECTED] wrote: On Tuesday 28 September 2004 15:02, Vladimir Dergachev wrote: On Tue, 28 Sep 2004, Nicolai Haehnle wrote: Hi Nicolai, you can just rename the driver so it produces r300_dri.so - the 2d driver is in fact configured to tell DRI clients to use that binary. Well, it does produce r300_dri.so right now. The reason I am doing the work in an r300/ subdirectory is that development is going on in a different CVS repository, and I really don't fancy worrying about complicated merges with Mesa CVS (across file renames, at that!). Or maybe I somehow misunderstood what you meant? I think Nicolai has proven his competence as a coder, I think it'd be ok to give him mesa cvs access. it might be easier to develop in mesa cvs to keep synced up and such. Thoughts? I suppose you might want to wait till 6.2 is tagged. Alex On a more happy note, Clear doesn't lock up anymore, but the coordinate calculation seems to be all wrong. cu, Nicolai --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 driver update
On Tue, 28 Sep 2004, Nicolai Haehnle wrote: On Tuesday 28 September 2004 15:02, Vladimir Dergachev wrote: On Tue, 28 Sep 2004, Nicolai Haehnle wrote: Hi Nicolai, you can just rename the driver so it produces r300_dri.so - the 2d driver is in fact configured to tell DRI clients to use that binary. Well, it does produce r300_dri.so right now. The reason I am doing the work in an r300/ subdirectory is that development is going on in a different CVS repository, and I really don't fancy worrying about complicated merges with Mesa CVS (across file renames, at that!). Or maybe I somehow misunderstood what you meant? It is I misunderstood what you meant - I thought you did not rename the driver. One very important feature of your driver is that allows to run with CP mode used for 2d operations and everything else done in software - this produces quite a speed up for most cards. This is useful for playing 2d games via Wine and for saving power on notebooks. Do I understand right that this (software fallback only) driver will have problems with regular X.org 6.8.1 ? If so it is unfortunate, or we could release a set of drivers for 6.8.1. On a more happy note, Clear doesn't lock up anymore, but the coordinate calculation seems to be all wrong. Cool ! Vladimir Dergachev cu, Nicolai --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R300 driver update
Alex Deucher wrote: On Tue, 28 Sep 2004 16:28:45 +0200, Nicolai Haehnle [EMAIL PROTECTED] wrote: On Tuesday 28 September 2004 15:02, Vladimir Dergachev wrote: On Tue, 28 Sep 2004, Nicolai Haehnle wrote: Hi Nicolai, you can just rename the driver so it produces r300_dri.so - the 2d driver is in fact configured to tell DRI clients to use that binary. Well, it does produce r300_dri.so right now. The reason I am doing the work in an r300/ subdirectory is that development is going on in a different CVS repository, and I really don't fancy worrying about complicated merges with Mesa CVS (across file renames, at that!). Or maybe I somehow misunderstood what you meant? I think Nicolai has proven his competence as a coder, I think it'd be ok to give him mesa cvs access. it might be easier to develop in mesa cvs to keep synced up and such. Thoughts? I suppose you might want to wait till 6.2 is tagged. Fine by me. Daniel Stone can set you up with CVS-write permission. Just don't mess up the core/trunk code this week. -Brian --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
