On Tuesday 28 September 2004 18:03, Alex Deucher wrote:
> 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 tagge
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 fa
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.
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 con
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
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
