You could point out to them that if we've been able to write a kernel that's good enough for them, we should be able to write drivers that are good enough as well.
As for patents, you could point out that whether their product has open source drivers or not has no bearing on whether it's infringing any patents. They can keep their drivers as close as they want and still be hit with patent lawsuits.
In the desktop and server space, there are many huge open source programs these days, programs that are essential in the enterprise market, and none of them have been hit with patent lawsuits any more than proprietary software of similar nature has been. I fail to understand the logic that assumes opening up code suddenly makes one more vulnerable to patent lawsuits.
Posted May 27, 2011 11:00 UTC (Fri) by stevem (subscriber, #1512)
[Link]
The usual argument is that a lot of the patented stuff is not immediately visible with closed drivers, whereas if people give out source showing how various features of a GPU work then it makes it easier for others to spot infringements.
The GPU area is a total mess because of the patent bollocks: as always, the only people benefiting are the lawyers.
Updates from Linaro
Posted May 27, 2011 11:53 UTC (Fri) by wookey (subscriber, #5501)
[Link]
Indeed - that is excactly the argument given. Clearly code licencing has exactly zero effect on infringement status, but nevertheless people feel that at least if they only ever ship binaries it's harder to point the finger at any particular infringement. In practice there is probably some truth in that, but it seems a pretty ropey scheme to base a major plank of your business on.
Of course whilst we'd like open drivers we're not actually asking for them to hand over the source - just some specs so we can write our own. I think the fear there is that writing down enough detail to program the device also shows fairly clearly which patents might be being infringed. I have no idea of the truth or otherwise of that as my expertise in not in GPUs and their architecture/instruction sets.