From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] BeagleBone: new board
Date: Sun, 11 Mar 2012 15:32:04 +0100 [thread overview]
Message-ID: <201203111532.04827.arnout@mind.be> (raw)
In-Reply-To: <1331214423-8647-2-git-send-email-fhunleth@troodon-software.com>
On Thursday 08 March 2012 14:47:03 Frank Hunleth wrote:
> This configuration uses the latest released kernel and u-boot versions
> supported by Beagleboard developers. The Linux kernel configuration has
> been modified to compile in EXT2 support and use gzip to compress the
> kernel.
>
> Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com>
> ---
> board/beaglebone/linux-3.2.9.config | 3572 ++++++++++++++++++++
Please use 'make linux-update-defconfig' to create a defconfig. Then we
don't have to add a 3500 line file.
[snip]
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-03-11 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 13:47 [Buildroot] [PATCH 1/2] uboot: Add support for copying MLO to the images directory for U-boot builds that include it Frank Hunleth
2012-03-08 13:47 ` [Buildroot] [PATCH 2/2] BeagleBone: new board Frank Hunleth
2012-03-11 14:32 ` Arnout Vandecappelle [this message]
2012-03-12 14:16 ` Frank Hunleth
2012-03-11 15:33 ` [Buildroot] [PATCH 1/2] uboot: Add support for copying MLO to the images directory for U-boot builds that include it Arnout Vandecappelle
2012-03-12 14:19 ` Frank Hunleth
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=201203111532.04827.arnout@mind.be \
--to=arnout@mind.be \
--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