On Sun, 8 Dec 2002 14:24:58 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
> Hi,
>
> as I reported earlier there seems to be a race condition in the Radeon
> driver when state is emitted while the card is processing vertices. Now
Keith, I just read your other message. Ok, so let's call it "failure" ;-)
> I narrowed it down to tex[0], tex[1] and tcl states that appear to
> require 3D to be idle. Can someone with Radeon specs confirm this? Other
That's exactly what you asked for :). More precisely, if TCL was
disabled I had to wait before emitting texture changes. If TCL was
enabled it was enough to wait before emitting TCL state. But this may be
due to the order of state changes. If TCL state is always emitted before
texture state, then waiting before the TCL state will also ensure that
3D is idle before the texture state change.
> state changes may not lock up the card but cause incorrect rendering. I
> havn't seen such behaviour, though. Again, what do the specs say?
You say, the card should know how to handle this. So if no one has seen
any problems so far, let's assume that's the case :)
> A refined patch for the user space driver is attached. A proper fix in
> the kernel would have to check the packet id in radeon_emit_packets
> (shared/drm/kernel/radeon_state.c) once we know exactly which packets
> are affected.
>
Felix
__\|/__ ___ ___ ___
__Tschüß_______\_6 6_/___/__ \___/__ \___/___\___You can do anything,___
_____Felix_______\Ä/\ \_____\ \_____\ \______U___just not everything____
[EMAIL PROTECTED] >o<__/ \___/ \___/ at the same time!
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
