Do you still see the artifacts with debugging and non-redirected output ?
If not it must be that R300 and later hardware requires delays in
command stream. This would be new - and difficult to debug without
specifications.
Yes, they are still there, but I think that they occur less often,
thoug
On Sat, 1 Jan 2005, Ben Skeggs wrote:
The gears seem to look normal now.
Without drm debugging I was able to resize the glxgears window without
lockups, but only while the r300_dri debug output wasn't redirected. With
glxgears 2>/dev/null, resizing the window caused a lockup.
The interesting t
The gears seem to look normal now.
Without drm debugging I was able to resize the glxgears window without
lockups, but only while the r300_dri debug output wasn't redirected.
With glxgears 2>/dev/null, resizing the window caused a lockup.
The interesting thing is that the artifacts still appear
r300_demo runs with or without this code (and without code in
radeon_state.c too)
>One more thing: try this code instead:
>
>if (IS_FAMILY_R300(dev_priv)) {
>BEGIN_RING( 6 );
>
>OUT_RING_REG(R300_RB3D_DSTCACHE_CTLSTAT, 0x0002);
>OUT_RING_REG(0x4F18, 0x0001); /*
One more thing: try this code instead:
if (IS_FAMILY_R300(dev_priv)) {
BEGIN_RING( 6 );
OUT_RING_REG(R300_RB3D_DSTCACHE_CTLSTAT, 0x0002);
OUT_RING_REG(0x4F18, 0x0001); /* Z cache? */
/* It seems a delay is needed */
On Fri, 31 Dec 2004, Peter Zubaj wrote:
Hi,
I played with it yesterday.
I have x11perf lockups too. And X sometimes crash (simply exits) to
login screen. I use FC3 and then when I do ctrl+alt+F1 (to get to
console) system freezes (few uppers rows are redrawn (maybe by console
text)), but no switch
On Fri, 31 Dec 2004, Boris Peterbarg wrote:
Hi Vladimir,
Just one question - are these the debugging messages that are supposed to
show if I don't add '2>/dev/null'?
Yes - they note the type of primitive and the amount of vertices being
sent to the hardware.
These message come from r300_render.
Hi,
I played with it yesterday.
I have x11perf lockups too. And X sometimes crash (simply exits) to
login screen. I use FC3 and then when I do ctrl+alt+F1 (to get to
console) system freezes (few uppers rows are redrawn (maybe by console
text)), but no switch to text mode.
When I uncomment these r
On Fri, 31 Dec 2004, Ben Skeggs wrote:
Cool ! Can you resize the window without lockups as well ?
No, I can't. I didn't think to test that until after my last email.
Okay, that wasn't quite true. I was just attempting to get the drm log of
what happened on the lockup and it was quite hard to p
Cool ! Can you resize the window without lockups as well ?
No, I can't. I didn't think to test that until after my last email.
Okay, that wasn't quite true. I was just attempting to get the drm log
of what happened on the lockup and it was quite hard to produce with drm
debugging on. I'm gues
Cool ! Can you resize the window without lockups as well ?
No, I can't. I didn't think to test that until after my last email.
This is very interesting - I see no artifacts on my computer. Could
you tell what resolution/colordepth are you running at ? How much
memory does your card have ?
Perha
On Fri, 31 Dec 2004, Ben Skeggs wrote:
Hello,
Well, this has progressed nicely since last time I checked in on it. Well
done.
I've tested the latest CVS on RV350 AP(0x4150) and it works without lockups.
Cool ! Can you resize the window without lockups as well ?
Although, while glxgears is runni
Hello,
Well, this has progressed nicely since last time I checked in on it.
Well done.
I've tested the latest CVS on RV350 AP(0x4150) and it works without
lockups. Although, while glxgears is running I seem to have artifacts
around the rest of my screen.
Also, vertex_shader.h and pixel_shade
Hi all,
New snapshot of r300_driver is available. Get it from CVS, tag
"rotating_gears"
Changes:
* code cleanup, do not clobber hardware state as much as before
* hook up projection matrix - displays actually rotating gears
* vertex buffer mode (not used by defaul)
P
14 matches
Mail list logo
