From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Regression in U-boot v2019-07-rcX
Date: Wed, 12 Jun 2019 16:23:37 +0300 [thread overview]
Message-ID: <20190612132337.GM9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190612131825.GL9224@smile.fi.intel.com>
On Wed, Jun 12, 2019 at 04:18:25PM +0300, Andy Shevchenko wrote:
> Hi!
>
> I have noticed today the regression in newer U-Boot.
> For now I'm not sure which version is affected first. At least v2019.07-rc4
> behaves badly.
>
> Under badly I mean the following. Consider the output at the boot time:
>
> U-Boot 2019.07-rc4-00012-gcea7942d57 (Jun 12 2019 - 16:08:09 +0300)
>
> CPU: Intel(R) Atom(TM) CPU U1000 @ 500MHz
> DRAM: 980.6 MiB
> MMC: mmc at ff3fc000: 0, mmc at ff3fa000: 1
> Loading Environment from MMC... OK
> In: serial
> Out: serial
> Err: serial
> Net: No ethernet found.
> Hit any key to stop autoboot: 0
>
> Note lines started with DRAM: and MMC:. Now the 4 seconds (!) time is passed
> between them.
>
> On top of that DFU seems twice slower (on the glance, I haven't measure with
> `time` yet).
>
> Any ideas, while I'll try to allocate some time to investigate myself?
>
> P.S. The board I'm testing with is Intel Edison. I think no need to tell that
> nothing has been changed except the base (I'm rebased my stuff on top of latest
> and greatest U-Boot releases).
v2019.07-rc1 is NOT affected!
The time difference with DFU:
-rc1: real 0m1.114s
-rc4: real 0m2.691s
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-06-12 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 13:18 [U-Boot] Regression in U-boot v2019-07-rcX Andy Shevchenko
2019-06-12 13:23 ` Andy Shevchenko [this message]
2019-06-12 13:37 ` Lukasz Majewski
2019-06-12 14:00 ` Andy Shevchenko
2019-06-12 13:49 ` Andy Shevchenko
2019-06-12 14:07 ` Bin Meng
2019-06-17 7:49 ` Andy Shevchenko
2019-06-17 9:51 ` Simon Glass
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=20190612132337.GM9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--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