From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] linux: install firmware to staging.
Date: Thu, 11 Jul 2013 10:58:43 +0200 [thread overview]
Message-ID: <20130711105843.3fdaef14@skate> (raw)
In-Reply-To: <20130710171218.GC3297@free.fr>
Dear Yann E. MORIN,
On Wed, 10 Jul 2013 19:12:18 +0200, Yann E. MORIN wrote:
> Altenatively, as I suggested before, this could be delegated to a
> post-build script:
> - the package (linux) always install its files in staging
> - a post-build scripts cherry-picks what is relevant
>
> What I don't like with this solution is that the Linux kernel would
> always install its firmware files, and that people will start using that
> as the source of the firmwares, while we do have linux-firmware for
> that.
Another solution is, inside the kernel menu:
[*] Install in-kernel firmwares
(*.dtbo) List of firmwares to installs
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-07-11 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 17:39 [Buildroot] [PATCH v2 1/2] linux: install firmware to staging Spenser Gilliland
2013-07-09 17:39 ` [Buildroot] [PATCH v2 2/2] beagle-capes: new package Spenser Gilliland
2013-07-09 20:04 ` Yann E. MORIN
2013-07-09 20:03 ` [Buildroot] [PATCH v2 1/2] linux: install firmware to staging Yann E. MORIN
2013-07-10 7:11 ` Thomas Petazzoni
2013-07-10 17:12 ` Yann E. MORIN
2013-07-11 8:58 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-09 17:00 Spenser Gilliland
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=20130711105843.3fdaef14@skate \
--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