Hello
I posted this last month on the dri-users list in hopes that I was doing
something wrong and would find out how to fix it. I eventually did fix it by
installing a matrox g450, and everything works. This pretty well rules out
any configuration issues and narrows it down to : radeon 7500
Hi
I dont know if its 'normal', but Quake3 seems to use about 50% CPU time
(framesync on) whilst running, with another 50% spent in the kernel.
any ideas why ?
___
Have big pipes? SourceForge.net is looking for download mirrors. We su
On Sunday 12 May 2002 01:15 pm, Leif Delgass wrote:
> this working, I've used buffer aging rather than interrupts. What I
> realized with interrupts is that there doesn't appear to be an interrupt
> that can poll fast enough to keep up, since a VBLANK is tied to the
> vertical refresh -- which i
On Sun, 12 May 2002, José Fonseca wrote:
> Leif,
>
> On 2002.05.12 19:15 Leif Delgass wrote:
> > Jose,
> >
> > I've been experimenting with this too, and was able to get things going
> > with state being emitted either from the client or the drm, though I'm
> > still having lockups and things a
On Sun, 12 May 2002, Keith Whitwell wrote:
> > > Just a small expansion on this. The texture management solution is
> > > weak. If two clients each had a small texture, it would be quite
> > > possible that they both would have fit in texture memory and no texture
> > > swapping would be required
"José Fonseca" wrote:
>
> Darryl,
>
> On 2002.05.12 19:11 Daryll Strauss wrote:
> > On Sun, May 12, 2002 at 05:27:26PM +0100, José Fonseca wrote:
> > > I would also appreciate any ideas regarding this. This is surely an
> > issue
> > > I would like to discuss further on the next meeting.
> >
> >
Hello,
I would like to know if anybody was able to run Maya 4 on a
Matrox G400
using DRI, it seems that Maya only support 3DLabs and nVidia cards. Any
clue
about running it on a G400?
Best regards,
- german
--
Send email with "SEND GPG KEY" as subject to rece
Leif,
On 2002.05.12 19:15 Leif Delgass wrote:
> Jose,
>
> I've been experimenting with this too, and was able to get things going
> with state being emitted either from the client or the drm, though I'm
> still having lockups and things are generally a bit buggy and unstable
> still. To try cli
Darryl,
On 2002.05.12 19:11 Daryll Strauss wrote:
> On Sun, May 12, 2002 at 05:27:26PM +0100, José Fonseca wrote:
> > I would also appreciate any ideas regarding this. This is surely an
> issue
> > I would like to discuss further on the next meeting.
>
> You're right, there's no automatic way to
Jose,
I've been experimenting with this too, and was able to get things going
with state being emitted either from the client or the drm, though I'm
still having lockups and things are generally a bit buggy and unstable
still. To try client side context emits, I basically went back to having
eac
Alan,
On 2002.05.12 17:35 Alan Hourihane wrote:
> Jose,
>
> I'd certainly forget using the gamma driver as any kind of template for
> any work.
>
> There are many unimplemented features, and multiple clients just don't
> work.
>
Ok. I wasn't aware of this.
> Purely a lack of time thing.
>
>
Jose,
I'd certainly forget using the gamma driver as any kind of template for
any work.
There are many unimplemented features, and multiple clients just don't
work.
Purely a lack of time thing.
Alan.
On Sun, May 12, 2002 at 05:27:26 +0100, Jos Fonseca wrote:
> As it becomes more clear that in
As it becomes more clear that in the mach64 the best solution is to fill
DMA buffers with the context state and the vertex buffers I've been trying
to understand how can this be done and how the Gamma driver (which has
this same model) does.
The context state is available right in the beginnin
On 2002.05.05 19:41 Frank C. Earl wrote:
> ...
>
> > I plan to build a test case for this, but I would like to hear
> preliminary
> > opinions about this, in case I'm missing something. Frank, have you
> tested
> > this before?
>
> Yes, pretty extensively, but I didn't have time to set up tests
You are fast, i never would have thought you would answer this fast!
Leif Delgass wrote:
>It looks like there's a problem with the drm initialization. Could you
>send the kmsg output with debugging turned on:
>
>close X
>become root
>rmmod mach64
>modprobe mach64 drm_opts=debug
>cat /proc/kmsg
15 matches
Mail list logo
