Vladimir Dergachev wrote:
Hi Aapo, Ben, Jerome, Nicolai:
I recently checked fresh code from CVS and was pleasantly surprised
to see that all Quake3 levels that were broken are now perfect - in fact
I cannot find anything that is amiss !
Do you think it would be a good idea to tag the
On 5/19/05, Keith Whitwell [EMAIL PROTECTED] wrote:
Vladimir Dergachev wrote:
Hi Aapo, Ben, Jerome, Nicolai:
I recently checked fresh code from CVS and was pleasantly surprised
to see that all Quake3 levels that were broken are now perfect - in fact
I cannot find anything that is
Felix Kühling [EMAIL PROTECTED] writes:
but I have next problem: X server locked after a few minutes playing in
quake2 ;( My computer do not react on mouse or keyboard activity... but
this is not bus lock --- mplayer is contining playing music and I can login
on the computer through SSH.
Jerome Glisse wrote:
Moreover i see that 9800 are reported to crash with the driver ? Is this
still true ?
Jerome Glisse
Yes, this is still very true. I've just rebuilt xorg, mesa and r300 from
cvs. I tested with glxgears and a couple of games. I've got a 9800 pro.
glxgears running alone
--- Adam Jackson [EMAIL PROTECTED] wrote:
On Wednesday 18 May 2005 23:53, Michel Dänzer wrote:
On Wed, 2005-05-18 at 22:47 +0100, Steven Newbury wrote:
1) When I move a window over a 3D rendering window the contents jumps to
the top left hand part of the display. If I move the output
--- Michel Dänzer [EMAIL PROTECTED] wrote:
On Wed, 2005-05-18 at 22:47 +0100, Steven Newbury wrote:
4) UseFBDev results in the following error and failed initialisation:
(EE) RADEON(0): FBIOPUT_VSCREENINFO: Invalid argument
Either you aren't running radeonfb, or it probably doesn't like
On 5/19/05, Boris Peterbarg [EMAIL PROTECTED] wrote:
Yes, this is still very true. I've just rebuilt xorg, mesa and r300 from
cvs. I tested with glxgears and a couple of games. I've got a 9800 pro.
glxgears running alone doesn't crash for a long time, but using anything
else in parallel (for
DRI is working on the R200 otherwise, I'm getting about 4200fps in glxgears,
not bad for an Athlon 1.4GHz and an Radeon 8500. I get about 540fps on the
MGA
G400MAX(overclocked) PIII/933MHz.
Would further details be usefull?
I've become skeptical that the r200 was ever truly stable... it
Jerome Glisse wrote:
-stencil
Stencil should work. GL_ATI_separate_stencil is not implemented
(hardware support it).
I think, fog is not implemented too.
Moreover i see that 9800 are reported to crash with the driver ? Is this
still true ?
I have 9500 Pro. Some opengl application locks
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=3267
--- Additional Comments From [EMAIL PROTECTED] 2005-05-19 05:35 ---
try
Jerome Glisse wrote:
Right now i am on pixel shader after doing some test i don't think we can
use a similar stuff like i915 emit arithm, i915 hardware are far more easier
to program than r300. I am coding another approach an hope to have it
done by the end of this week.
Moreover i see that 9800
Jerome Glisse wrote:
On 5/19/05, Keith Whitwell [EMAIL PROTECTED] wrote:
Vladimir Dergachev wrote:
Hi Aapo, Ben, Jerome, Nicolai:
I recently checked fresh code from CVS and was pleasantly surprised
to see that all Quake3 levels that were broken are now perfect - in fact
I cannot find
--- Steven Newbury [EMAIL PROTECTED] wrote:
--- Adam Jackson [EMAIL PROTECTED] wrote:
On Wednesday 18 May 2005 23:53, Michel Dänzer wrote:
On Wed, 2005-05-18 at 22:47 +0100, Steven Newbury wrote:
1) When I move a window over a 3D rendering window the contents jumps
to
the top
On Thursday 19 May 2005 09:20, Keith Whitwell wrote:
Vladimir Dergachev wrote:
Hi Aapo, Ben, Jerome, Nicolai:
I recently checked fresh code from CVS and was pleasantly surprised
to see that all Quake3 levels that were broken are now perfect - in fact
I cannot find anything that
On 5/19/05, Steven Newbury [EMAIL PROTECTED] wrote:
--- Michel Dänzer [EMAIL PROTECTED] wrote:
On Wed, 2005-05-18 at 22:47 +0100, Steven Newbury wrote:
4) UseFBDev results in the following error and failed initialisation:
(EE) RADEON(0): FBIOPUT_VSCREENINFO: Invalid argument
Either
Jerome Glisse wrote:
I've also been working on some fragment program stuff. I have attached what
I've done so far, which works quite well with Keith's texenv program
generation
that's in Mesa cvs. Not all arb_f_p opcodes are implemented, but I
think everything's
there that the texenv stuff
On Thu, 19 May 2005, Jerome Glisse wrote:
Thus what we may do is use this table or use your swizzle
function. Table lookup are faster but we doesn't have to translate
code often, no ?
An intermediate approach would be to have an if function that is easier
to read (and debug) but instead of using
I've also been working on some fragment program stuff. I have attached what
I've done so far, which works quite well with Keith's texenv program
generation
that's in Mesa cvs. Not all arb_f_p opcodes are implemented, but I
think everything's
there that the texenv stuff needs.
I was
On 5/19/05, Nicolai Haehnle [EMAIL PROTECTED] wrote:
On Thursday 19 May 2005 09:20, Keith Whitwell wrote:
Vladimir Dergachev wrote:
Hi Aapo, Ben, Jerome, Nicolai:
I recently checked fresh code from CVS and was pleasantly surprised
to see that all Quake3 levels that were broken
On Thu, 19 May 2005 12:13:17 +0100 (IST)
Dave Airlie [EMAIL PROTECTED] wrote:
DRI is working on the R200 otherwise, I'm getting about 4200fps in glxgears,
not bad for an Athlon 1.4GHz and an Radeon 8500. I get about 540fps on the
MGA
G400MAX(overclocked) PIII/933MHz.
Would further
On 5/19/05, Boris Peterbarg [EMAIL PROTECTED] wrote:
Well, I tried now - I have an old computer...well, the box anyway. Had
to switch all the cables between the two computers all the time.
First, the program that I ran consumed 100%. After killing it, X
consumed 100% and took about 15 minutes
On Thu, May 19, 2005 at 03:21:38PM +0200, khaqq wrote:
On Thu, 19 May 2005 12:13:17 +0100 (IST)
Dave Airlie [EMAIL PROTECTED] wrote:
I've become skeptical that the r200 was ever truly stable... it may be
less stable now .. I'm getting crsahes on my 9200 with multi-app also..
and I've
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2596
--- Additional Comments From [EMAIL PROTECTED] 2005-05-19 09:14 ---
Hi,
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=3217
--- Additional Comments From [EMAIL PROTECTED] 2005-05-19 09:25 ---
I
On 5/19/05, Vladimir Dergachev [EMAIL PROTECTED] wrote:
On Thu, 19 May 2005, Jerome Glisse wrote:
Thus what we may do is use this table or use your swizzle
function. Table lookup are faster but we doesn't have to translate
code often, no ?
An intermediate approach would be to have an
Jerome Glisse wrote:
I use a similar approach. v_swiz contains all the native r300 swizzle
values,
aswell as a couple of cases where we have to handle them specially. The
non-native cases have v_swiz-native set to GL_FALSE.
I saw that in code but you still got a loop and test case, your
On Thu, 19 May 2005, Jerome Glisse wrote:
On 5/19/05, Vladimir Dergachev [EMAIL PROTECTED] wrote:
On Thu, 19 May 2005, Jerome Glisse wrote:
Thus what we may do is use this table or use your swizzle
function. Table lookup are faster but we doesn't have to translate
code often, no ?
An intermediate
I use a similar approach. v_swiz contains all the native r300 swizzle
values,
aswell as a couple of cases where we have to handle them specially. The
non-native cases have v_swiz-native set to GL_FALSE.
I saw that in code but you still got a loop and test case, your
approach is well
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=1678
--- Additional Comments From [EMAIL PROTECTED] 2005-05-19 10:53 ---
Hi,
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=3337
Summary: ati radeon 7000 pci dri not working cruppted display and
remember)). 3D works for hours (original UT, Quake3) without
lockups, whereas newer snapshots for xorg (gentoo / linux 2.6.8.11 /
xorg 6.8.2) crash in less than a minute (and sometimes in seconds)
on the same PC. Q3A seems to take longer to crash than UT, but
that's a subjective
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=3217
--- Additional Comments From [EMAIL PROTECTED] 2005-05-19 15:22 ---
(In
On Thu, May 19, 2005 at 10:57:52PM +0100, Dave Airlie wrote:
Phil wrote:
fwiw, I've found the dri snapshot at nixnuts.net to be absolutely
stable with my 9200SE (rv280 chipset). I don't think I've had any
crashes at all. Mostly it gets used for a spot of Q3A or UT -- UT2003
is unbearably
Here's a refactor I did of the various drm_addbufs_* functions in
drm_bufs.c. Basically, I pulled all the common, boilerplate ioctl code
out of the individual functions into drm_addbufs. A side benefit (and
the actual reason I did the exercise) is that the drm_addbufs_* routines
can now be
I think you can spend a lot of time on this problem, but maybe we should
check some simpler things first:
* which 3D driver are you using? From Xorg CVS or Mesa CVS? The
latter one is the most up-to-date. With LIBGL_DEBUG=verbose you
can check which driver binary is being
35 matches
Mail list logo
