Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] Makefile: add media image generation
Date: Thu, 19 Mar 2015 10:19:22 +0100	[thread overview]
Message-ID: <20150319101922.5e68220b@free-electrons.com> (raw)
In-Reply-To: <20150319084435.GA4367@free.fr>

Dear Yann E. MORIN,

On Thu, 19 Mar 2015 09:44:35 +0100, Yann E. MORIN wrote:

> However, what I wonder about, is that all those defconfigs rely on the
> image already generated by Buildroot, and I fail to see how one would
> write a mutli-partition genimage config file.
> 
> Furthermore, I've read the genimage docs (a mere README, far from being
> complete), and it does not look obvious to me.
> 
> Also, rather than letting Buildroot build the filesystem images and then
> aggregate that with genimage, it would be meuch more interesting (IMHO)
> to provide an example that lets genimage do the filesystem. That would
> be a good example on how to do it.

Well, the boot.vfat image in the raspberry pi example is a good
illustration of this: the FAT filesystem image is not created by
Buildroot, but by genimage itself.

> Also, in the case of multiple partitions, I wonder how /etc/fstab is
> updated (since the current examples only use a pre-generated filesystem
> image, they can't update fstab).

Using a post-build script ?

> It might even be interesting to have an example (e.g. in the manual or
> somewhere else...) with a more complex setup, like a multi-partition
> setup where parts are inherited from Buildroot (the rootfs) and others
> are generated by genimage, or whatever seemingly complex setup we can
> come up with...

Yes, I agree it would be interesting to have more complicated cases
covered in the Buildroot manual.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-03-19  9:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 22:51 [Buildroot] [PATCH 0/5] media image generation Vivien Didelot
2015-03-17 22:51 ` [Buildroot] [PATCH 1/5] Makefile: add " Vivien Didelot
2015-03-19  0:04   ` Yann E. MORIN
2015-03-19  8:27     ` Thomas Petazzoni
2015-03-19  8:44       ` Yann E. MORIN
2015-03-19  9:19         ` Thomas Petazzoni [this message]
2015-03-19 17:37           ` Vivien Didelot
2015-03-19 18:25             ` Yann E. MORIN
2015-03-19 20:31               ` Vivien Didelot
2015-03-19 22:46                 ` Arnout Vandecappelle
2015-03-19 22:05     ` Arnout Vandecappelle
2015-03-17 22:51 ` [Buildroot] [PATCH 2/5] board/raspberrypi: install Device Tree Vivien Didelot
2015-03-18 22:44   ` Yann E. MORIN
2015-03-18 23:05     ` Vivien Didelot
2015-03-17 22:51 ` [Buildroot] [PATCH 3/5] board/raspberrypi: add a genimage config Vivien Didelot
2015-03-17 22:51 ` [Buildroot] [PATCH 4/5] board/beaglebone: " Vivien Didelot
2015-03-17 22:51 ` [Buildroot] [PATCH 5/5] board/wandboard: " Vivien Didelot
2015-03-19 22:57 ` [Buildroot] [PATCH 0/5] media image generation Arnout Vandecappelle
2015-03-20  0:52   ` Vivien Didelot

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=20150319101922.5e68220b@free-electrons.com \
    --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