From: "Fredrik Markström" <fredrik.markstrom@avalonenterprise.com>
To: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Developing non-commercial drivers ?
Date: Wed, 19 Nov 2008 23:32:04 +0100 [thread overview]
Message-ID: <fc262dee0811191432w7e24dabbyb2b9eff1b8a33d77@mail.gmail.com> (raw)
In-Reply-To: <20081119183809.GF5682@csclub.uwaterloo.ca>
Well, who knows ? If you read my email carefully enough you should see
that that is not the question or issue here.
This was my first question to this list ever and I'm impressed with
the good and constructive answers I've gotten, but I really do not
understand the purpose of your response.
/Fredrik
On Wed, Nov 19, 2008 at 7:38 PM, Lennart Sorensen
<lsorense@csclub.uwaterloo.ca> wrote:
>
> On Tue, Nov 18, 2008 at 05:16:44PM +0100, Fredrik Markstr?m wrote:
> > 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.
>
> Ethernet MACs are a commodity these days. Who is dumb enough to think
> their ethernet MAC needs to be protected these days?
>
> You make an ethernet MAC... good for you. You have not invented
> anything new and amazing that needs protecting. Really. Get over it,
> you are not that special. :)
>
> > 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 ?
>
> Probably not, but I think the real issue is the previous one.
>
> --
> Len Sorensen
next prev parent reply other threads:[~2008-11-19 22:32 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
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 [this message]
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=fc262dee0811191432w7e24dabbyb2b9eff1b8a33d77@mail.gmail.com \
--to=fredrik.markstrom@avalonenterprise.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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
Powered by JetHome