From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Extract data file from U-Boot image
Date: Thu, 25 Jul 2013 21:01:59 +0200 [thread overview]
Message-ID: <20130725190159.43BA338319F@gemini.denx.de> (raw)
In-Reply-To: <CAF=5bWftE3UwPrOH+q+JPm-ag0igmAr_G4s=kLzhSObNhN=YyA@mail.gmail.com>
Dear Guilherme Maciel Ferreira,
In message <CAF=5bWftE3UwPrOH+q+JPm-ag0igmAr_G4s=kLzhSObNhN=YyA@mail.gmail.com> you wrote:
>
> 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?
Speaking just for myself: I needed such features only in very rare
occasions, where it was way faster to use a one-liner on the command
line than to write any actual code.
YMMV...
But I fear that mkimage explodes from creaping featurism, so if you
go and implement something like this, please do not add it to kmimage,
but rather create a separate, new tool, say "dumpimage" or so.
> 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.
Well, when I was doing such things, I never did this on the embedded
targets, nor did I ever have to care about performance because I
always needed it just once or twice.
Could you please be so kind and feed my curiousity a bit: what exactly
are you doing that you need such a feature on the target? I can't
think of useful applications at the moment...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
: ... and it's got weird formatting - Notepad, Write, Works 3 can't
: decipher it, and it's too big to go in DOS Edit. Help!
Install an operating system. :-) -- Tom Christiansen
next prev parent reply other threads:[~2013-07-25 19:01 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
2013-07-25 19:01 ` Wolfgang Denk [this message]
[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=20130725190159.43BA338319F@gemini.denx.de \
--to=wd@denx.de \
--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