I have been monitoring the DRI since it first began and I have just
one question regarding the MGA driver.
I was wondering if you consider it to be functioning at the highest
performance that you can get out of it?
I ask this because I have been doing benchmarking and comparison between
Wi
FYI,
I know this isn't DRI related, but I sent this fix to the XFree86 folks
months ago and I
still see the buglet in CVS. Hopefully someone on here has clout.
Module dri/xc/programs/Xserver/hw/xfree86/input/joystick/xf86Jstk.c:
Search for the text "WACOM" and replace with "JOYSTICK". This is j
I've taken a stab at fixing the libglide3.so for Voodoo3 vs Voodoo5 problem.
Basically, the tdfx driver looks at the screen's device ID and either loads
libglide3-v3.so or libglide3-v5.so (filenames not finalized) with dlopen()
and initializes a table of per-context Glide function pointers accord
Around 12 o'clock on May 22, "Mike A. Harris" wrote:
>Yes, that supports depth switching. Although I think it does it by
>translating data to a native depth so the memory requirements are still
>there. Anyone else know for sure?
The frame buffer depth will change, existing windows will end up i
On Tue, 22 May 2001, Daryll Strauss wrote:
>> I will try to report things here in the future. My idea was by
>> doing it in the config tool, i could gage how things should be
>> constrained, and then patch X to avoid allowing combinations that
>> are unuseable.
>
>Well as a practical matter that
On Tue, 22 May 2001, Daryll Strauss wrote:
>> Right, but what I want is "Here are your options, and you cannot
>> choose DRI in a configuration that will make the machine lock up
>> due to memory constraints."
>
>We shouldn't lock up. That's a bug. We should fix it.
Ok, I wasn't completely sure
On Tue, May 22, 2001 at 12:07:44PM -0400, Mike A. Harris wrote:
> I will try to report things here in the future. My idea was by
> doing it in the config tool, i could gage how things should be
> constrained, and then patch X to avoid allowing combinations that
> are unuseable.
Well as a practic
On Tue, May 22, 2001 at 11:46:34AM -0400, Mike A. Harris wrote:
> On Tue, 22 May 2001, Daryll Strauss wrote:
>
> Right, but what I want is "Here are your options, and you cannot
> choose DRI in a configuration that will make the machine lock up
> due to memory constraints."
We shouldn't lock up.
On Tue, 22 May 2001, Alan Hourihane wrote:
>> >So, the calculation Brian listed is the minimum requirement for 3D to
>> >work in a given mode, but it isn't the maximum. Each board is different
>> >and may change as the code changes. You're not going to get one formula
>> >that says "With ram X an
On Tue, May 22, 2001 at 11:46:34AM -0400, Mike A. Harris wrote:
> On Tue, 22 May 2001, Daryll Strauss wrote:
>
> >> Then, you should have at least a couple megabytes left over for
> >> the X pixmap cache and for OpenGL textures.
> >
> >Please realize these are important and significant parts of t
On Tue, 22 May 2001, Daryll Strauss wrote:
>> Then, you should have at least a couple megabytes left over for
>> the X pixmap cache and for OpenGL textures.
>
>Please realize these are important and significant parts of the
>calculation. For example, in the tdfx driver you can be using up to 1MB
Brian Paul wrote:
>
> "Mike A. Harris" wrote:
> >
> > I would like to know given x Mb of video RAM on a given DRI
> > supported video card, how can I calculate what the maximum
> > screen resolution should be?
> >
> > width * height * fbbpp / 8 == 2D screensize
> >
> > I'll need to take virtual s
On Tue, May 22, 2001 at 08:23:21AM -0600, Brian Paul wrote:
> Then, you should have at least a couple megabytes left over for
> the X pixmap cache and for OpenGL textures.
Please realize these are important and significant parts of the
calculation. For example, in the tdfx driver you can be using
>From: "Mike A. Harris" <[EMAIL PROTECTED]>
>
>I would like to know given x Mb of video RAM on a given DRI
>supported video card, how can I calculate what the maximum
>screen resolution should be?
>
>width * height * fbbpp / 8 == 2D screensize
>
>I'll need to take virtual screen dimensions into ac
"Mike A. Harris" wrote:
>
> I would like to know given x Mb of video RAM on a given DRI
> supported video card, how can I calculate what the maximum
> screen resolution should be?
>
> width * height * fbbpp / 8 == 2D screensize
>
> I'll need to take virtual screen dimensions into account, as we
"Marcelo E. Magallon" wrote:
>
> Brian Paul wrote:
>
> > The DRI trunk code has a few problems with thread safety and
> > swapbuffers (all drivers but tdfx, probably). I've fixed this on
> > the 3.5 branch. You might try that.
>
> hmm... I picked the branch on a bad day it seems...
Do y
Brian Paul wrote:
> The DRI trunk code has a few problems with thread safety and
> swapbuffers (all drivers but tdfx, probably). I've fixed this on
> the 3.5 branch. You might try that.
hmm... I picked the branch on a bad day it seems...
#1 0x81ff980 in ?? ()
#2 0x406ccc7a in _tnl_run_
I would like to know given x Mb of video RAM on a given DRI
supported video card, how can I calculate what the maximum
screen resolution should be?
width * height * fbbpp / 8 == 2D screensize
I'll need to take virtual screen dimensions into account, as well
as double buffering, etc.
I'd like to
18 matches
Mail list logo
