Hi, On 02/12/17 15:10, Jagan Teki wrote: > + Andre > > On Sat, Dec 2, 2017 at 8:28 PM, Thomas Petazzoni > <[email protected]> wrote: >> Hello, >> >> On Wed, 1 Nov 2017 19:05:45 +0100, Jagan Teki wrote: >> >>> +# Firmware >>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE=y >>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y >>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://github.com/apritzel/arm-trusted-firmware.git"; >>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="sun50iw1p1" >>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="aa75c8da415158a94b82a430b2b40000778e851f" >>> +BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES="bl31" >> >> What is this "bl31" additional variable doing? > > Source build varies based on the exception levels switches, like bl31 > we have bl31, bl2, bl1
Those are not exception levels, but just stages of ATF: BROM loads bl1, which (optionally) loads bl2 and possibly bl31 (if bl2 does not do this). Various platforms can implement only a subset of these stages, the Allwinner port chose to only implement bl31. Technically we should express this in the Makefile snippets, so that "make all" just builds bl31, but that's not easy to do in the Allwinner port. >> Aren't you hijacking the ADDITIONAL_VARIABLES thing to call the bl31 >> make target ? > > Since ADDITIONAL_VARIABLES resembles to use additional parameters for > ATF build, I've treated bl31 as additional variable for this ATF I have the same feeling as Thomas: bl31 is just a make target (instead of "all" and/or "fip"). So it should be treated like this. Using ADDITIONAL_VARIABLES sounds like a hack. Cheers, Andre. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
