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] genimage raw partition from multiple files
Date: Wed, 2 Aug 2017 20:11:36 +0200	[thread overview]
Message-ID: <20170802201136.08c38588@windsurf.home> (raw)
In-Reply-To: <5eba6e0b-68e0-db07-f0d7-d5be0580e257@gmail.com>

Hello,

On Wed, 2 Aug 2017 20:09:01 +0200, Micha? ?yszczek wrote:

> > And those two snippets of genimage configuration can be in a single
> > genimage.cfg, and both uboot.img and then sdcard.img will be produced
> > by a single genimage invocation ? Or do we need a first genimage
> > invocation to generate uboot.img, and then a second genimage invocation
> > to generate sdcard.img (which requires uboot.img) ?
> 
> Only one invocation of genimage.sh is needed to generate working
> sdcard.img. Yes! It's that simple! I attach full genimage.cfg I created
> for my port for cyclone5. This genimage.cfg creates fully working
> sdcard.img (including uboot.img), and only external script used is
> support/script/genimage.sh -c genimage.cfg.

Excellent! So I guess you can send a new version of your patch!

Also, don't hesitate to contribute to genimage to improve its
documentation.

Best regards,

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

      reply	other threads:[~2017-08-02 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 13:55 [Buildroot] genimage raw partition from multiple files Michał Łyszczek
2017-08-02 17:25 ` Michał Łyszczek
2017-08-02 17:55   ` Thomas Petazzoni
2017-08-02 18:09     ` Michał Łyszczek
2017-08-02 18:11       ` Thomas Petazzoni [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=20170802201136.08c38588@windsurf.home \
    --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