On Sun, 2004-09-26 at 09:12, Nicolai Haehnle wrote:
> Hi,
>
> I'm trying to completely understand the command buffer stuff for my R300
> driver work, and I noticed something about the save_on_next_unlock code.
> I'm concerned about the state_atom::check function.
> The check functions use the cu
Hi,
I'm trying to completely understand the command buffer stuff for my R300
driver work, and I noticed something about the save_on_next_unlock code.
I'm concerned about the state_atom::check function.
The check functions use the current state of the context to figure out which
atoms must be em
Philipp Klaus Krause wrote:
Has anyone else experienced problems reading back depth values with
the r200 driver?
Whenever I read back a depth value from the right part
(about a seventh or eighth of the width) I get 1.0.
Reading back from other parts of the buffer works OK
as does software Mesa ever
