From: Aaron Lehmann <aaronl@vitelus.com>
To: Matthew Jacob <mjacob@feral.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h
Date: Thu, 24 May 2001 23:31:11 -0700 [thread overview]
Message-ID: <20010524233111.F23155@vitelus.com> (raw)
In-Reply-To: <Pine.BSF.4.21.0105242325460.4980-100000@beppo.feral.com>
On Thu, May 24, 2001 at 11:26:20PM -0700, Matthew Jacob wrote:
> Sure- that's not BSD. You were speaking about all kinds of firmware, at least
> I thought you were. Must be too short on sleep.
Yes, I am. New-style BSD licenses are compatible with the GPL. As long
as a piece of firmware contains source (which I discussed in a
previous post; see the GPL for the relevent defenition of source code)
and is under a GPL-compatible license it should be fine (excepting
further issues like patents.
In the case of the keyspan drivers, the source code is not distributed
and the license is not free, nor GPL-compatible. I hear steps are
going towards resolving this, which is excellent. My other concern is
what the general policy towards these non-free firmware images
is/should be. I know that a lot of firmware exists in advansys.c, and
there are probably many more occurances of binary-only firmware
throughout the kernel.
next prev parent reply other threads:[~2001-05-25 6:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSF.4.21.0105242155540.4849-100000@beppo.feral.com>
2001-05-25 5:57 ` Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h Aaron Lehmann
2001-05-25 6:26 ` Matthew Jacob
2001-05-25 6:31 ` Aaron Lehmann [this message]
2001-05-29 1:38 Adam J. Richter
-- strict thread matches above, loose matches on Subject: below --
2001-05-26 11:09 Adam J. Richter
2001-05-26 3:10 Adam J. Richter
2001-05-26 11:00 ` James Sutherland
2001-05-29 0:03 ` Jamie Lokier
2001-05-29 0:24 ` Alan Cox
2001-05-29 0:55 ` Jamie Lokier
2001-05-26 2:34 Adam J. Richter
2001-05-26 2:38 ` Larry McVoy
2001-05-26 4:52 ` Jeff V. Merkey
2001-05-25 17:02 Adam J. Richter
2001-05-25 17:23 ` Jacob Luna Lundberg
2001-05-25 18:30 ` Larry McVoy
2001-05-25 22:30 ` Aaron Lehmann
2001-05-26 1:43 ` Larry McVoy
2001-05-25 19:14 ` Doug Ledford
2001-05-25 10:36 Adam J. Richter
2001-05-25 9:34 Adam J. Richter
2001-05-25 16:06 ` Doug Ledford
[not found] <200105250559.f4P5x80365151@saturn.cs.uml.edu>
2001-05-25 6:03 ` Aaron Lehmann
2001-05-25 6:34 ` Alexander Viro
2001-05-25 6:42 ` Aaron Lehmann
2001-05-25 6:58 ` Alexander Viro
2001-05-25 7:02 ` Andreas Jaeger
2001-05-25 7:05 ` Alexander Viro
2001-05-25 10:56 ` Erik Mouw
2001-05-25 11:56 ` Alexander Viro
2001-05-25 12:44 ` Pavel Machek
[not found] <mailman.990765360.7016.linux-kernel2news@redhat.com>
2001-05-25 6:02 ` Pete Zaitcev
2001-05-25 4:34 Aaron Lehmann
2001-05-25 5:07 ` Greg KH
2001-05-25 10:00 ` John Cavan
2001-05-25 11:10 ` Alan Cox
2001-05-25 16:17 ` Alan Cox
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=20010524233111.F23155@vitelus.com \
--to=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjacob@feral.com \
/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