From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: allow own initramfs to be specified
Date: Mon, 27 Jul 2009 16:21:48 +0200 [thread overview]
Message-ID: <20090727162148.4ec3c25b@surf> (raw)
In-Reply-To: <1248702330-28741-1-git-send-email-daniel@caiaq.de>
Le Mon, 27 Jul 2009 15:45:30 +0200,
Daniel Mack <daniel@caiaq.de> a ?crit :
> The initramfs source location is removed from the given Linux kernel
> configuration at the moment and only filled in again in case BR2 is
> asked to provide a cpio for that feature.
>
> This patch allows to specify an own location for such an image file.
Just curious, what's the use case for this ?
Buildroot already allows to integrate the root filesystem it generated
into the initramfs. It seems your patch allows to integrate a different
initramfs that the one generated by Buildroot. Is this correct ? If so,
what's your use case ?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-07-27 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 13:45 [Buildroot] [PATCH] linux: allow own initramfs to be specified Daniel Mack
2009-07-27 14:21 ` Thomas Petazzoni [this message]
2009-07-27 16:00 ` Daniel Mack
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=20090727162148.4ec3c25b@surf \
--to=thomas.petazzoni@free-electrons.com \
--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