From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shawn Guo Date: Mon, 17 Jun 2019 10:16:09 +0800 Subject: [U-Boot] Poplar broken in U-Boot v2019.07-rc4 In-Reply-To: References: <20190611013147.GW7115@bill-the-cat> Message-ID: <20190617021607.GA9201@dragon> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: u-boot@lists.denx.de On Sun, Jun 16, 2019 at 07:36:08PM +0200, Andreas F=C3=A4rber wrote: > Hello, >=20 > 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. > >=20 > > 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. >=20 > 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: >=20 > 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 =3D 0x37000000 > INFO: SPSR =3D 0x3c9 >=20 > 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. >=20 > 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 drive= r") I'm not sure this indicates above commit is problematic or Poplar platform is buggy on DM support though. Shawn