From: Tom Rini <trini@konsulko.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Moiz Imtiaz <moizimtiaz1@gmail.com>,
sjg@chromium.org, u-boot@lists.denx.de,
moiz.imtiaz@skyelectric.com, jehannazkhan@skyelectric.com
Subject: Re: Problem with U-boot | Configuration Signature not being checked while booting
Date: Sat, 11 Sep 2021 17:05:45 -0400 [thread overview]
Message-ID: <20210911210545.GX12964@bill-the-cat> (raw)
In-Reply-To: <561452b36639d218@bloch.sibelius.xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
On Sat, Sep 11, 2021 at 09:18:46PM +0200, Mark Kettenis wrote:
> > From: Moiz Imtiaz <moizimtiaz1@gmail.com>
> > Date: Sat, 11 Sep 2021 23:19:05 +0500
> >
> > Hi Simon,
> >
> > Thanks for the reply. I already followed the steps mentioned in
> > "doc/uImage.FIT/beaglebone_vboot.txt".
> >
> > >I wonder if rpi is not using the devicetree compiled with U-Boot, but
> > instead one provided by the earlier-stage firmware?
> >
> > Not sure, but seems like this is the case. I checked and there isn't any
> > dtb or dts for rpi4 (bcm2711-rpi-4-b) in arc/arm/dts in u-boot. I tried to
> > add the dtb and other dts dtsi
> > <https://github.com/raspberrypi/linux/tree/rpi-5.10.y/arch/arm64/boot/dts/broadcom>files
> > from the raspberry pi Linux and compile them with CONFIG_OF_SEPARATE and
> > CONFIG_OF_EMBED (one at a time) *but it couldn't even boot the U-Boot and
> > it would just give a blank screen*. I wonder why there isn't any device
> > tree in the U-boot repo for RPI4. Is U-boot control FDT not supported by
> > RPI4?
>
> The issue with the rpi4 is that the addresses of devices move around
> based on the version of the Raspberry Pi firmware you're using. And
> possibly on the amount of memory on the board as well. So U-Boot
> pretty much has to use the device tree passed by the firmware since
> the device tree in the U-Boot tree would be wrong for many
> combinations of firmware and hardware.
>
> Simon, this sort of thing is exactly the reason why I think the idea
> of having all U-Boot configuration information in a single device tree
> with the hardware description doesn't work everywhere.
In this case, doesn't the Pi firmware pass along apply overlays and
construct the device tree it's going to pass along, so in this case you
would want to make an "overlay" for the Pi firmware to apply and pass
along to U-Boot, that includes the required information?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-09-11 21:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 20:21 Problem with U-boot | Configuration Signature not being checked while booting Moiz Imtiaz
2021-09-10 4:37 ` Simon Glass
2021-09-11 18:19 ` Moiz Imtiaz
2021-09-11 19:18 ` Mark Kettenis
2021-09-11 21:05 ` Tom Rini [this message]
2021-09-11 21:30 ` Mark Kettenis
2021-09-11 21:34 ` Tom Rini
2021-09-11 21:58 ` Moiz Imtiaz
2021-09-12 15:02 ` Tom Rini
2021-09-12 20:45 ` Moiz Imtiaz
2021-09-15 13:02 ` Tom Rini
2021-09-15 10:13 ` Simon Glass
2021-09-15 10:25 ` François Ozog
2021-09-17 16:21 ` Simon Glass
2021-09-17 17:18 ` François Ozog
2021-09-17 17:55 ` Tom Rini
2021-09-15 11:51 ` Mark Kettenis
2021-09-15 13:35 ` Tom Rini
2021-09-15 13:53 ` François Ozog
2021-09-17 16:21 ` Simon Glass
2021-09-17 17:42 ` Tom Rini
2021-09-18 9:27 ` Simon Glass
2021-09-18 13:24 ` Tom Rini
2021-09-17 16:19 ` Simon Glass
2021-09-17 17:26 ` Tom Rini
2021-09-18 9:27 ` Simon Glass
2021-09-18 9:47 ` Moiz Imtiaz
2021-09-18 10:10 ` Mark Kettenis
2021-09-18 10:26 ` François Ozog
2021-09-18 13:24 ` Moiz Imtiaz
2021-09-18 13:30 ` Moiz Imtiaz
2021-09-20 15:33 ` Tom Rini
2021-09-18 11:15 ` Mark Kettenis
2021-09-18 15:28 ` Simon Glass
2021-09-20 15:38 ` Tom Rini
2021-09-20 15:27 ` Tom Rini
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=20210911210545.GX12964@bill-the-cat \
--to=trini@konsulko.com \
--cc=jehannazkhan@skyelectric.com \
--cc=mark.kettenis@xs4all.nl \
--cc=moiz.imtiaz@skyelectric.com \
--cc=moizimtiaz1@gmail.com \
--cc=sjg@chromium.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