| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 20 Mar 2009 15:00:32 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Greg KH <greg@...ah.com> Cc: Daniel Stone <daniel@...ishbar.org>, Sindhudweep Sarkar <sindhudweep.sarkar@...il.com>, David Airlie <airlied@...ux.ie>, Thomas Hellstrom <thellstrom@...are.com>, dri-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org, Richard Purdie <rpurdie@...ux.intel.com> Subject: Re: [patch 0/5] Intel Poulsbo/Morrestown DRM driver and DRM core changes > > By the same logic, would you support including the proprietary NVIDIA > > driver while we wait for Nouveau to catch up? > > The license of the NVIDIA driver does not allow that to even be a > possibility. I'm not convinced this is any different. If you accept the 3D changes you step into a dangerous world of estoppel and since it has many rightsholders also the wonderful world of contributory infringement. It really really needs lawyers to look into it. Now the other way to do it that might be more productive and simpler would be to rip all the 3D crap out of that driver and just include the minimum needed 2D bits for the open source X driver. Makes the code smaller and cleaner, avoids an legal questions and lets people get on with real work. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists