From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] BeagleBone: new board
Date: Tue, 10 Apr 2012 18:56:13 +0200 [thread overview]
Message-ID: <4F84662D.8070906@relinux.de> (raw)
In-Reply-To: <CA+-urNS5R_3bUY_SjVFFE3nMfdDN60O_-jJALKzo3cpu2my0fw@mail.gmail.com>
Am 10.04.2012 01:27, schrieb Frank Hunleth:
> Hi Stephan,
>
> On Sat, Apr 7, 2012 at 9:13 AM, Stephan Hoffmann <sho@relinux.de> wrote:
>> Am 12.03.2012 15:13, schrieb Frank Hunleth:
>>> 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>
>> Tested-by: Stephan Hoffmann <sho@relinux.de>
>>
>> CONFIG_EXT3_FS=m has to be changed to "y" to boot with the supplied u-boot configuration.
> Thanks a lot for testing the patch and reporting back.
>
> It is interesting that ext3 needs to be turned on. The patch to u-boot
> which *should* have been applied should have changed the ext3 config
> reference to ext2. However, I haven't been paying close attention to
> the BR list for the past couple weeks and my patch could be out of
> date now.
Hello Frank,
at least, I prefer having ext3;-) What would be a reason to stick to ext2?
> Having said this, I need to update my patch anyway. Nicolas Dechesne
> submitted an SPL bootloader patch that I'd like to base the new patch
> off of once it gets in. Also, the Linux config that I submitted feels
> way too bloated for BR. If you need something sooner, my current
> configs are at:
>
> https://github.com/nerves-project/bbone-erlang-buildroot/blob/master/configs/beaglebone_defconfig
>
> and
>
> https://github.com/nerves-project/bbone-erlang-buildroot/blob/master/board/beaglebone/linux-3.2.9.config
I'll have a look at these. I've also thrown out lots of drivers to get a
compact system.
Kind regards
Stephan
> The main change is that no longer compiles many drivers, and hardware
> float is enabled on the compiler. Since I haven't rebased that tree in
> a while, you'll probably need to make the ext3 change again.
>
> Thanks,
> Frank
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
next prev parent reply other threads:[~2012-04-10 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 14:13 [Buildroot] [PATCH v2 2/2] BeagleBone: new board Frank Hunleth
2012-03-14 0:19 ` Arnout Vandecappelle
2012-03-17 20:42 ` Frank Hunleth
2012-04-07 13:13 ` Stephan Hoffmann
2012-04-09 23:27 ` Frank Hunleth
2012-04-10 16:56 ` Stephan Hoffmann [this message]
2012-04-10 18:18 ` Frank Hunleth
2012-04-11 17:03 ` Stephan Hoffmann
2012-04-12 1:06 ` 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=4F84662D.8070906@relinux.de \
--to=sho@relinux.de \
--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