From: Floris Bos <bos@je-eigen-domein.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/wf111: remove package
Date: Tue, 25 Aug 2015 00:15:38 +0200 [thread overview]
Message-ID: <55DB978A.3050805@je-eigen-domein.nl> (raw)
In-Reply-To: <55DB7994.8080509@mind.be>
On 08/24/2015 10:07 PM, Arnout Vandecappelle wrote:
> I registered (under a false name and with a dummy e-mail address) and
> downloaded the driver, and there is no license text available in it. I also did
> not have to agree to any license conditions in order to register or download
> anything. So either this representative is wrong about "does not allow
> redistributing without licensing conditions", or the website designer botched
> it. Probably the latter. Bottom line is: unless you have a separate agreement
> with Bluegiga, you are not allowed to use this software for any purpose. I don't
> understand how legal departments can let something like this pass but on the
> other hand get all excited about some piece of GPLv3 in your product...
>
> The source code says "Refer to LICENSE.txt included with this source code for
> details on the license terms.", but LICENSE.txt is missing. An earlier version
> of the tarball has a LICENSE.txt with a MIT-like license or GPLv2. But anyway,
> that obviously only applies to the sources, not to the userspace binaries that
> are included and much less to the firmware blobs. So we probably can't host a
> copy on sources.buildroot.org.
Although not necessarily a version that works with this device, source
for the unifi_helper program doesn't seem to be that hard to find either.
https://github.com/kk30/A10-Linux-2.6.36/tree/master/modules/wifi/apm/unifi-linux
license.txt suggests everything is dual licensed MIT and GPLv2
So wonder if it is really the chip vendor being the problem...
Yours sincerely,
Floris Bos
next prev parent reply other threads:[~2015-08-24 22:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 0:13 [Buildroot] [PATCH] package/wf111: remove package Yann E. MORIN
2015-08-23 14:36 ` Thomas Petazzoni
2015-08-23 15:37 ` Yann E. MORIN
2015-08-23 18:58 ` Thomas Petazzoni
2015-08-24 20:07 ` Arnout Vandecappelle
2015-08-24 22:15 ` Floris Bos [this message]
2015-08-25 20:28 ` Peter Korsgaard
2015-08-26 15:09 ` Thomas Petazzoni
2015-08-26 15:31 ` Peter Korsgaard
2015-08-26 17:32 ` Thomas Petazzoni
2015-08-26 18:47 ` Yann E. MORIN
2015-08-26 20:24 ` Peter Korsgaard
2015-08-26 22:05 ` Yann E. MORIN
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=55DB978A.3050805@je-eigen-domein.nl \
--to=bos@je-eigen-domein.nl \
--cc=buildroot@busybox.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