From: Floris Bos <bos@je-eigen-domein.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] configs: add RaspberryPi defconfig
Date: Fri, 11 Jan 2013 22:16:33 +0100 [thread overview]
Message-ID: <50F08131.1080208@je-eigen-domein.nl> (raw)
In-Reply-To: <50F072D9.3010808@mind.be>
On 01/11/2013 09:15 PM, Arnout Vandecappelle wrote:
> On 11/01/13 18:08, Floris Bos wrote:
>> On 01/11/2013 02:17 PM, Maxime Hadjinlian wrote:
>>> In order to have a working SDCard, you should have at least two
>>> partitions :
>>
>> Might also be worth mentioning that for use cases that do not require
>> file changes to persist across reboots you can go the initramfs route,
>> and let the bootloader load the entire rootfs to memory at boot.
>>
>> - "make menuconfig" -> select "Filesystem images" -> "initramfs for
>> intial ramdisk of linux kernel"
>> - After build simply copy the files from target to a FAT formatted SD
>> card.
>>
>> No need to mess with extra partitions that way, and you are less
>> affected
>> by the glitches the Pi's SD card kernel module has from time to time.
>
> Does the RPi bootloader support initrd loading? In that case, maybe
> it's better to default to rootfs.cpio.gz (or .lzma) and adapt the
> config.txt accordingly. That way, creating a bootable is a lot
> simpler: just chuck the entire images directory on a FAT-formatted SD
> card...
The bootloader does support loading separate initrd files through a
config.txt option.
But the standard bcmrpi_defconfig Raspberry kernel does not, because
CONFIG_BLK_DEV_INITRD isn't enabled in the default configuration.
If you cannot use the standard kernel, and have to compile your own
anyway, it is easier to use the buildroot "initramfs" option, and have
the initramfs integrated into zImage.
Yours sincerely,
Floris Bos
next prev parent reply other threads:[~2013-01-11 21:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 13:17 [Buildroot] [PATCH v2] configs: add RaspberryPi defconfig Maxime Hadjinlian
2013-01-11 13:36 ` Yann E. MORIN
2013-01-11 13:38 ` Maxime Hadjinlian
2013-01-11 15:19 ` Floris Bos
2013-01-11 15:34 ` Maxime Hadjinlian
2013-01-11 16:01 ` Thomas Petazzoni
2013-01-11 16:05 ` Thomas Petazzoni
2013-01-11 17:08 ` Floris Bos
2013-01-11 20:15 ` Arnout Vandecappelle
2013-01-11 21:16 ` Floris Bos [this message]
2013-01-11 23:22 ` Arnout Vandecappelle
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=50F08131.1080208@je-eigen-domein.nl \
--to=bos@je-eigen-domein.nl \
--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