Eric Anholt wrote:
On Tue, 2003-12-09 at 10:29, Brian Paul wrote:
Alan Hourihane wrote:
On Tue, Dec 09, 2003 at 09:58:44AM -0800, Jon Smirl wrote:
--- Alan Hourihane [EMAIL PROTECTED] wrote:
[...]
I think SourceForge has fixed the CVS problems of times gone by.
If SF's CVS causes problems, I'm OK
On Tue, 09 Dec 2003 17:53:14 -0600
David D. Hagood [EMAIL PROTECTED] wrote:
Alan Hourihane wrote:
I'm going to merge the newmesa branch to the trunk in a few moments.
I've giving people a heads up that I'm going to delete the xc/extras/Mesa
directory and insist on people checking out a
Felix Kühling wrote:
On Tue, 09 Dec 2003 17:53:14 -0600
David D. Hagood [EMAIL PROTECTED] wrote:
Alan Hourihane wrote:
I'm going to merge the newmesa branch to the trunk in a few moments.
I've giving people a heads up that I'm going to delete the xc/extras/Mesa
directory and insist on people
Felix Kühling wrote:
It would be annoying for people with dialup connections if make required
access to a remote CVS repository.
And how would that be any different than syncing up with the main DRI
CVS repo? If you are building one from CVS, you may as well get the
other from CVS as well.
David D. Hagood [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
It would be annoying for people with dialup connections if make required
access to a remote CVS repository.
And how would that be any different than syncing up with the main DRI
CVS repo? If you are building one from CVS, you
Martin Spott wrote:
You would sync manually and not every time you call 'make',
Whether you sync'ed every time or not would depend upon the way the make
rule was written - if the rule is tied to the existance of the
directory, then the pull would happen the first time only.
I'm going to merge the newmesa branch to the trunk in a few moments.
I've giving people a heads up that I'm going to delete the xc/extras/Mesa
directory and insist on people checking out a copy of Mesa's newtree and
people setting that in their xc/config/cf/host.def file to point to their
checked
On Tue, 9 Dec 2003 15:11:06 +
Alan Hourihane [EMAIL PROTECTED] wrote:
I'm going to merge the newmesa branch to the trunk in a few moments.
I've giving people a heads up that I'm going to delete the xc/extras/Mesa
directory and insist on people checking out a copy of Mesa's newtree and
Alan Hourihane wrote:
I'm going to merge the newmesa branch to the trunk in a few moments.
I've giving people a heads up that I'm going to delete the xc/extras/Mesa
directory and insist on people checking out a copy of Mesa's newtree and
people setting that in their xc/config/cf/host.def file to
How should this affect DRI 3d drivers? According to the documenation:
http://dri.sourceforge.net/doc/DRIintro.html
it says Most DRI 3D drivers today are based on Mesa. How so?
Is it that the 3d drivers (_dri.so's) use the Mesa Library to to
catch OpenGL calls and map them onto hardware events? I
--- Alan Hourihane [EMAIL PROTECTED] wrote:
So Mesa/newtree is going to be the master copy of the dri drivers, including the
ones in mesa/dri/drivers? I'm all for that after doing the merge a couple of
times.
I've giving people a heads up that I'm going to delete the xc/extras/Mesa
directory
Jon Smirl wrote:
--- Alan Hourihane [EMAIL PROTECTED] wrote:
So Mesa/newtree is going to be the master copy of the dri drivers, including the
ones in mesa/dri/drivers? I'm all for that after doing the merge a couple of
times.
Yes.
I've giving people a heads up that I'm going to delete the
On Tue, Dec 09, 2003 at 09:58:44AM -0800, Jon Smirl wrote:
--- Alan Hourihane [EMAIL PROTECTED] wrote:
So Mesa/newtree is going to be the master copy of the dri drivers, including the
ones in mesa/dri/drivers? I'm all for that after doing the merge a couple of
times.
Yes.
I've giving
Alan Hourihane wrote:
On Tue, Dec 09, 2003 at 09:58:44AM -0800, Jon Smirl wrote:
--- Alan Hourihane [EMAIL PROTECTED] wrote:
So Mesa/newtree is going to be the master copy of the dri drivers, including the
ones in mesa/dri/drivers? I'm all for that after doing the merge a couple of
times.
Yes.
Luis R. Rodriguez wrote:
How should this affect DRI 3d drivers? According to the documenation:
http://dri.sourceforge.net/doc/DRIintro.html
it says Most DRI 3D drivers today are based on Mesa. How so?
Is it that the 3d drivers (_dri.so's) use the Mesa Library to to
catch OpenGL calls and map them
Alan Hourihane wrote:
I'm going to merge the newmesa branch to the trunk in a few moments.
I've giving people a heads up that I'm going to delete the xc/extras/Mesa
directory and insist on people checking out a copy of Mesa's newtree and
people setting that in their xc/config/cf/host.def file to
Did the DRM device drivers get moved too? They generally have to be changed in
tandem with the 3D drivers.
=
Jon Smirl
[EMAIL PROTECTED]
__
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
Jon Smirl wrote:
Did the DRM device drivers get moved too? They generally have to be changed in
tandem with the 3D drivers.
Not yet. Let's just get what we've done working tested.
The DRM drivers have a proper, versioned interface to the driver, so a lot of
the arguments about co-evolution
On Tue, 2003-12-09 at 18:33, Luis R. Rodriguez wrote:
This should probably go in a another e-mail thread but what sort of more
tests are left before merging IGP patch into DRI cvs tree?
As soon as I find the time, I intend to look at your additions to my
patch and see about getting it in.
Alan Hourihane wrote:
I'm going to merge the newmesa branch to the trunk in a few moments.
I've giving people a heads up that I'm going to delete the xc/extras/Mesa
directory and insist on people checking out a copy of Mesa's newtree and
people setting that in their xc/config/cf/host.def file to
On Tue, 2003-12-09 at 10:29, Brian Paul wrote:
Alan Hourihane wrote:
On Tue, Dec 09, 2003 at 09:58:44AM -0800, Jon Smirl wrote:
--- Alan Hourihane [EMAIL PROTECTED] wrote:
So Mesa/newtree is going to be the master copy of the dri drivers, including the
ones in mesa/dri/drivers? I'm all
21 matches
Mail list logo
