On Mit, 2002-11-20 at 16:56, Adam K Kirchhoff wrote:
On 20 Nov 2002, Michel [ISO-8859-1] Dänzer wrote:
On Mit, 2002-11-20 at 00:38, Adam K Kirchhoff wrote:
heretic2 has some problems, but they also show up in the trunk :-)
Basically, any sort of flashing (like if my character throws
On Mit, 2002-11-20 at 22:04, Martin Spott wrote:
Brian wrote:
Adam K Kirchhoff wrote:
So I decided to give the mesa-4-1-branch a whirl and do some testing... I
grabbed it from CVS:
$ cvs -z3 co -r mesa-4-1-branch xc
Do a CVS update again in case you didn't get my latest check-ins.
On Wed, 20 Nov 2002, Ian Romanick wrote:
On Tue, Nov 19, 2002 at 11:06:16PM -0800, Linus Torvalds wrote:
On Wed, 20 Nov 2002, Dieter Nützel wrote:
Am Mittwoch, 20. November 2002 00:55 schrieb Ian Molton:
Linus updated 2.5.48 with Brian's latest DRM r200 stuff so I
Hi!
I've done some more testing on the mesa-4-1-branch (checked out and
compiled yesterday)
All in all everything runs quite nicely and stable. I successfully tested:
-quake (quakeforge-0.5.2): works, but quite sluggish, especially when
there are lots of light effects
-quake2 (quakeIIforge
Adam K Kirchhoff wrote:
On Wed, 20 Nov 2002, Ian Romanick wrote:
On Tue, Nov 19, 2002 at 11:06:16PM -0800, Linus Torvalds wrote:
On Wed, 20 Nov 2002, Dieter N?tzel wrote:
Am Mittwoch, 20. November 2002 00:55 schrieb Ian Molton:
Linus updated 2.5.48 with Brian's latest DRM r200 stuff so I
On Sun, Oct 27, 2002 at 04:44:34PM +0100, Felix Kühling wrote:
But this way you waste lots of CPU cycles on frames which are never
displayed. Wouldn't be waiting (IRQ) for the pageflip to occur before
you render the 3rd frame in the above example a better approach?
What's the point of
Title: New ATI FireGL drivers announced
Hello,
i know that DRI is targeting open source development,
but i know myselves that for a developer there can
always be a need for a 2nd source driver reference.
There are several other reasons why an alternate
Linux driver might be of interest for
On Thu, 21 Nov 2002 12:14:20 +0100
Marcelo E. Magallon [EMAIL PROTECTED] wrote:
What's the point of trying to display 120 Hz if you monitor can only
do 85 Hz?
the faster you render, the lower your latency. its pointless for 3D
modelling / artwork, but very nice for 3D games.
On Thu, Nov 21, 2002 at 04:33:47PM +0100, Alexander Stohr wrote:
Hello,
i know that DRI is targeting open source development,
but i know myselves that for a developer there can
always be a need for a 2nd source driver reference.
There are several other reasons why an alternate
Linux driver
On Thu, Nov 21, 2002 at 08:28:01AM -0500, Adam K Kirchhoff wrote:
On Wed, 20 Nov 2002, Ian Romanick wrote:
On Tue, Nov 19, 2002 at 11:06:16PM -0800, Linus Torvalds wrote:
On Wed, 20 Nov 2002, Dieter Nützel wrote:
Am Mittwoch, 20. November 2002 00:55 schrieb Ian Molton:
Hi all,
i have a problem with the R128 driver: when i launch X from a normal
user, the XFree driver r128 is loaded, but when i launch an openGL
application like glxinfo i get this output:
name of display: :0.0
drmR128GetParam (R128_PARAM_IRQ_NR): -13
Segmentation fault
The lsmod output shows
I asked about this on dri-users but I think it may
be better placed here.
I was just browsing around the developer relations
areas of the ATI and Matrox sites, and I'm getting
the impression that they don't really care about having
open source DRI drivers available for their products.
Are these
On Thu, 21 Nov 2002, Ian Romanick wrote:
On Thu, Nov 21, 2002 at 08:28:01AM -0500, Adam K Kirchhoff wrote:
On Wed, 20 Nov 2002, Ian Romanick wrote:
The problem is that it uses EXT_texture_env_dot3 (which the driver does
advertise), but the driver doesn't actually implement only
On Thu, Nov 21, 2002 at 11:57:32AM -0500, Adam K Kirchhoff wrote:
On Thu, 21 Nov 2002, Ian Romanick wrote:
On Thu, Nov 21, 2002 at 08:28:01AM -0500, Adam K Kirchhoff wrote:
On Wed, 20 Nov 2002, Ian Romanick wrote:
The problem is that it uses EXT_texture_env_dot3 (which the
I just ran FlightGear with this branch (instead of employing binary
snapshots) on my Radeon7500. Everything is quite fast, the colours look
perfect, the previously known feature of everything appearing too dark has
gone !
Hmmm, today I had to realize that this is still dependend on the
Let me express that i do _not_ object to any of the DRI-Devel works.
DRI did great job and it resolves for situations where ATI
cant provide solutions as of today and possibly long term.
Just saying embedded Radeon chipsets, ATI chipsets on BSD,
old ATI chipsets prior to the R200 and further
On Wed, 20 Nov 2002, Linus Torvalds wrote:
On Thu, 21 Nov 2002, Dieter Nützel wrote:
Option AGPFastWrite 1
This just makes the machine lock up for me at X startup.
same here, instant and nasty lockup.
Ingo
---
This
On Thu, Nov 21, 2002 at 01:27:03PM -0500, Adam K Kirchhoff wrote:
Hmmm... Well, line 592 of scene.cpp (in glaxium 0.5, just downloaded from
the website) seems to be:
glEnable(GL_TEXTURE_2D);
Line 586, though, makes reference to GL_DOT3_RGB_EXT. I've made the
change there.
Now,
On Thu, Nov 21, 2002 at 05:50:51PM +0200, Pasi Kärkkäinen wrote:
|
| Quote from the webpage (URL above):
|
| The new unified driver provides robust OpenGL® 2.0 support for many of ATIs
| award-winning graphics boards including:
|
|
| Does these drivers _really_ have OGL 2.0 support?
Couldn't
Title: New ATI FireGL drivers announced
with
the last drivers i got a 'third party chipset or board not suported ' ??? but
all radeon 8500 are not built by ati !!!
-Mensagem original-De:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Em nome de Alexander
StohrEnviada:
On Thu, Nov 21, 2002 at 05:50:51PM +0200, Pasi Kärkkäinen wrote:
|
| Quote from the webpage (URL above):
|
| The new unified driver provides robust OpenGL® 2.0 support for many of ATIs
| award-winning graphics boards including:
|
|
| Does these drivers _really_ have OGL 2.0 support?
ATI says
By reading the readme, xinerma+dri is not yet supported. Is support
planned for this? if so, when?
that's something that'll have to be built into the core X infrastructure,
from what I hear.
maybe X 5.0 will have some capability for that; but don't hold your breath.
if you need it, try XiG's
Title: RE: [Dri-devel] New ATI FireGL drivers announced
By reading the readme, xinerma+dri is not yet supported. Is support
planned for this? if so, when?
To be honest, i just dont know because i am
not that deeply involved in 2D development.
Anyways, i wouldnt be allowed to talk about
On Thu, 21 Nov 2002, Ian Romanick wrote:
On Thu, Nov 21, 2002 at 01:27:03PM -0500, Adam K Kirchhoff wrote:
Hmmm... Well, line 592 of scene.cpp (in glaxium 0.5, just downloaded from
the website) seems to be:
glEnable(GL_TEXTURE_2D);
Line 586, though, makes reference to
Hi
Does this driver works with Powered By Ati cards??
The previus driver didnt work giving the error that is not a Build By Ati
card. Here in my City is impossible to find a BBA ATI, so i had to buy a
Powercolor (powered by) ATI 8500. The nvidia binary only driver works with
any brand of card
I only think it works with built by ati cards, howeverI don't have a
built by ati card and I was able to get it to work, but you risk
damaging your card. What you have to do is get a built by ATI Bios and
burn it to your card, and then you got yourself a Power By ATI Card that
says it was
Hello,
I was quite surprised to see that my OpenGL application ran about 3x
slower with the latest DRI drivers (last week's CVS) and my brand new
Radeon 7500 AIW card. I think I tracked it down to
glDrawBuffer(GL_NONE) when drawing to Z buffer is enabled. I guess
this is a software fallback case;
Leif,
Attached is the patch to allocate private DMA and ring buffers on the
DDX - the DDX part only. I'll now focus on the DRM part.
The code compiles but I'll only be able to test it when the changes on
DRM are also done. I would appreciate if you used those falcon eyes of
yours and see if you
WOULD YOU LIKE TO HAVE YOUR MESSAGE SEEN BY OVER
14.9 MILLION TARGETED PROSPECTS DAILY?
Below contains all the information you will ever need to market your product or
service on the Internet.
If you have a product, service, or message that you would like to get out
to Thousands, Hundreds of
On Thu, 21 Nov 2002, [iso-8859-15] José Fonseca wrote:
Leif,
Attached is the patch to allocate private DMA and ring buffers on the
DDX - the DDX part only. I'll now focus on the DRM part.
I didn't get the attachment, could you send it again?
The code compiles but I'll only be able to
On Thu, 21 Nov 2002, Alexander Stohr wrote:
I tried XVideo support and it showed that the CPU usage of TOP
was higher than that of the video player application. Features
that you will on FireGL boards are Overlays and PBuffer rendering
support.
This is getting off-topic but, FYI, X-Video
Never mind. I'm wrong.
Adam
On Thu, 21 Nov 2002, Adam K Kirchhoff wrote:
On Thu, 21 Nov 2002, Alexander Stohr wrote:
I tried XVideo support and it showed that the CPU usage of TOP
was higher than that of the video player application. Features
that you will on FireGL boards are
On Thu, Nov 21, 2002 at 05:41:55PM -0500, Leif Delgass wrote:
On Thu, 21 Nov 2002, [iso-8859-15] José Fonseca wrote:
Leif,
Attached is the patch to allocate private DMA and ring buffers on the
DDX - the DDX part only. I'll now focus on the DRM part.
I didn't get the attachment,
33 matches
Mail list logo
