From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] configs: bump kernel use for RPi, use simpler defconfig
Date: Thu, 05 Sep 2013 15:43:13 +0200 [thread overview]
Message-ID: <87fvtj2xla.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <92b005253312c4d36732e01a60a9fdf6ec6660cc.1378330371.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Wed, 4 Sep 2013 23:35:54 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Yann> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
Yann> Bump for a slew of USB-related and other fixes.
Yann> The bcmrpi defconfig is a huge beast with lots of superfluous drivers.
Yann> The brcmrpi_quick defconfig is a stripped down minimalist defconfig with
Yann> all that is needed to bring up a RPi with complete HW support, and
Yann> nothing superfluous, which is what we need for a board's defconfig in
Yann> buildroot.
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-09-05 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 21:35 [Buildroot] [pull request] Pull request for branch yem/misc-updates Yann E. MORIN
2013-09-04 21:35 ` [Buildroot] [PATCH 1/4] package/rpi-firmware: bump version Yann E. MORIN
2013-09-05 13:42 ` Peter Korsgaard
2013-09-04 21:35 ` [Buildroot] [PATCH 2/4] configs: bump kernel use for RPi, use simpler defconfig Yann E. MORIN
2013-09-05 13:43 ` Peter Korsgaard [this message]
2013-09-04 21:35 ` [Buildroot] [PATCH 3/4] targets: move target options to their own sub-menu Yann E. MORIN
2013-09-05 2:25 ` Thomas De Schampheleire
2013-09-05 13:51 ` Yann E. MORIN
2013-09-05 13:44 ` Peter Korsgaard
2013-09-04 21:35 ` [Buildroot] [PATCH 4/4] toolchain/wrapper: add option to print one argument per line Yann E. MORIN
2013-09-05 12:48 ` Luca Ceresoli
2013-09-05 13:55 ` Yann E. MORIN
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=87fvtj2xla.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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