From: Davide CASCONE <davide.cascone@st.com>
To: <linux-mtd@lists.infradead.org>
Subject: uboot performances
Date: Fri, 23 Jun 2006 12:55:56 +0200 [thread overview]
Message-ID: <001001c696b3$9aeacf70$253682a4@nap.st.com> (raw)
I'm working with the OMAP5912 OSK platform. I have the boot-loader code and the Linux OS compressed image in a Sibley flash. When I run the system, the boot loader (uBoot) have to copy the Kernel Image (about 700KB) in RAM. It takes about 300ms in order to perform that copy. But I have read some benchmark results in which the copy of the kernel in RAM lasts only 80-100ms. In order to reduce the time of the copy on my platform, the only solution that I found (after checking the memory controller settings) is to modify the copy function memmove (uboot/ lib_generic/string.c). This function performs the copy byte by byte. If I modify this function to perform the copy 4byte by 4byte, the bootloader only takes about 80 ms. Do you think this is a good workaround for this problem? Can you suggest me anything better?
Thanks in advance.
Best Regards,
Davide
next reply other threads:[~2006-06-23 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 10:55 Davide CASCONE [this message]
2006-06-23 12:26 ` uboot performances Josh Boyer
2006-06-23 12:32 ` Gianluca
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='001001c696b3$9aeacf70$253682a4@nap.st.com' \
--to=davide.cascone@st.com \
--cc=linux-mtd@lists.infradead.org \
/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