Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/4] binaries-marvell: new package
Date: Mon, 4 Dec 2017 09:01:43 +0100	[thread overview]
Message-ID: <20171204090143.00298c53@windsurf.home> (raw)
In-Reply-To: <20171204054510.oui3vvag34655pka@sapphire.tkos.co.il>

Hello,

On Mon, 4 Dec 2017 07:45:10 +0200, Baruch Siach wrote:

> > > +BINARIES_MARVELL_VERSION = 0dabe23b956420b0928d337d635f0cd5646c33d0
> > > +BINARIES_MARVELL_SITE = $(call github,MarvellEmbeddedProcessors,binaries-marvell,$(BINARIES_MARVELL_VERSION))
> > > +BINARIES_MARVELL_LICENSE = PROPRIETARY
> > > +BINARIES_MARVELL_REDISTRIBUTE = NO  
> > 
> > Well, if you can't distribute it... it's a bit problematic no?
> > 
> > In fact, there is a license on the master branch, i.e at
> > https://raw.githubusercontent.com/MarvellEmbeddedProcessors/binaries-marvell/master/README.md.
> > And to me, this is GPL-2.0 with the FreeRTOS exception, so I've changed
> > the BINARIES_MARVELL_LICENSE variable to that, and dropped
> > BINARIES_MARVELL_REDISTRIBUTE. Let me know what you think.  
> 
> IANAL, but as this text does not appear in the branch we are using, this might 
> indicate that it does not apply there. Moreover, the text in README.md refers 
> to sources that we do not have. AFAICS, it says nothing about the binaries 
> license, and there is no indication that the binaries were generated from GPL 
> code.

True.

> I believe that this is just an oversight of Marvell, but having an explicit 
> assurance would be better.

Agreed. Perhaps in the mean time, what Sergey originally did is the
safest, i.e assuming is proprietary.

And in fact, my statement about <pkg>_REDISTRIBUTE = NO was incorrect.
In the context of Buildroot <pkg>_REDISTRIBUTE = NO does not mean that
you're not allowed to redistribute the software, it means that it
shouldn't be shipped as part of legal-info. But still, I don't see why
binaries-marvell shouldn't be listed as part of legal-info.

I'll go and ask Marvell about the license of those blobs.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-12-04  8:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 18:18 [Buildroot] [PATCH v3 0/4] Add support for MacchiatoBin board Sergey Matyukevich
2017-12-03 18:18 ` [Buildroot] [PATCH v3 1/4] mv-ddr-marvell: new package Sergey Matyukevich
2017-12-03 22:01   ` Thomas Petazzoni
2017-12-03 18:18 ` [Buildroot] [PATCH v3 2/4] binaries-marvell: " Sergey Matyukevich
2017-12-03 22:03   ` Thomas Petazzoni
2017-12-04  5:45     ` Baruch Siach
2017-12-04  8:01       ` Thomas Petazzoni [this message]
2017-12-03 18:18 ` [Buildroot] [PATCH v3 3/4] atf: add support for Marvell Armada SoCs Sergey Matyukevich
2017-12-03 22:04   ` Thomas Petazzoni
2017-12-03 18:18 ` [Buildroot] [PATCH v3 4/4] solidrun/macchiatobin: add new board Sergey Matyukevich
2017-12-03 21:35   ` Thomas Petazzoni
2017-12-03 21:53 ` [Buildroot] [PATCH v3 0/4] Add support for MacchiatoBin board Thomas Petazzoni
2017-12-04  6:10   ` Sergey Matyukevich

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=20171204090143.00298c53@windsurf.home \
    --to=thomas.petazzoni@free-electrons.com \
    --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