Linked by Thom Holwerda on Fri 13th Nov 2009 17:01 UTC
Thread beginning with comment 394478
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2006-12-20
I'm not entirely sure how closely the graphics drivers tie in to X on Linux, but even if Chrome's display system can use the existing drivers, there could still be problems. When KDE 4 first came out, there were a lot of problems caused by the fact that KDE was doing things (graphics-wise) that weren't commonly done on the Linux desktop at the time. This caused a lot of weak points in the drivers to be exposed, where functionality which was previously rarely-touched was being more thoroughly exercised.
I believe this was particularly the case with the nVidia binary drivers (which I use and recommend), but the drivers were actually fixed fairly quickly. I remember Aaron Seigo saying at the time that it was necessary for KDE to push the limits of what the drivers were capable of in order to exert pressure to get the drivers improved. It seemed to work from the nvidia end of things, anyway.