From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: a3load.hex
Date: Fri, 14 Oct 2005 21:13:38 +0000 [thread overview]
Message-ID: <20051014211338.GA7101@kroah.com> (raw)
In-Reply-To: <20051014134617.42227.qmail@web30703.mail.mud.yahoo.com>
On Fri, Oct 14, 2005 at 06:46:16AM -0700, william baroniunas wrote:
> Hi.
>
> I am new to this list, so I'm hoping that I can find
> someone to help me with a question regarding the
> a3load.hex source file found in the hotplug
> package(s).
>
> In this file, the Cypress copyright prohibits
> distribution of the file unless it is distributed with
> a Cypress USB product. It is not freely distributable.
>
> How are folks in the Linux community handling this
> issue?
No distro that I know of, distributes this file. Do you know of any?
We got approval from Cypress to add it to the package, as the file
really isn't useful at all without a Cypress processor to run on.
And the copyright says:
# Cypress Semiconductor Corporation hereby grants a copyright
# license to use or redistribute this firmware image, in text or
# binary form as required, only in conjunction with devices
# using a Cypress USB microcontroller. Every copy in any form
# of the firmware shall include Cypress copyright legends.
So it is ok to bundle it, right?
But I think you need to take it up with the individual distros that are
distributing the file, if you still object.
> Are there hotplug distributions that have
> extracted this file, as well as the ezusb functions?
I don't know, have you checked?
> Or has everyone simply ignored the copyright? To keep
> open source as real open source, it should ONLY
> include files that apply to a GPL-like license.
The license must be the same for files that are linked together. This
file isn't linked into any other one, right? So it should be fine.
> Anything short of that could spawn litigation issues
> in the future.
Litigation from whom? Cypress who gave us the file to redistribute? I
don't think so :)
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-10-14 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 13:46 a3load.hex william baroniunas
2005-10-14 21:13 ` Greg KH [this message]
2005-10-15 17:27 ` a3load.hex Adrian McMenamin
2005-10-17 13:14 ` a3load.hex william baroniunas
2005-10-17 18:45 ` a3load.hex Greg KH
2005-10-17 18:59 ` a3load.hex Adrian McMenamin
2005-10-17 19:57 ` a3load.hex Darren Salt
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=20051014211338.GA7101@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).