All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vyacheslav via buildroot <buildroot@buildroot.org>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/amlogic-boot-fip: new package
Date: Sat, 22 Jan 2022 19:09:28 +0300	[thread overview]
Message-ID: <1a3ce2b5-4b17-b79f-5dd5-29637575d473@lexina.in> (raw)
In-Reply-To: <20220122160914.7e4cc513@windsurf>

Hi, Neil!
Can you help us with understanding license for Amlogic binaries in
https://github.com/LibreELEC/amlogic-boot-fip?


22.01.2022 18:09, Thomas Petazzoni wrote:
> Hello,
> 
> On Sat, 22 Jan 2022 18:05:06 +0300
> Vyacheslav <adeep@lexina.in> wrote:
> 
>>> So how can the contents of this repository be useful? OK, then can be
>>> used locally for your own experiments. But for building an actual
>>> device that you can ship/provide to others, using the contents of that
>>> repository, because Amlogic does not even allow you to distribute the
>>> contents of this repository.
>>>
>>> So I am wondering if it's really reasonable to package this in
>>> Buildroot.
>>>    
>> You already have package/odroidc2-firmware with same license.
>> amlogic-boot-fip just put all similar binaries together and Neil
>> Armstrong made a build system for aml uboot binaries.
> 
> Well, I wasn't aware package/odroidc2-firmware was under the same
> restrictive license. Are the license terms for
> package/odroidc2-firmware available somewhere? This package is
> downloaded from https://github.com/hardkernel/u-boot, but I don't see
> the license terms from Amlogic preventing redistribution. Of course, I
> understand that they simply may be missing (which would be really bad!).
> 
> But how can anyone use those blobs? You can't redistribute them.
> According to their license, just putting them on Github is not even
> allowed.
> 
> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-01-22 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 11:14 [Buildroot] [PATCH] package/amlogic-boot-fip: new package Vyacheslav Bocharov via buildroot
2022-01-22 13:33 ` Thomas Petazzoni
2022-01-22 15:05   ` Vyacheslav via buildroot
2022-01-22 15:09     ` Thomas Petazzoni
2022-01-22 16:09       ` Vyacheslav via buildroot [this message]
2022-01-24 13:41         ` Neil Armstrong
2022-01-24 20:45           ` Thomas Petazzoni
2022-01-26  5:41             ` Vyacheslav via buildroot

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=1a3ce2b5-4b17-b79f-5dd5-29637575d473@lexina.in \
    --to=buildroot@buildroot.org \
    --cc=adeep@lexina.in \
    --cc=narmstrong@baylibre.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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.