linux-kernel - Developing non-commercial drivers ?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 18 Nov 2008 17:16:44 +0100
From:	"Fredrik Markström" 
	<fredrik.markstrom@...lonenterprise.com>
To:	linux-kernel@...r.kernel.org
Subject: Developing non-commercial drivers ?

Linus, others...

I'm working for as a consultant for a large hardware company porting
Linux to their new cpu-architecture and everything is pretty much
up and running. Now they want us to develop a closed-source (to
protect their IP) ethernet driver for their proprietary Ethernet MAC.

My question is:    Is there a fair way to do this and still comply to
the intent and spirit of the Linux licensing ?

If yes, how ?

/Fredrik
--
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/