Linked by Thom Holwerda on Wed 25th Jun 2008 09:49 UTC
Thread beginning with comment 320249
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/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2006-01-17
a) no stable ABI - this means that it's not guaranteed to work with new kernels until updated. Normally, Linux developers aren't crazy to adopt that strategy.
b) binary blob - it isn't scrutinized by multiple sides like the rest of kernel. Remember that Vista driver for nvidia caused up to 30% of total crashes in the last year, due to immaturity of drivers. In open source world, such experimental features wouldn't be accepted into a kernel before it stabilizes.
c) PITA - yes, installing the blob for each kernel can couse troubles, and it usually conflicts with libGL from Mesa. Also they sometimes lack certain features of current Xorg, or don't even support it at the time of release.
c) Progress - Having documentation and help from nvidia would be useful for development of DRI (DRM), Gallium etc. Because it's different hardware and it's good to take it's design into account when developing features like videocard memory management. Having at least basic 3D, EXA etc. support out of box is also a desired feature for Linux (and for user experience with it).