On Sun, 2012-09-16 at 15:21 +0200, Marek Olšák wrote:
> You may try to move the call to r600_init_atom in
> evergreen_init_state_functions before the other atoms or experiment
> what positions works you.
I've tried to reorder the atoms but it doesn't help. Also I've noticed
that lockup only happen
You may try to move the call to r600_init_atom in
evergreen_init_state_functions before the other atoms or experiment
what positions works you.
Marek
On Sun, Sep 16, 2012 at 3:12 AM, Vadim Girlin wrote:
> Hi Marek,
>
> It seems after this patch something goes wrong for me on juniper - I've
> got
Hi Marek,
It seems after this patch something goes wrong for me on juniper - I've
got lockups with longprim test (when running with '-auto'). I don't see
anything wrong in the patch itself, so I guess it's order of writes or
something like that, maybe even not directly related to this patch but
un
---
src/gallium/drivers/r600/evergreen_hw_context.c |4 --
src/gallium/drivers/r600/evergreen_state.c |1 +
src/gallium/drivers/r600/r600_blit.c|4 +-
src/gallium/drivers/r600/r600_hw_context.c |7 ++--
src/gallium/drivers/r600/r600_pipe.h| 45 ++
