Linked by Thom Holwerda on Fri 9th Nov 2012 22:11 UTC
Permalink for comment 541849
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 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2010-07-16
"Protecting the integrity" by allowing some closed blobs to use dma-buf but not nvidia? Yes, all the SoC drivers that use dma-buf are closed. Sure they have a GPL component in the kernel, which is how they're allowed to use dma-buf, but that component won't do you much without the userspace blobs.
So there's no "protecting integrity" or "making a moral stance" or anything by keeping Nvidia out. It's that some vendors have managed to isolate just enough of their driver into a GPL component, while Nvidia can't because of how their driver is put together.
Also, the first two versions of dma-buf did not have those symbols exported as gpl-only: http://lists.freedesktop.org/archives/dri-devel/2012-October/029107...