From: Floris Bos <bos@je-eigen-domein.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] rpi-firmware: New package
Date: Tue, 08 Jan 2013 01:59:09 +0100 [thread overview]
Message-ID: <50EB6F5D.4040202@je-eigen-domein.nl> (raw)
In-Reply-To: <50EB5C6A.4010301@mind.be>
On 01/08/2013 12:38 AM, Arnout Vandecappelle wrote:
> On 08/01/13 00:30, Floris Bos wrote:
>> On 01/08/2013 12:06 AM, Maxime Hadjinlian wrote:
>>> On Mon, Jan 7, 2013 at 11:41 PM, Arnout Vandecappelle <arnout@mind.be>
>>> wrote:
>>>> On 06/01/13 23:01, Peter Korsgaard wrote:
>>>>> +RPI_FIRMWARE_LICENSE = BSD-3c
>>>>> +RPI_FIRMWARE_LICENSE_FILE = boot/LICENCE.broadcom
>>>>
>>>> As Thomas pointed out, this is not BSD-3c but "Broadcom proprietary
>>>> license".
>>>>
>>>> Maybe it should also get
>>>>
>>>> RPI_FIRMWARE_REDISTRIBUTE = NO
>>>>
>>> So, even the binary are not free from redistributing ? I'm sorry, I
>>> lack absolute knowledge in license... I should study this.
>>> I will patch to add this.
>>
>> Perhaps also copy the boot/LICENCE.broadcom file to the directory
>> holding
>> the boot files?
>
> Why? Usually when the device is redistributed, the end user doesn't
> even have access to the filesystem. So putting license files in the
> root filesystem is quite redundant.
>
In the case of the Raspberry, the bootloader files are always stored on
the FAT partition of a removable SD card.
Even inside an enclosure, they are quite more accessible to end-users
than with other devices.
Yours sincerely,
Floris Bos
next prev parent reply other threads:[~2013-01-08 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 22:01 [Buildroot] [git commit] rpi-firmware: New package Peter Korsgaard
2013-01-07 22:41 ` Arnout Vandecappelle
2013-01-07 23:06 ` Maxime Hadjinlian
2013-01-07 23:30 ` Floris Bos
2013-01-07 23:38 ` Arnout Vandecappelle
2013-01-08 0:59 ` Floris Bos [this message]
2013-01-08 9:06 ` Maxime Hadjinlian
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=50EB6F5D.4040202@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 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.