[TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages
Tom Rini
trini at konsulko.com
Fri Jun 18 19:17:46 CEST 2021
On Thu, Jun 17, 2021 at 04:45:48PM -0700, raghu.ncstate at icloud.com wrote:
[snip]
> I also think it is incorrect to partition platforms into what u-boot/linux boot/embdedded systems do and what “UEFI/private code” does. UEFI is a huge part of the ARM eco-system and is being used fairly extensively and supported across different markets and is not private code.
I don't think "u-boot/linux boot/embedded systems" vs "UEFI/private
code" is the right distinction. It's "device tree/related" vs
"ACPI/related" as the difference between U-Boot (for example) and EDK II
(for another example) on aarch64 booting a system via EFI is that U-Boot
is likely to be passing in a device tree (setting aside what we can do
on x86 as a digression) and EDK II being likely to pass ACPI/related.
In both cases we can quite easily be talking about all of the data
having been written to persistent flash and automatically passed along.
To riff on a phrase, U-Boot can be quite boring too.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210618/7defb1e2/attachment.sig>
More information about the U-Boot
mailing list