All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] configs: add RaspberryPi defconfig
Date: Sat, 12 Jan 2013 00:22:40 +0100	[thread overview]
Message-ID: <50F09EC0.6070906@mind.be> (raw)
In-Reply-To: <50F08131.1080208@je-eigen-domein.nl>

On 11/01/13 22:16, Floris Bos wrote:
> 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.

  Bummer.

> 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.

  It's just that that increases compile time, with little real benefit 
over a separate initramfs.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
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

      reply	other threads:[~2013-01-11 23:22 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
2013-01-11 23:22       ` Arnout Vandecappelle [this message]

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=50F09EC0.6070906@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.