Hi Moritz,
On 12/1/20 1:19 PM, Moritz Fischer wrote:
Hi Richard,
On Tue, Dec 01, 2020 at 01:30:16PM -0600, Richard Gong wrote:
Can U-Boot determine whether it's the new or old flow? Can you set a
different compatible value in your device-tree, to disambiguate
behaviors?
The boot flow is determined by defconfig during compilation, which means
each boot flow will have its own defconfig.
SDM firmware loads SPL into OCRAM, then SPL will load the apporiate ATF or
U-boot into the DRAM according to the setting of CONFIG_SPL_ATF. If
CONFIG_SPL_ATF=y, SPL loads ATF and then jumps to ATF. ATF setups EL3
environment and initialize the PSCI services.
CONFIG_SPL_ATF is not set for the old boot flow.
So you know at (U-Boot) build time? Can you just pass a different DT to
the kernel in that case?
Yes, we have decided the boot flow at build time. Starting from the next
release, our U-boot will use the ATF boot flow.
Per my limited knowledge in U-boot, I don't think we can follow your
suggestion. Or it will take a lot of efforts to achieve.
I think that back compatibility is your main concern, correct? the issue
does exist with the old boot flow and old firmware, whenever the
customers try to use authentication. Unfortunately we can't update
U-boot or firmware that has been released.
The authentication feature is supported only at the ATF boot flow,
updated kernel and firmware. We will have a well-documented document to
inform our customers that if they want to have authentication feature,
they need to upgrade the latest U-boot, kernel and firmware.
We always encourage our customers to take the latest U-boot, kernel and
firmware releases in their developments.
- Moritz
Regards,
Richard
