From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Very slow fatload on bcm2835
Date: Wed, 17 Jun 2015 19:55:40 -0600 [thread overview]
Message-ID: <5582251C.9050303@wwwdotorg.org> (raw)
In-Reply-To: <201506171243.05720.marex@denx.de>
On 06/17/2015 04:43 AM, Marek Vasut wrote:
> On Tuesday, June 16, 2015 at 11:19:11 AM, Michal Marek wrote:
>> On 2015-06-16 06:01, Stephen Warren wrote:
>>> On 06/11/2015 12:35 PM, Jakub Kicinski wrote:
>>>> Hello!
>
> Hi/Ahoj :)
>
>>>> I'm using latest git source of U-Boot on Raspberry Pi Compute Module
>>>> and performance of fatload is quite bad. Does anyone have any clue
>>>> about what can be wrong? Is it the lack of cache?
>>>
>>>> Sample boot log:
>>> ...
>>>
>>>> reading zImage
>>>> 4003816 bytes read in 48930 ms (79.1 KiB/s)
>>>
>>> I see this too. I bisected it to:
>>> 33fe2fb8df01 ARM: mmc: bcm283x: Remove get_timer_us() from mmc driver
>>>
>>> Marek, this is the second symptom I bisected to this patch. Something
>>> seems quite wrong with it. Did changing to the other timer function
>>> change the timer tick rate or something? FWIW, "sleep 10" at the shell
>>> prompt appears to run for the correct amount of time, so I guess it's
>>> not that.
>
> Hmmmm, get_timer() returns msecs, not usecs. I wonder what I was smoking.
> Can you try with the attached diff please (I only compile-tested it) ?
Thanks for the quick fix; it works great.
Tested-by: Stephen Warren <swarren@wwwdotorg.org>
>> I think you meant Marek Va?ut. I'm Marek by last name :).
>
> We're both Czech though ;-)
Oops. Must check my auto-completes more thoroughly!
prev parent reply other threads:[~2015-06-18 1:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 18:35 [U-Boot] Very slow fatload on bcm2835 Jakub Kicinski
2015-06-16 4:01 ` Stephen Warren
2015-06-16 9:19 ` Michal Marek
2015-06-17 10:43 ` Marek Vasut
2015-06-17 13:44 ` Jeroen Hofstee
2015-06-18 12:34 ` Marek Vasut
2015-06-18 1:55 ` Stephen Warren [this message]
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=5582251C.9050303@wwwdotorg.org \
--to=swarren@wwwdotorg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.