On Fri, 23 Jul 2004 09:43:34 -0700, Eric Anholt <[EMAIL PROTECTED]> wrote:
> On Fri, 2004-07-23 at 01:56, Sérgio M. Basto wrote:
> > On Fri, 2004-07-23 at 05:04, Eric Anholt wrote:
> > > I still need to merge the development drivers
> > > (mach64, savage), but my testbox is down due to a bad flopp
On Sat, 24 Jul 2004 18:55:48 +0100, Alan Cox <[EMAIL PROTECTED]> wrote:
> I have S3virge DRI ported but not working
>
While you are on this fixing up old chipsets kick, you ought to finish
off the trident and tdlabs drivers. :)
Alex
---
This
I have S3virge DRI ported but not working
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=100
On Sun, 2004-07-25 at 21:21, Eric Anholt wrote:
> As I said in the message quoted, someone will need to go to the savage
> driver, cvs up -jDRI-XFree86-4_3_99_12-merge -jDRI, resolve conflicts,
> place the new code under a BuildDevelDRIDrivers ifdef (see the via
> driver), and test. This is what i
On Sun, 2004-07-25 at 11:47, Sérgio Monteiro Basto wrote:
> On Fri, 2004-07-23 at 23:28, Sérgio Monteiro Basto wrote:
> > > Someone needs to go into x.org cvs, cd .../drivers/savage, cvs up
> > > -jDRI-XFree86-4_3_99_12-merge -jDRI and resolve conflicts, place the new
> > > code under a BuildDevelD
> Someone needs to go into x.org cvs, cd .../drivers/savage, cvs up
> -jDRI-XFree86-4_3_99_12-merge -jDRI and resolve conflicts, place the new
> code under a BuildDevelDRIDrivers ifdef, and test. Until then you won't
> be able to build a working savage setup from x.org.
>
> #define BuildDevelD
On Fri, 2004-07-23 at 01:56, Sérgio M. Basto wrote:
> On Fri, 2004-07-23 at 05:04, Eric Anholt wrote:
> > I still need to merge the development drivers
> > (mach64, savage), but my testbox is down due to a bad floppy and I do
> > want to test these merges on the appropriate hardware.
>
> yes , I
On Fri, 23 Jul 2004 10:32:55 +0100 (IST), Dave Airlie <[EMAIL PROTECTED]> wrote:
>
> also as far as I know the unichrome driver is in-secure it suffers I think
> the same issues as the savage and mach64 with its DDX setting up in-secure
> buffers...
>
> have a look at
> http://dri.sourceforge.net
also as far as I know the unichrome driver is in-secure it suffers I think
the same issues as the savage and mach64 with its DDX setting up in-secure
buffers...
have a look at
http://dri.sourceforge.net/IRC-logs/20040628.txt
if this is so I recommend the via stuff goes in under devel for now ..
On Fri, 2004-07-23 at 05:04, Eric Anholt wrote:
I still need to merge the development drivers
(mach64, savage), but my testbox is down due to a bad floppy and I do
want to test these merges on the appropriate hardware.
yes , I had this problem yesterday, DRI savage module doesn't compile.
Adam Jackson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 23 July 2004 00:04, Eric Anholt wrote:
The point is that the DRI is merging into X.Org and there won't be a
separate tree any more. I still need to merge the development drivers
(mach64, savage), but my testbox is down due
On Thu, 2004-07-22 at 23:00, Adam Jackson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Friday 23 July 2004 00:04, Eric Anholt wrote:
> > The point is that the DRI is merging into X.Org and there won't be a
> > separate tree any more. I still need to merge the development driver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 23 July 2004 00:04, Eric Anholt wrote:
> The point is that the DRI is merging into X.Org and there won't be a
> separate tree any more. I still need to merge the development drivers
> (mach64, savage), but my testbox is down due to a bad flo
On Thu, 2004-07-22 at 18:11, Sérgio Monteiro Basto wrote:
> Hi
> I am happy to see that dri and drm are in xorg cvs (very cool:).
> I will test savage dri soon.
>
> But my email is about other subject.
> So I think it time to have a new dri tree since the trunk tree is a
> "very" old version.
> Ot
Hi
I am happy to see that dri and drm are in xorg cvs (very cool:).
I will test savage dri soon.
But my email is about other subject.
So I think it time to have a new dri tree since the trunk tree is a
"very" old version.
Other question is about if we have updated dri and drm what about Mesa
is th
On Thu, 2004-07-22 at 00:47, Donnie Berkholz wrote:
> On Thu, 2004-07-22 at 03:21, Eric Anholt wrote:
> > OK, so current DRI sources have been merged. Sorry for the CVS logs not
> > being clear on the mailing list, but what happened was that after I
> > noticed that the Mesa log was huge I went an
On Thu, 2004-07-22 at 03:21, Eric Anholt wrote:
> OK, so current DRI sources have been merged. Sorry for the CVS logs not
> being clear on the mailing list, but what happened was that after I
> noticed that the Mesa log was huge I went and turned off logging until
> after the conflict resolution.
OK, so current DRI sources have been merged. Sorry for the CVS logs not
being clear on the mailing list, but what happened was that after I
noticed that the Mesa log was huge I went and turned off logging until
after the conflict resolution. Probably should have turned it back on
before conflict
18 matches
Mail list logo
