From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/9] iMX6S-PICO: add default config file (imx6spico_defconfig)
Date: Wed, 11 Oct 2017 15:14:05 +0200 [thread overview]
Message-ID: <20171011151405.3fd491f9@windsurf.lan> (raw)
In-Reply-To: <1507724378-23461-1-git-send-email-agambier.dev@gmail.com>
Hello,
On Wed, 11 Oct 2017 14:19:30 +0200, Alexandre Gambier wrote:
> Signed-off-by: Alexandre Gambier <agambier.dev@gmail.com>
Thanks for your contributions.
However, as I have written to you off list already, your patches 7/9,
8/9 and 9/9 will not make it to the list because they are too big.
And we anyway don't want such huge firmware files in Buildroot
directly, as I already explained to you. Especially without a license
file.
Can you instead work with the linux-firmware project to get those
firmware files included? This will obviously require to have a proper
license for them, but that would anyway be needed for you to be allowed
to redistribute them.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-11 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 12:19 [Buildroot] [PATCH 1/9] iMX6S-PICO: add default config file (imx6spico_defconfig) Alexandre Gambier
2017-10-11 12:19 ` [Buildroot] [PATCH 2/9] iMX6S-PICO: add linux default config file (defconfig) Alexandre Gambier
2017-10-11 12:19 ` [Buildroot] [PATCH 3/9] iMX6S-PICO: add post image scripts Alexandre Gambier
2017-10-11 12:19 ` [Buildroot] [PATCH 4/9] iMX6S-PICO: add firmware files (nvram*) Alexandre Gambier
2017-10-11 12:19 ` [Buildroot] [PATCH 5/9] iMX6S-PICO: add firmware files (bcm*) Alexandre Gambier
2017-10-11 12:19 ` [Buildroot] [PATCH 6/9] iMX6S-PICO: add firmware files (bcmfmac*) Alexandre Gambier
2017-10-11 13:14 ` Thomas Petazzoni [this message]
2017-10-11 16:34 ` [Buildroot] [PATCH 1/9] iMX6S-PICO: add default config file (imx6spico_defconfig) Arnout Vandecappelle
2017-10-11 13:17 ` Thomas Petazzoni
[not found] ` <CAKrb2srEz1UeT-RJgY7NCEDp28OX7xGq=JD5qOvR_eZBkkahKg@mail.gmail.com>
[not found] ` <20171011164908.3cc14130@windsurf.lan>
[not found] ` <CAKrb2soZLWtymDeToLxPmk=Vtdt0E+wT5KHMcCa6x-BLukSCaQ@mail.gmail.com>
2017-10-11 15:34 ` Thomas Petazzoni
2017-10-11 16:04 ` Fabio Estevam
2017-10-11 16:06 ` Fabio Estevam
2017-10-11 16:26 ` Arnout Vandecappelle
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=20171011151405.3fd491f9@windsurf.lan \
--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 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.