public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools: mkimage can read input on /dev/stdin
Date: Sun, 28 Sep 2014 00:01:26 +0200	[thread overview]
Message-ID: <201409280001.26383.marex@denx.de> (raw)
In-Reply-To: <20140927215655.365B9380044@gemini.denx.de>

On Saturday, September 27, 2014 at 11:56:55 PM, Wolfgang Denk wrote:

Hello Wolfgang,

> Dear Julien,
> 
> In message <CADF714bLG21jobjTnbUbWqsyj3xbzL+Fb+WBfcrq8YH4-
ugm5Q@mail.gmail.com> you wrote:
> > I'm not sure to understand what you mean. In both cases, the file is
> > copied.
> > 
> > What is bothering you?
> 
> I asked:
> | What is the size and performance impact of the suggested change for
> | typical use cases?
> 
> Can you please provide values for the size of the binary and the
> execution time?
> 
> It's not really critical, but I'd like to understand the impact of
> your changes.  You use case is pretty exotic, so it seems a valid
> question to me to try to understand what the extended functionality
> costs.

Won't it be better to focus on the overall concept first and dig in the finer 
details later ?

I think right now, the question is -- do we want to support stdin as a source of 
payload for mkimage or not at all?

Best regards,
Marek Vasut

  reply	other threads:[~2014-09-27 22:01 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
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 [this message]
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=201409280001.26383.marex@denx.de \
    --to=marex@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