On Sunday 13 January 2002 11:50 pm, Gareth Hughes wrote:
> > While we're discussing things here, can anyone tell me why
> > things like the emit state code is in the DRM instead of in
> > the Mesa drivers? It looks like it could just as easily be
> > in the Mesa driver at least in the case of th
Frank C. Earl wrote:
>
> While we're discussing things here, can anyone tell me why
> things like the emit state code is in the DRM instead of in
> the Mesa drivers? It looks like it could just as easily be
> in the Mesa driver at least in the case of the RagePRO code-
> is there a good reason
On Tuesday 08 January 2002 04:12 pm, Leif Delgass and Manuel Teira wrote:
> Happy New Year!
Hopefully for all, it will be a better one than the last...
> > Well, after the holidays, I would like to recover the development in the
> > mach64 branch. I started today to investigate the DMA stuff be
> From: Manuel Teira <[EMAIL PROTECTED]>
> But, are you able to play Quake3 decently at 1024x768 with your mach64?
> That's what I wanted to mean, perhaps it's too work for our little rage.
The Utah-GLX drivers made Quake III Arena *just* playable on Mach64,
with an 8MB Rage Pro ... I've been
Brian Paul wrote:
> Nick Hudson wrote:
> >
> > My libglide3.so is located in /usr/lib.
> >
> > Could this have something to do with it?
> > > > libGL error: dlerror() message: /usr/lib/libglide3.so: undefined
> > > > symbol: \
> > > > _trisetup_3DNow_win_nocull_valid
> >
> > I donno but its ther
