> I put the page together after trying to walk thru several
> people with buggy Redhat installs. For some reason things like ldd or
> strace are not as well known to new users as they should be.
The problem here is not so much that people don't know about LDD, but that
they should not have to kn
I've made some corrections and included a link to DRI documentation area.
Michel: I don't mind if you fold this into dri guide or mirror it or
something. I put the page together after trying to walk thru several
people with buggy Redhat installs. For some reason things like ldd or
strace are n
I have made the correction - please let me know if I missed anything.
Vladimir Dergachev
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
On Thursday 21 June 2001 14:55, Michel Dänzer mentioned:
> Jordan Crouse wrote:
> > I am running Linux 2.4.5-ac16 and XFree86 4.1.0 with an ATI Rage Mobility
> > LF Rev 2 chipset (Renderer string: Mesa DRI Rage 128 20010405 M3 AGP 2x
> > x86/MMX/SSE) and I am getting the the old familiar "black f
Jordan Crouse wrote:
> I am running Linux 2.4.5-ac16 and XFree86 4.1.0 with an ATI Rage Mobility LF
> Rev 2 chipset (Renderer string: Mesa DRI Rage 128 20010405 M3 AGP 2x
> x86/MMX/SSE) and I am getting the the old familiar "black flicker" problem.
> Unfortunately, the old familar Option "UseCCE
Is there a lot of people experiencing problems getting this patch
running correctly? As I said, the patch needs to be applied on a fresh
install of XFree86 4.1.0 and disabledEXTCompiledVertexArray should be
set to "1" in the ClientPrefs file for Tribes2 players.
It is important to make this cl
On Thu, 21 Jun 2001, Jens Owen wrote:
> Vladimir,
>
> Your page looks very helpful. Thanks for putting it together. The only
> comment I have is regarding your first miscellaneous comment:
>
> "While hardware 3d is active nothing except your Xserver should be
> accessing your video card - o
All -
I am running Linux 2.4.5-ac16 and XFree86 4.1.0 with an ATI Rage Mobility LF
Rev 2 chipset (Renderer string: Mesa DRI Rage 128 20010405 M3 AGP 2x
x86/MMX/SSE) and I am getting the the old familiar "black flicker" problem.
Unfortunately, the old familar Option "UseCCEFor2D" "true" tric
Hello.
I've been looking for a programmer's manual or some documentation of this
kind, for the ATI Mach64 chipset.
I'm looking for something in the style of the Intel i810 Chipset Family
Programmers Reference Manual (Ref: 298026-001).
Do you know about any document of this kind? Has ATI releas
Brian Paul wrote:
> No need to bump version number as this value isn't used anywhere in
> the kernel module.
Speaking of a version bump, it looks like the _major_ of the r128 driver in
the trunk needs to be bumped (see discussion on the Xpert list). I'm reluctant
to do it myself as I don't h
Gareth Hughes writes:
> Memory allocation. It's hard to get a large chunk of physically
> contiguous memory, which the MGA needs to do PCI DMA. Not impossible,
> just a low priority. It would be nice to not just have a hacked-up
> solution like the Utah-GLX driver.
There are systems where
Jaakko Niemi wrote:
>
> >From: Karl Lessard
> >Subject: Re: [Dri-devel] GL_DECAL and texture corruption fixes for MGA driver
> >Date: Mon, 18 Jun 2001 08:28:46 -0700
> >
> >
> >
> >You're right, mgaConvertTexture needs to handle RGB5_A1 as a special
> >case. But there is no need to redefined MGAP
>From: Karl Lessard
>Subject: Re: [Dri-devel] GL_DECAL and texture corruption fixes for MGA driver
>Date: Mon, 18 Jun 2001 08:28:46 -0700
>
>
>
>You're right, mgaConvertTexture needs to handle RGB5_A1 as a special
>case. But there is no need to redefined MGAPACKCOLOR1555, check
>MGAPACKCOLOR
Geoff Reedy wrote:
>
> On Wed, Jun 20, 2001 at 01:50:03PM -0400, Karl Lessard <[EMAIL PROTECTED]> said
> >
> > There is a AGP-to-PCI bridge on a G450 PCI. The thing is that you have a
> > AGP chip on your PCI card , and the bridge is used to connect the chip
> > on a PCI bus. But I don't know why
On Wed, Jun 20, 2001 at 01:50:03PM -0400, Karl Lessard <[EMAIL PROTECTED]> said
>
> There is a AGP-to-PCI bridge on a G450 PCI. The thing is that you have a
> AGP chip on your PCI card , and the bridge is used to connect the chip
> on a PCI bus. But I don't know why DRI only supports AGP cards,
I've been banging my head on this for too long without much luck. Karl,
can you send me (and me only) a snapshot of Mesa/demos/texenv running
with your patch applied? I'm getting incorrect rendering no matter what
I do, and Tribes2 is still broken (the landscape is clearly being
textured incorre
Brian Paul wrote:
>
> That's what I was worried about. Changing the SAREA layout would
> require bumping the version number. However, I've grepped all the
> Radeon sources and it doesn't appear that RADEON_MAX_TEXTURE_LEVELS
> is used at all in the SAREA or kernel code. I'll have to do some
>
Gareth Hughes wrote:
>
> Brian Paul wrote:
> >
> > I've looked into this a bit more. Looks like the token
> > is incorrectly defined to be 11 in
> > the current driver. It should be 12 in order to support 2Kx2K
> > textures. It looks like this can safely be changed from 11 to 12
> > without a
Philip Willoughby wrote:
>
> Just out of interest, does 2kx2k texture support mean 2048x2048 or 2050x2050
> (for borders?).
I have never seen a graphics chip accelerate texture borders. All the
Mesa-based drivers fall back to software rendering if you have them.
-- Gareth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Gareth Hughes wrote:
>Brian Paul wrote:
>>
>> I've looked into this a bit more. Looks like the token
>> RADEON_MAX_TEXTURE_LEVELS is incorrectly defined to be 11 in
>> the current driver. It should be 12 in order to support 2Kx2K
>> textures
Fredrik Hegardt wrote:
> Will using the matrox framebuffer cause me problems trying to use DRI?
Possible. Some people tend to blame framebuffer devices for everything. ;)
> I have:
>
> X410
> Matrox G450
>
> Have tried everything and still can't get any OpenGL-apps to run. (The apps
> are lin
On Thu, 21 Jun 2001, Michel Dänzer wrote:
> [EMAIL PROTECTED] wrote:
> >
> > I've put up a "Guide to debugging DRI installations" at
> >
> > http://www.linuxvideo.org/gatos/dri-debug.html
Excellent!
>
> I wonder if this is really necessary? Wouldn't it be better to point at the
> DRI user guid
Hello!
Will using the matrox framebuffer cause me problems trying to use DRI?
I have:
X410
Matrox G450
Have tried everything and still can't get any OpenGL-apps to run. (The apps are
linked to the correct libGL, libGLU; DRI is enabled according to the X-log and
Glxinfo). Gears hangs the mac
[EMAIL PROTECTED] wrote:
>
> I've put up a "Guide to debugging DRI installations" at
>
> http://www.linuxvideo.org/gatos/dri-debug.html
I wonder if this is really necessary? Wouldn't it be better to point at the
DRI user guide and improve it if needed? We all know the bad aspects of
duplicatio
24 matches
Mail list logo
