summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorErich E. Hoover <[email protected]>2026-06-12 09:04:54 -0600
committerMichal Simek <[email protected]>2026-07-08 08:55:51 +0200
commitcc0d3f546063383b6547ffe850f61818eae8c700 (patch)
tree3cdbf240fd53c5f4a25e9b05723eaf6f472c6fc0 /drivers
parent71c54b9769bfe43c72908678921537819cf38db6 (diff)
mkimage: allow zynqmpbif to use a register initialization file
The ZynqMP Boot Image Format allows specifying the register initialization file with the "[init]" attribute. Since this feature is already supported by the "zynqmpimage" backend, this commit leverages that existing capability to add support for the "[init]" attribute in the zynqmpbif backend: https://docs.amd.com/r/en-US/ug1283-bootgen-user-guide/init This currently uses the same register initialization file format as zynqmpimage (ASCII text hex values with each line composed of a pair of register address and value), for example: === 0xff003248 0x12345678 === It is not, yet, compatible with the format used by bootgen: https://docs.amd.com/r/en-US/ug1283-bootgen-user-guide/Initialization-Pairs-and-INT-File-Attribute Use this feature, with other zynqmpbif options, like so: === image : { [init] reginit.int [bootloader] fsbl.elf [pmufw_image] pmufw.elf [destination_cpu=a53-0, exception_level=el-3] bl31.elf [destination_cpu=a53-0, exception_level=el-2, load=0x08000000, startup=0x08000000] u-boot.bin } === Signed-off-by: Erich E. Hoover <[email protected]> Signed-off-by: Michal Simek <[email protected]> Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions