From: "Adam J. Richter" <adam@yggdrasil.com>
To: hugh@misc.nu
Cc: aaronl@vitelus.com, acahalan@cs.uml.edu, greg@kroah.com,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h
Date: Fri, 25 May 2001 03:36:43 -0700 [thread overview]
Message-ID: <200105251036.DAA23376@adam.yggdrasil.com> (raw)
Here's a surprise. I think the problems with the keyspan
copyrights may have sprung from an administrative error. I notice that
the copyright notices in
linux-2.4.*/drivers/usb/serial/keyspan_usa{26,28,49}msg.h, which look
GPL compatible to me, look as if they were intended for
keyspan_usa{18x,19,28,28x,49w}_fw.h, since they refer to firmware
in their titles:
Copyright (c) 1998-2000 InnoSys Incorporated. All Rights Reserved
This file is available under a BSD-style copyright
Keyspan USB Async Firmware to run on Anchor EZ-USB
^^^^^^^^
Yet, the keyspan*msg.h files have no firmware. The firmware
is in keyspan_usa*_fw.h.
Hugh, perhaps you could pass this up the chain of command
at Keyspan and see if they will simply grant permission to
replace the *_fw.h copyright notice with the one from *msg.h, which
is probably a lot simpler than having them spend lawyer and management
time on writing new terms.
I have cc'ed this to linux-kernel because there is a
current discussion going on there on this subject that I had just
responded to.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
next reply other threads:[~2001-05-25 10:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 10:36 Adam J. Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-29 1:38 Adam J. Richter
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 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
[not found] <Pine.BSF.4.21.0105242155540.4849-100000@beppo.feral.com>
2001-05-25 5:57 ` Aaron Lehmann
2001-05-25 6:26 ` Matthew Jacob
2001-05-25 6:31 ` Aaron Lehmann
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=200105251036.DAA23376@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=aaronl@vitelus.com \
--cc=acahalan@cs.uml.edu \
--cc=greg@kroah.com \
--cc=hugh@misc.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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®