From: Theodore Tso <tytso@mit.edu>
To: "Fredrik Markström" <fredrik.markstrom@avalonenterprise.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: Developing non-commercial drivers ?
Date: Tue, 18 Nov 2008 18:28:31 -0500 [thread overview]
Message-ID: <20081118232831.GA7863@mit.edu> (raw)
In-Reply-To: <fc262dee0811181313n35f39184ne438ddebb0225ba5@mail.gmail.com>
On Tue, Nov 18, 2008 at 10:13:30PM +0100, Fredrik Markström wrote:
>
> Unfortunately I can't disclose our client simply because I have not
> asked for their permission.
Understood, of course not. All you can do is suggest that they might
want to contact us.
> Anyway strongly doubt they want to do something illegal or wrong, but
> a lot of people obviously thinks binary drivers are accepted by the
> Linux community and licensing. It sure would be nice if this could be
> stated more explicit in some official FAQ.
There are many different ways to use the word "wrong". There is
"morally wrong" (as in, goes against the spirit of the license and of
the development community). There is "legally wrong", which depends
on the legal jurisdiction (of you, the company, and the end user),
which will require a lawyer's input. And then there's "pragamatically
wrong", as in, regardless of whether it's legal, there are significant
technical downsides in trying to trying to develop binary-only drivers
that in the long run will cost you money.
> Your (the Linux Foundations) web gives the impression that you protect
> Linux against external interests (like my clients), but do you have
> to authority to work the other way ? Can you make deals or promises on
> behalf of the copyright owners of the Linux kernel ? I doubt that but
> might be wrong.
No, of course not. That being said, there are binary modules out
there, and there are ways which are "safer" in terms of whether you
are likely to get sued, if the company you are working with wants to
skate close to the dark side and live in the same legal grey zone as
Nvidia and Broadcom.
> Anyway, I'm not sure how the Linux Foundation can help in this case,
> if you can explain that, I sure will bring it up with our client.
We can give advice; but it's well informed advice.
- Ted
next prev parent reply other threads:[~2008-11-18 23:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 16:16 Developing non-commercial drivers ? 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 [this message]
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=20081118232831.GA7863@mit.edu \
--to=tytso@mit.edu \
--cc=Valdis.Kletnieks@vt.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--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