From: Adrian McMenamin <adrian@mcmen.demon.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: a3load.hex
Date: Sat, 15 Oct 2005 17:27:24 +0000 [thread overview]
Message-ID: <1129397244.3413.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20051014134617.42227.qmail@web30703.mail.mud.yahoo.com>
On Fri, 2005-10-14 at 06:46 -0700, william baroniunas wrote:
>
> How are folks in the Linux community handling this
> issue? Are there hotplug distributions that have
> extracted this file, as well as the ezusb functions?
> 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.
I think you'll find that one of the principal uses of hotplug is to
allow the distribution of firmware with distros.
For instance, I have some firmware for the device I am working on which
is BSD licenced. In Linux 2.4 all this was whacked into a header in the
kernel and distributed under the GPL. Although the source was freely
available, GPL purists could have argued it was tainting the kernel (in
fact there are not enough Dreamcast users to make an issue of this).
However, hotplug allows me to distribute the firmware in userspace and
keep the kernel GPL-pure.
In other cases the firmware won't even be available on BSD-type terms.
In that case if we followed your advice (on licences NOT copyright by
the way) we'd have nothing.
As an aside: is the reply-to header not set on this list deliberately?
-------------------------------------------------------
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-15 17:27 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 ` a3load.hex Greg KH
2005-10-15 17:27 ` Adrian McMenamin [this message]
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=1129397244.3413.12.camel@localhost.localdomain \
--to=adrian@mcmen.demon.co.uk \
--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).