From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] Makefile: add media image generation
Date: Thu, 19 Mar 2015 09:44:35 +0100 [thread overview]
Message-ID: <20150319084435.GA4367@free.fr> (raw)
In-Reply-To: <20150319092741.31bddb93@free-electrons.com>
Thomas, Vivien, All,
On 2015-03-19 09:27 +0100, Thomas Petazzoni spake thusly:
> On Thu, 19 Mar 2015 01:04:45 +0100, Yann E. MORIN wrote:
> > I've had a quick look at the examples you provide in later patches,
> > especially the RPi ones. You laways only have a single rootfs partition,
> > and there is no setup where you'd have (Rpi for example):
> >
> > /dev/mmcblk0p1 --> fat --> -
> > /dev/mmcblk0p2 --> squashfs --> /
> > /dev/mmcblk0p3 --> ext4 --> /usr/
>
> Well, the examples are "defconfig" style examples, so in the spirit of
> Buildroot, they should implement the simplest case possible. It's then
> up to the user to further refine the configuration to adapt the
> filesystem layout to his needs.
Sorry, I might not have been clear: I think the defconfig are indeed OK.
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.
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).
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...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-03-19 8:44 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 [this message]
2015-03-19 9:19 ` Thomas Petazzoni
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=20150319084435.GA4367@free.fr \
--to=yann.morin.1998@free.fr \
--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