Hi Quentin,
On 8/5/2026 12:24 am, Quentin Schulz wrote:
[CAUTION: This email is from outside your organization. Unless you trust the
sender, do not click on links or open attachments as it may be a fraudulent
email attempting to steal your information and/or compromise your computer.]
Hi Alif,
On 5/5/26 3:57 AM, [email protected] wrote:
From: Alif Zakuan Yuslaimi <[email protected]>
Binman will attempt to package kernel.itb during U-Boot build, expecting
Image and linux.dtb files that are not available in standard U-Boot-only
builds. This would cause build warnings with missing blob errors.
Add conditional deletion of the kernel node from binman when FIT is enabled
CONFIG_SOCFPGA_SECURE_VAB_AUTH is not defined.
Why is this specific to socfpga_agilex5_socdk_emmc?
Should we rather guard the definition of &binman/kernel with
defined(CONFIG_SOCFPGA_SECURE_VAB_AUTH) in
arch/arm/dts/socfpga_soc64_fit-u-boot.dtsi instead?
Also, please use CONFIG_IS_ENABLED/IS_ENABLED macros instead of defined()
Cheers,
Quentin
We have been doing this for several of our devices in our downstream,
and for arch/arm/dts/socfpga_agilex-u-boot.dtsi as well as
arch/arm/dts/socfpga_agilex_socdk-u-boot.dtsi in which we have
upstreamed recently.
Thank you for your suggestion. I will proceed with the next submission
with guarding the "kernel" subnode under the binman node in
arch/arm/dts/socfpga_soc64_fit-u-boot.dtsi as well as cleaning up the
mentioned Agilex U-Boot .dts files for v2.
Best regards,
Alif
