| 1 |
On Dienstag 25 August 2009, Nikos Chantziaras wrote: |
| 2 |
> On 08/25/2009 03:54 AM, Volker Armin Hemmann wrote: |
| 3 |
> > On Dienstag 25 August 2009, Nikos Chantziaras wrote: |
| 4 |
> >> Only Catalyst has this problem. The open source Radeon drivers are fine |
| 5 |
> >> (and of course NVidia's closed drivers and everything Intel is fine |
| 6 |
> >> too). It's one of those Catalyst bugs that are there for several years |
| 7 |
> >> but one bothers fixing. |
| 8 |
> > |
| 9 |
> > nvidia was not fine for a long time - and since nvidia replaces a lot of |
| 10 |
> > x and kernel funtionailty within their driver I would not be surprised if |
| 11 |
> > they replaced the offending parts too. Intel is not hit, because it is |
| 12 |
> > their patch that made their life splendid and everybody else bad. |
| 13 |
> |
| 14 |
> And what about the two open source drivers? (radeon and radeonhd.) |
| 15 |
> They don't suffer either, and they're not Intel. |
| 16 |
|
| 17 |
they start/started to suffer as soon as they use(d) acceleration. As long as |
| 18 |
everything is done by the cpu in system memory and just the results copied |
| 19 |
into the framebuffer everything seems to be fine and dandy . |
| 20 |
|
| 21 |
bridgeman and others explained it in several threads on the phoronix forum. |
| 22 |
Start with the ask ati devs thread and then look at the other threads |
| 23 |
featuring bridgeman. |
Archives