From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Image copy to ram
Date: Tue, 12 Apr 2011 15:12:17 -0400 [thread overview]
Message-ID: <201104121512.20524.vapier@gentoo.org> (raw)
In-Reply-To: <4DA49E52.3040605@arcor.de>
On Tuesday, April 12, 2011 14:47:46 Matthias Weisser wrote:
> Am 12.04.2011 18:20, schrieb Mike Frysinger:
> > On Tuesday, April 12, 2011 04:01:18 Matthias Wei?er wrote:
> >> I looked into the documentation but I can't find a command which copies
> >> an image from one address to another.
> >
> > you mean 'cp' ?
>
> Well, not exactly. cp doesn't know anything about the size of an image
> and is, compared to a simple memcpy or even an optimized version of
> memcpy, painfully slow which would eat up my expected performance
> improvements. A quick hack showed that a "imcpy" command could save me
> some 400ms on boot time which is about 50% of the total time spend in
> u-boot.
it prob makes more sense to make it an optional subcommand to bootm. however,
i wonder why even bother with the double reads. if we assume that a valid crc
is going to happen the vast majority of the time, we should tailor to that,
and taking a perf hit in the edge cases where the crc is invalid is fine.
in other words, let's see about merging the decompression and verification
steps so that there is only ever one read.
dont compression routines have crc checking built into them anyways ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110412/c2e48aca/attachment.pgp
next prev parent reply other threads:[~2011-04-12 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 8:01 [U-Boot] Image copy to ram Matthias Weißer
2011-04-12 16:20 ` Mike Frysinger
2011-04-12 18:47 ` Matthias Weisser
2011-04-12 19:12 ` Mike Frysinger [this message]
2011-04-12 19:43 ` Matthias Weisser
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=201104121512.20524.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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