Linked by Thom Holwerda on Tue 14th Sep 2010 22:42 UTC
Ubuntu, Kubuntu, Xubuntu If there's one consistent piece of criticism that gets lobbed in Canonical's and Mark Shuttleworth's direction, it's that they do not contribute enough code - or anything else for that matter - to the Free software world. Mark Shuttleworth has apparently had enough, and has written a very, very lengthy blog post detailing how he feels about this criticism.
Thread beginning with comment 441250
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: duh
by lemur2 on Thu 16th Sep 2010 02:14 UTC in reply to "RE: duh"
lemur2
Member since:
2007-02-17

Look at the recent problems with KWin 4.5: Those aren't bugs in KWin. Those are driver bugs.
Nothing more recent than OpenGL 2.0 is supported by FOSS drivers and even that support is buggy.


Well it should be pointed out that for the ATI FOSS drivers the programming specifications have only been available for just over a year now. ATI FOSS drivers are entirely new code (AMD/ATI did NOT release their driver code as FOSS, only the programming specifications).

OpenGL support in FOSS drivers (at least, for the ATI FOSS drivers) is buggy because it is so new. It will improve in very short order as the driver gains a bit of maturity.

Reply Parent Score: 2

RE[3]: duh
by Fettarme H-Milch on Thu 16th Sep 2010 13:35 in reply to "RE[2]: duh"
Fettarme H-Milch Member since:
2010-02-16

Well it should be pointed out that for the ATI FOSS drivers the programming specifications have only been available for just over a year now. ATI FOSS drivers are entirely new code (AMD/ATI did NOT rel
ease their driver code as FOSS, only the programming specifications).

OpenGL support in FOSS drivers (at least, for the ATI FOSS drivers) is buggy because it is so new. It will improve in very short order as the driver gains a bit of maturity.

And how does code get marture? By having people to work on it.
Novell worked a while on radeonhd but ever since AMD chose to support the normal radeon driver, Novell stopped to work on radeonhd.
To make matters worse, financial trouble of Novell meant that the radeonhd developer was fired.
That leaves the situation in the following way: AMD works on the driver but only with the barest minimum of resources and only after AMD's slow "Legal Team" gives its OK to work on certain driver features.
Distributors could stept in and at least help stabilizing existing features but Novell currently can't (so they say), Red Hat puts its resources to Nouveau (where they are even more needed), and Canonical simply does nothing.

Reply Parent Score: 3