From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Some topics for the Buildroot Developer Day
Date: Sat, 29 Oct 2011 08:20:24 +0200 [thread overview]
Message-ID: <20111029082024.61d9042b@skate> (raw)
In-Reply-To: <4ff558d1b2a462f239c4c83ef48b6680@zacarias.com.ar>
Le Wed, 26 Oct 2011 10:05:55 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :
> My $.02 is that we could just do it as a package with a huge option
> list for each firmware file(s) required for different drivers/devices.
> I'd go for a smaller subset to begin with since there are firmware
> files for SAN controllers and other big iron stuff that probably
> are't the target for buildroot.
Or you put a single "string" option in which the user can pass a
space-separated list of firmware to install.
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:[~2011-10-29 6:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 15:38 [Buildroot] Some topics for the Buildroot Developer Day Thomas Petazzoni
2011-10-24 16:59 ` Robert Schwebel
2011-10-24 19:47 ` Thomas Petazzoni
2011-10-24 20:06 ` Eric Bénard
2011-10-25 6:02 ` Peter Korsgaard
2011-10-25 6:34 ` Robert Schwebel
2011-10-25 7:15 ` Peter Korsgaard
2011-10-25 12:20 ` Robert Schwebel
2011-10-24 21:44 ` Shawn J. Goff
2011-10-25 5:53 ` Mike Frysinger
2011-10-24 22:54 ` Quotient Remainder
2011-10-25 6:24 ` Thomas Petazzoni
2011-10-25 7:13 ` Peter Korsgaard
2011-10-25 8:26 ` Thomas De Schampheleire
2011-10-26 12:48 ` Yegor Yefremov
2011-10-26 13:05 ` Gustavo Zacarias
2011-10-29 6:20 ` Thomas Petazzoni [this message]
2011-10-29 11:36 ` Gustavo Zacarias
2011-11-18 16:48 ` Thomas Petazzoni
2011-10-30 20:29 ` Thomas Petazzoni
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=20111029082024.61d9042b@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