On Tue, 5 Mar 2002, José Fonseca wrote:
> BTW, I've isolated the problem with the texture locking, it only happens
> when the code between if(mmesa->multitex) { .. } in the _tris is run.
> Don't know why. I've been trying to premult the texture coordinates,
> either within a new _vbtmp templat
On 2002.03.05 22:44 Leif Delgass wrote:
> On Tue, 5 Mar 2002 [EMAIL PROTECTED] wrote:
>
> > Tony,
> >
> > On 2002.03.05 21:04 Tony Rogvall wrote:
> > >
> > > Hi everyone!
> > >
> > > I am new on the list, I am currently struggling with getting the dri
> on
> > > my
> > > sony working. I have been
On Tue, 5 Mar 2002 [EMAIL PROTECTED] wrote:
> Tony,
>
> On 2002.03.05 21:04 Tony Rogvall wrote:
> >
> > Hi everyone!
> >
> > I am new on the list, I am currently struggling with getting the dri on
> > my
> > sony working. I have been able to set it up, compile and all that, but
> > there is so
Tony,
On 2002.03.05 21:04 Tony Rogvall wrote:
>
> Hi everyone!
>
> I am new on the list, I am currently struggling with getting the dri on
> my
> sony working. I have been able to set it up, compile and all that, but
> there is something missing. It looks to me that there is some pci
> support
Hi everyone!
I am new on the list, I am currently struggling with getting the dri on
my
sony working. I have been able to set it up, compile and all that, but
there is something missing. It looks to me that there is some pci
support
missing for the mach64 branch.
I hope I can do something, if j
Leif Delgass wrote:
>
> The mach64 driver with Mesa 3.x was using code like this (borrowed from
> utah-glx) to cull primitives:
>
> xx[0] = (GLint)(v0->v.x * 4);
> yy[0] = (GLint)(v0->v.y * 4);
>
> xx[1] = (GLint)(v1->v.x * 4);
> yy[1] = (GLint)(v1->v.y * 4);
>
> xx[2] = (GLint)(v3->v.x * 4);
I've added a new section to the FAQ regarding the suggested reading for
a newbie.
I would appreciate comments on it.
It can be reached at
http://mefriss1.swan.ac.uk/~jfonseca/dri/faq/html/getting-started.html#SUGGESTED-READING
Jose Fonseca
___
Dri-
Dieter Nützel wrote:
>> > Are you sure that 3D hardware acceleration is working right?
>>
>> Appearently not.
>> It locked up once tring anothe benchmark,
>> and neither agpgart, not r128 modules
>> got loaded when I restarted:(
>
> Try to rmmod most of your modules and then modprobe agpgart an
Just started using oprofile, from oprofile.sf.net -- It's good stuff... Not
vtune, but still good...
Keith
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
The mach64 driver with Mesa 3.x was using code like this (borrowed from
utah-glx) to cull primitives:
xx[0] = (GLint)(v0->v.x * 4);
yy[0] = (GLint)(v0->v.y * 4);
xx[1] = (GLint)(v1->v.x * 4);
yy[1] = (GLint)(v1->v.y * 4);
xx[2] = (GLint)(v3->v.x * 4);
yy[2] = (GLint)(v3->v.y * 4);
/* calculate
On Tuesday 05 March 2002 10:45, Jeff Hartmann wrote:
> I have no problem accepting the agpgart change, and I think its cleaner.
> We might want to modify that patch in the future so the old behavior
> can be selected, but thats not a big deal for now.
>
> Btw, do you have a working driver for the
I have no problem accepting the agpgart change, and I think its cleaner. We
might want to modify that patch in the future so the old behavior can be
selected, but thats not a big deal for now.
Btw, do you have a working driver for the HP IA64 chipset? If you do, it
might make sense to submit it
On Mon, Mar 04, 2002 at 09:41:38AM -0800, Ian Romanick wrote:
> On Mon, Mar 04, 2002 at 03:28:48AM +0100, Andreas Stenglein wrote:
>
> > I have this lockups with quake3arena, too.
> > I found a temporary (and slow) workaround: disable
> > the use of OpenGL-extensions in the q3a-setup-menu.
> > I
--- Leif Delgass <[EMAIL PROTECTED]> wrote: >
I commited a fix for single texturing which works
> now. Turns out the
> teximages weren't being marked for upload in
> UpdateTextureUnit, so
> UploadTexImages never got called. Multitexture is
Great. I was also hunting this problem.
> still not
I commited a fix for single texturing which works now. Turns out the
teximages weren't being marked for upload in UpdateTextureUnit, so
UploadTexImages never got called. Multitexture is still not working.
Multiarb makes my box hang.
I noticed some drm messages in the syslog that say "failed GU
Hi Michel,
Thanks for the speedy reply.
O.K. That got rid of the drm message and screen paint problem.
Now I am getting the following message when logging out from
KDE :
*** /var/log/messages ***
Mar 4 15:48:35 roglinux kernel: mtrr: no MTRR f
16 matches
Mail list logo
