All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aiko Barz <aiko@chroot.de>
To: linux-kernel@vger.kernel.org
Subject: WRT54G
Date: Sun, 19 Sep 2004 11:58:57 +0200	[thread overview]
Message-ID: <20040919095857.GD17602@lain.chroot.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

Hi there!

It's the wrt54g subject again...
I'm mirroring the Sveasoft-firmware, which was published under the
terms of "GPL". At least Sveasoft said that. Of course, many drivers
are closed. And others look like this:
 * This is UNPUBLISHED PROPRIETARY SOURCE CODE of Broadcom Corporation;
Since those drivers are kept outside the kernel-tree it might be
allright with the GPL.

Now, wind changed quite a bit: Sveasoft wants money for their
firmware. (It's ok with me.) Sveasoft actually sells the code. You
only get a copy if you are a registered, paying Sveasoft-user. This
also covers the GPL-part.

This site http://www.linksys.com/support/gpl.asp also implies, that i
can redistribute those drivers and firmwares. But it is the same
problem with them. Those wrt54g-firmwares also contain non-GPL
sourcecodes and binaries.

Sveasoft is hunting down mirrorsites right now. Of course, they want
to earn some money. So i'm not sure what I should do next?!
Going down or asking for the rest of the code?

Bis denne,
        Aiko

-- 
  .~.	 Aiko Barz
  /v\ 	 
 // \\	 Mail: aiko@chroot.de
/( _ )\  Web:  http://www.chroot.de
 ^^ ^^   PGP:  http://www.chroot.de/index.php?navi=GnuPG


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-09-19  9:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-19  9:58 Aiko Barz [this message]
2004-09-20 13:13 ` WRT54G Alan Cox
2004-09-21 12:10   ` WRT54G Daniel Egger
  -- strict thread matches above, loose matches on Subject: below --
2004-09-22  7:41 WRT54G www.sveasoft.com
2004-09-22  9:55 ` WRT54G Daniel Egger
2004-09-22 14:08 ` WRT54G 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=20040919095857.GD17602@lain.chroot.de \
    --to=aiko@chroot.de \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.