All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] compiling kernel
Date: Thu, 20 Mar 2014 21:34:24 +0100	[thread overview]
Message-ID: <532B50D0.7030100@mind.be> (raw)
In-Reply-To: <1395101926704-65501.post@n4.nabble.com>

On 18/03/14 01:18, raj wrote:
> Hi Arnout,
> 
> Thanks much for your reply...
> I want to compile kernel and root file system separately for couple of
> reasons:
> 
> 1. I want application developer to just use prebuilt kernel binary + rootfs
> and run some script to create full Image so that, they don't need to have
> kernel source files.
> 
> could you give some clarity on creating separately file system and passing
> boot args to kernel to use the file system located in the dram.

 I'm not sure what you mean exactly, but perhaps you should look into
unionfs-fuse. That allows you to boot a standard rootfs and then mount
the developer's additions on top of it.

> 
> 2. I can compile kernel without the  "Initial RAM filesystem and RAM disk
> (initramfs/initrd) support", so that it has only the kernel image. How do I
> built the file system image?

 Look in buildroot's filesystem options menu.

 Regards,
 Arnout

> 
> 
> Thanks & Regards,
> Raj
>  
> 
> 
> 
> 
> 
> --
> View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/compiling-kernel-tp63718p65501.html
> Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 


-- 
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:[~2014-03-20 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 23:08 [Buildroot] compiling kernel Basavaraj Hiremath
2014-02-26  7:48 ` Mike Zick
2014-02-26 17:38   ` Arnout Vandecappelle
2014-03-18  0:18     ` raj
2014-03-20 20:34       ` Arnout Vandecappelle [this message]
2014-03-21 22:02         ` raj
2014-03-25 22:19           ` 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=532B50D0.7030100@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.