From: Shawn Guo <shawn.guo@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Poplar broken in U-Boot v2019.07-rc4
Date: Mon, 17 Jun 2019 10:16:09 +0800 [thread overview]
Message-ID: <20190617021607.GA9201@dragon> (raw)
In-Reply-To: <a690037c-74c9-3583-5ec9-17a5cb47a5e0@suse.de>
On Sun, Jun 16, 2019 at 07:36:08PM +0200, Andreas Färber wrote:
> Hello,
>
> Am 11.06.19 um 03:31 schrieb Tom Rini:
> > It's release day and here is v2019.07-rc4. At this point, I know we
> > have some regression fixes for i.MX that are coming, and I'm expecting a
> > fix to the build time failure for tinker-rk3288.
> >
> > To repeat myself about DM migration deadlines, first, let me say again,
> > that DM is not required for SPL. This comes up enough that I want to
> > say it again here. Next, if there is active progress on converting
> > things, we'll keep from pulling the code out. This is why for example,
> > we haven't yet pulled out a lot of deprecated SPI code. Some of it is
> > still in progress on being converted, so I need to update the series I
> > posted after the last -rc to remove still less drivers.
>
> I've noticed that Poplar board is regressing with v2019.07-rc4 compared
> to v2019.04. It doesn't even show a U-Boot version banner:
>
> INFO: Boot BL33 from 0x37000000 for 0 Bytes
> NOTICE: BL31: v2.1(debug):
> NOTICE: BL31: Built : 16:00:26, Jun 16 2019
> INFO: ARM GICv2 driver initialized
> INFO: BL31: Initializing runtime services
> WARNING: BL31: cortex_a53: CPU workaround for 819472 was missing!
> WARNING: BL31: cortex_a53: CPU workaround for 824069 was missing!
> WARNING: BL31: cortex_a53: CPU workaround for 827319 was missing!
> INFO: BL31: cortex_a53: CPU workaround for 855873 was applied
> INFO: BL31: InitINFO: BL31: Preparing for EL3 exit to normal world
> INFO: Entry point address = 0x37000000
> INFO: SPSR = 0x3c9
>
> I'm using TF-A v2.1 with the pending eMMC fix from
> https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/1230
> but same issue without that patch.
>
> I don't see any report or fix for this yet - is this related to DM?
Thanks for reporting, Andreas. I just ran a git bisect which points to
commit below.
3a7c45f6a772 ("simple-bus: add DM_FLAG_PRE_RELOC flag to simple-bus driver")
I'm not sure this indicates above commit is problematic or Poplar
platform is buggy on DM support though.
Shawn
next prev parent reply other threads:[~2019-06-17 2:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 1:31 [U-Boot] [ANN] U-Boot v2019.07-rc4 released Tom Rini
2019-06-11 2:56 ` [U-Boot] [U-Boot-Board-Maintainers] " Marek Vasut
2019-06-11 11:15 ` Tom Rini
2019-06-11 13:39 ` Marek Vasut
2019-06-11 5:38 ` Lukasz Majewski
2019-06-16 17:36 ` [U-Boot] Poplar broken in U-Boot v2019.07-rc4 Andreas Färber
2019-06-17 2:16 ` Shawn Guo [this message]
2019-06-17 2:19 ` Bin Meng
2019-06-17 2:31 ` Shawn Guo
2019-06-22 14:55 ` [U-Boot] [ANN] U-Boot v2019.07-rc4 released Simon Glass
2019-06-22 15:08 ` [U-Boot] [U-Boot-Custodians] " Marek Vasut
2019-06-22 15:10 ` [U-Boot] [U-Boot-Board-Maintainers] " Andreas Färber
2019-06-22 18:15 ` Simon Glass
2019-06-22 19:08 ` Andreas Färber
2019-06-22 19:14 ` Simon Glass
2019-06-22 19:49 ` Andreas Färber
2019-06-24 13:56 ` Simon Glass
2019-06-24 17:10 ` [U-Boot] [U-Boot-Custodians] " Marek Vasut
2019-06-25 0:10 ` Simon Glass
2019-06-22 19:12 ` Heinrich Schuchardt
2019-06-22 19:43 ` Marek Vasut
2019-06-24 15:29 ` Tom Rini
2019-06-25 11:10 ` [U-Boot] [U-Boot-Board-Maintainers] [U-Boot-Custodians] " Neil Armstrong
2019-06-25 12:04 ` Tom Rini
2019-06-30 10:34 ` Matwey V. Kornilov
2019-07-01 7:23 ` Neil Armstrong
2019-07-02 16:04 ` [U-Boot] [U-Boot-Custodians] [U-Boot-Board-Maintainers] " Troy Benjegerdes
2019-07-02 17:03 ` Marek Vasut
2019-07-03 15:59 ` Simon Glass
2019-07-03 16:04 ` [U-Boot] [U-Boot-Board-Maintainers] [U-Boot-Custodians] " Tom Rini
2019-07-03 16:22 ` Troy Benjegerdes
2019-07-03 19:34 ` Heinrich Schuchardt
2019-06-25 3:51 ` [U-Boot] [U-Boot-Custodians] [U-Boot-Board-Maintainers] " Heiko Schocher
2019-06-30 10:32 ` Matwey V. Kornilov
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=20190617021607.GA9201@dragon \
--to=shawn.guo@linaro.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