On Mon, Jun 23, 2008 at 03:02:58PM +0200, Matthew wrote:I think that's one of the reasons of Greg's post. (...) You're wrong here. If they have patented routines, they don't need their drivers to be closed, since there routines are protected by patents. And even if they are not patented, not releasing the source will not prevent a competitor from disassembling the code anyway. So there's really no point in remaining closed. Some of them might have signed NDAs before using some technologies, but by this time, they should have sorted that our. Do you know many products with closed Linux drivers which are not supported by at least one closed OS ? If they chose to support Linux, it's not for your pleasure, just because they know they will sell 5-10% more when a penguin is stuck on the box. That has nothing to do with open/close. They may as well continue to use their dirty hacks when the sources are public. That just means that owners of such cards on other platforms (PPC, etc...) might be able to build the drivers for those platforms. I think that most users don't care about the fact that a driver is dirty. They want something which simply builds for their platform. Also, publishing their dirty hacks will encourage kernel developers to propose some cleaner alternatives or to extend the kernel in order to ease integration of such drivers. Willy --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Kamalesh Babulal | [BUILD-FAILURE] 2.6.26-rc8-mm1 - build failure at drivers/char/hvc_rtas.c |
| Luciano Rocha | usb hdd problems with 2.6.27.2 |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Christoph Lameter | Network latency regressions from 2.6.22 to 2.6.29 |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
git: | |
