diff options
| author | Heinrich Schuchardt <xypron.glpk@gmx.de> | 2021-03-02 08:07:19 +0100 |
|---|---|---|
| committer | Heinrich Schuchardt <xypron.glpk@gmx.de> | 2021-03-07 17:37:26 +0100 |
| commit | 7d3eff3412886f277c724a9effcbe545c4cdd5b5 (patch) | |
| tree | fab87d3307e5c4902c07ff4ab630a9a709bc6daa /configs/boston64r2_defconfig | |
| parent | e91789e2f6611c0d7f3510691c154e524e7cfa43 (diff) | |
| download | u-boot-7d3eff3412886f277c724a9effcbe545c4cdd5b5.tar.gz u-boot-7d3eff3412886f277c724a9effcbe545c4cdd5b5.tar.xz u-boot-7d3eff3412886f277c724a9effcbe545c4cdd5b5.zip | |
efi_loader: correct uboot_bin_env.its file format
Up to now the EFI capsule Python tests were always skipped. The reason is
that mkimage fails with:
uboot_bin_env.its:13.21-23.5: Warning (unit_address_vs_reg):
/images/u-boot-bin@100000: node has a unit name, but no reg property
uboot_bin_env.its:24.21-34.5: Warning (unit_address_vs_reg):
/images/u-boot-env@150000: node has a unit name, but no reg property
If a unit in a device-tree has an address, a reg property must be provided.
But adding a reg property is not the solution here.
Since 2017 unit addresses are disallowed for FIT,
cf. common/image-fit.c:1624.
So remove the unit addresses in uboot_bin_env.its.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Diffstat (limited to 'configs/boston64r2_defconfig')
0 files changed, 0 insertions, 0 deletions