From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Extract data file from U-Boot image
Date: Thu, 25 Jul 2013 20:57:52 +0200 [thread overview]
Message-ID: <20130725205752.018024a3@lilith> (raw)
In-Reply-To: <CAF=5bWftE3UwPrOH+q+JPm-ag0igmAr_G4s=kLzhSObNhN=YyA@mail.gmail.com>
Hi Guilherme,
On Thu, 25 Jul 2013 12:31:46 -0300, Guilherme Maciel Ferreira
<guilherme.maciel.ferreira@gmail.com> wrote:
> Hi list,
>
> I guess I'm not the first one who ever needed to retrieve data files
> from multifile images, those create by mkimage tool. However, I could
> just find scripts to do that (specially an old thread answered by
> Wolfgang about dd).
>
> I made a patch to allow mkimage to extract files from images, which
> just works for multi-file image. But, the fact that nobody has ever
> done this means that this feature is not desired in the tool?
>
> IMHO, it is very convenient to have a C code to do that, specially for
> embedded systems where scripting is noticeably slower than binary
> code. Besides it requires 'dd' to extract and another tool to parse
> file's offsets inside the image.
>
> Comments?
My comment would be that, while U-Boot images /run/ on embedded
systems, people do not necessarily /work on/ these images /from within/
said systems; indeed, work on such images, and more generally,
development around U-Boot, is performed on development systems, not
on target systems.
Besides, in many cases, the image was actually built from files
available -- even from files themselves built just before putting them
together within the image.
Apart from very specific cases (tweaking the initrd in an existing
image comes to mind), I don't see the point in taking images apart when
you can simply build them the way you want.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-07-25 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 15:31 [U-Boot] Extract data file from U-Boot image Guilherme Maciel Ferreira
2013-07-25 18:57 ` Albert ARIBAUD [this message]
2013-07-25 19:01 ` Wolfgang Denk
[not found] ` <CAHCtDORkcGdgTnTPyJfrxwdpmA=mrFDAJ5rHEzz94gy=wuq1fQ@mail.gmail.com>
2013-07-25 19:43 ` Wolfgang Denk
2013-07-25 21:12 ` Guilherme Maciel Ferreira
2013-07-26 5:24 ` Wolfgang Denk
2013-07-26 19:30 ` Guilherme Maciel Ferreira
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=20130725205752.018024a3@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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