On Thu, Sep 17, 2009 at 1:13 PM, Alberto Milone <
<email address hidden>> wrote:
> Just a clarification on the issue:
>
> Removing the 3D driver (/usr/lib/dri/r600_dri.so) is a valid workaround
> and the debdiff that I attached in comment 132 prevents mesa from
> building that driver.
>
> We are still looking into the possibility to get a working 3D driver for
> r600 in time for Karmic. I can't promise anything though.
>
>
You should co-operate more with upstream when you try to get still in
development code to work. It would be nice to know what kernel modules code
you are using and what extra patches etc. People will be coming to complain
to upstream anyway so fixing bugs is easier there if there is more knowledge
what you are doing.
Did you try to revert the patch that hooked in blit to kernel copy
operation? It is known to be buggy in some hw still so better not to ship
that kind of change in Ubuntu until most of problems with blit code is
fixed.
On Thu, Sep 17, 2009 at 1:13 PM, Alberto Milone <
<email address hidden>> wrote:
> Just a clarification on the issue: dri/r600_ dri.so) is a valid workaround
>
> Removing the 3D driver (/usr/lib/
> and the debdiff that I attached in comment 132 prevents mesa from
> building that driver.
>
> We are still looking into the possibility to get a working 3D driver for
> r600 in time for Karmic. I can't promise anything though.
>
>
You should co-operate more with upstream when you try to get still in
development code to work. It would be nice to know what kernel modules code
you are using and what extra patches etc. People will be coming to complain
to upstream anyway so fixing bugs is easier there if there is more knowledge
what you are doing.
Did you try to revert the patch that hooked in blit to kernel copy
operation? It is known to be buggy in some hw still so better not to ship
that kind of change in Ubuntu until most of problems with blit code is
fixed.