From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools: mkimage can read input on /dev/stdin
Date: Sat, 27 Sep 2014 14:54:34 +0200 [thread overview]
Message-ID: <20140927125434.B9C8F382279@gemini.denx.de> (raw)
In-Reply-To: <CADF714agpUedt_o3iXcGBRBc5CaV6TBUn=1oGEqJj3h2b+f-Vg@mail.gmail.com>
Dear Julien,
In message <CADF714agpUedt_o3iXcGBRBc5CaV6TBUn=1oGEqJj3h2b+f-Vg@mail.gmail.com> you wrote:
>
> I would like to give /dev/stdin to the flag -d of mkimage. The only
What would be the benefit of doing so? Do you have an example for a
practical use case where this makes sense?
> This patch replaces the use of mmap(2) with read(2). If accepted, I
> could give a look to accept /dev/stdout as output file (which is
> currently also required to be a file).
What is the size and performance impact of the suggested change for
typical use cases?
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
Q: Why do PCs have a reset button on the front?
A: Because they are expected to run Microsoft operating systems.
next prev parent reply other threads:[~2014-09-27 12:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 19:33 [U-Boot] [PATCH] tools: mkimage can read input on /dev/stdin Julien Castets
2014-09-27 12:54 ` Wolfgang Denk [this message]
2014-09-27 13:11 ` Julien Castets
2014-09-27 13:25 ` Wolfgang Denk
2014-09-27 17:28 ` Julien Castets
2014-09-27 18:24 ` Wolfgang Denk
2014-09-27 19:06 ` Julien Castets
2014-09-27 21:56 ` Wolfgang Denk
2014-09-27 22:01 ` Marek Vasut
2014-09-27 22:21 ` Wolfgang Denk
2014-09-28 0:16 ` Julien Castets
2014-09-28 6:49 ` Wolfgang Denk
2014-09-28 10:49 ` Julien Castets
2014-09-28 17:48 ` Wolfgang Denk
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=20140927125434.B9C8F382279@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