Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: allow own initramfs to be specified
Date: Mon, 27 Jul 2009 18:00:35 +0200	[thread overview]
Message-ID: <20090727160035.GT13236@buzzloop.caiaq.de> (raw)
In-Reply-To: <20090727162148.4ec3c25b@surf>

On Mon, Jul 27, 2009 at 04:21:48PM +0200, Thomas Petazzoni wrote:
> 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 ?

Yep, you're right. We should do it that way. I was thinking of offering
a way to let a precompiled cpio image become the initramfs of the built
kernel, but it is really better to let br2 handle it all.

There are, however, two problems with the existing code.

1) the linux modules are installed unconditionally which we must avoid
   our case
2) the initramfs target is currently broken

So, forget about this patch, I'll provide two new ones to make this
work.

Thanks,
Daniel

      reply	other threads:[~2009-07-27 16:00 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
2009-07-27 16:00   ` Daniel Mack [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=20090727160035.GT13236@buzzloop.caiaq.de \
    --to=daniel@caiaq.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