Linked by Thom Holwerda on Sun 20th Apr 2008 12:52 UTC, submitted by Michael Larabel
Permalink for comment 311055
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2006-03-20
Hahahaha. In the bad old Xfree86 days, Xfree86 had a stable API. In fact, it was so stable that nobody had been able to implement significant improvements for over a decade. This is why the Nvidia people gave up on them and wrote their *own* 2d acceleration framework for their linux drivers, and they wrote their *own* kernel acceleration infrastructure for their linux drivers.
The innability for Linux (or any other unix) to set (or stick to) standards is the reason why this sort of thing has lagged for over a decade.
Actually, no. The fact that Xfree86 was run by a**hats who had no clue of how to run a project, scared away all their developers, and did jack to actually improve the state of the art is the reason that this has lagged for over a decade.
The willingness of the Linux people to break their API and get things working is why they're able to do kernel modesetting at all -- kernel modesetting is yet another API and ABI break for the Xorg drivers that want to take advantage of it. It's a significant change to DRI.