Netdev List
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Meelis Roos <mroos@linux.ee>
Cc: chas3@users.sourceforge.net, netdev@vger.kernel.org
Subject: Re: Fore 200 firmware
Date: Tue, 1 Jun 2010 18:12:04 +0100	[thread overview]
Message-ID: <20100601171203.GJ5306@decadent.org.uk> (raw)
In-Reply-To: <alpine.SOC.1.00.1006011902490.22519@math.ut.ee>

On Tue, Jun 01, 2010 at 06:03:31PM +0100, Meelis Roos wrote:
> > >does not have to redo the detective work I am doing. Packaging it along 
> > >with linux-atm packages (atm-tools in Debian) does not seem correct, so 
> > >do we need to make a special firmware package out of it or just add to 
> > >some other firmware repo that is packaged already?
> > 
> > i dont care which happens really.  i would to think it is part of
> > atm-tools since the fore200e driver really isnt useful with the
> > atm tools.
> 
> OK, so we should push the distro maintainers of it to create a suggested 
> firmware package or just include the fore firmware unconditionally - 
> once it is in released linux-atm.
> 
> > >What's the licence of the firmware anyway - unknown likely?
> > 
> > it says the firmware is gpl.  look at fore200e_firmware_copyright
> > in one of the old kernel distros.
> 
> Well, there is no source to fulfill the GPL... but there also should be 
> no problem redistributing it.
[...]
 
The GPL says (approximately) that people are allowed to redistribute binaries
only if they also redistribute source.  If the source is not available to the
public then anyone redistributing it is relying on the assumption that the
copyright holder didn't really mean this condition and will not enforce it.
At any time the copyright holder could sue them for copyright infringement,
and they would have to rely on a defence such as laches.

This is a common problem with firmware images that were added to the kernel
long ago.  To reduce legal risk, Debian has been removing these images and
will not include them in any future releases, even in the non-free archive
section, unless this is fixed.  Please do not try to add this firmware to
Debian without getting an appropriate licence.
 
Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus

      reply	other threads:[~2010-06-01 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31  8:06 Fore 200 firmware Meelis Roos
2010-06-01 14:37 ` Chas Williams (CONTRACTOR)
2010-06-01 14:52   ` Meelis Roos
2010-06-01 15:49     ` Chas Williams (CONTRACTOR)
2010-06-01 16:09       ` Meelis Roos
2010-06-01 17:12         ` Ben Hutchings [this message]

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=20100601171203.GJ5306@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=chas3@users.sourceforge.net \
    --cc=mroos@linux.ee \
    --cc=netdev@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