cases?
None. The behaviour is exactly the same.
--
Julien Castets
+33 (0)6.85.20.10.03
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
mmap(2) fails.
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).
>From e107bdc73ee7b2159956cfc753328f9f03c058e8 Mon Sep 17 00:00:00 2001
From: Julien Castets
Date: Fri, 26
asurements?
mmap is useful when you need to make random access in a file, or to
optimize memory: when a file is mmapped, the kernel only loads the
parts of the file that are accessed. In the case of mkimage, the file
is read sequentially (meaning all
On Sep 27, 2014 8:24 PM, "Wolfgang Denk" > OK, so you don't have any real
data, but make a very specific
> statement: "exactly the same."
>
> Sorry, but this is not an answer I'm going to buy.
I'm not sure to understand what you mean. In both cases, the file is copied.
What is bothering you?
is pretty exotic, so it seems a valid
> question to me to try to understand what the extended functionality
> costs.
I understand the use case, in its globality, is pretty exotic.
However, I don't really get why giving /dev/stdin as input is.
Regards,
--
Julien Castets
_
ee files
through stdin.
> You see, even such a simple change like your suggestion needs some
> deeper thought if you want to keep the design consistent. This is why
> I am asking about your use case, and how it would fit into other
> situations.
Indeed!
--
Julien Castets
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
6 matches
Mail list logo
