From: Valdis.Kletnieks@vt.edu
To: "Fredrik Markström" <fredrik.markstrom@avalonenterprise.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Developing non-commercial drivers ?
Date: Tue, 18 Nov 2008 14:25:33 -0500 [thread overview]
Message-ID: <63125.1227036333@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 18 Nov 2008 17:16:44 +0100." <fc262dee0811180816k29cc93aas51c2c47ede2c7a1@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On Tue, 18 Nov 2008 17:16:44 +0100, =?ISO-8859-1?Q?Fredrik_Markstr=F6m?= said:
> 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.
Am I the only one that's boggled by the concept of a company that can develop
an entire CPU architecture and be OK on the GPL licensing of all the code
in arch/new-foo-cpu that exposes the IP of the cpu design, but they're worried
about the special sauce in a freakin' *ethernet controller*?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-11-18 19:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 16:16 Fredrik Markström
2008-11-18 16:29 ` Robert Hancock
2008-11-18 16:52 ` Fredrik Markström
2008-11-18 17:04 ` Robert Hancock
2008-11-18 17:17 ` Xavier Bestel
2008-11-18 17:17 ` Chris Friesen
2008-11-18 18:00 ` Radhakrishnan
2008-11-18 18:13 ` Chris Friesen
2008-11-18 18:33 ` linux-os (Dick Johnson)
2008-11-18 17:40 ` Alan Cox
2008-11-22 18:16 ` Dr. David Alan Gilbert
2008-11-18 17:32 ` Alan Cox
2008-11-18 19:25 ` Valdis.Kletnieks [this message]
2008-11-18 19:29 ` Alan Cox
2008-11-18 20:20 ` Theodore Tso
2008-11-18 21:13 ` Fredrik Markström
2008-11-18 23:28 ` Theodore Tso
2008-11-19 18:38 ` Lennart Sorensen
2008-11-19 22:32 ` Fredrik Markström
2008-11-19 22:47 ` Lennart Sorensen
2008-12-01 0:19 ` Enrico Weigelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63125.1227036333@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=fredrik.markstrom@avalonenterprise.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®