mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-22 03:03:05 +00:00
78144826bb
The ti-secure entry contains certificate for binaries that will be loaded or booted by system firmware whereas the ti-secure-rom entry contains certificate for binaries that will be booted by ROM. Support for both these types of certificates is necessary for booting of K3 devices. Reviewed-by: Simon Glass <sjg@chromium.org> [vigneshr@ti.com: fixed inconsist cert generation by multiple packing] Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com> Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
25 lines
495 B
Text
25 lines
495 B
Text
// SPDX-License-Identifier: GPL-2.0+
|
|
|
|
/dts-v1/;
|
|
|
|
/ {
|
|
#address-cells = <1>;
|
|
#size-cells = <1>;
|
|
|
|
binman {
|
|
ti-secure-rom {
|
|
content = <&unsecure_binary>;
|
|
content-sbl = <&unsecure_binary>;
|
|
content-sysfw = <&unsecure_binary>;
|
|
content-sysfw-data = <&unsecure_binary>;
|
|
content-sysfw-inner-cert = <&unsecure_binary>;
|
|
content-dm-data = <&unsecure_binary>;
|
|
combined;
|
|
sysfw-inner-cert;
|
|
dm-data;
|
|
};
|
|
unsecure_binary: blob-ext {
|
|
filename = "ti_unsecure.bin";
|
|
};
|
|
};
|
|
};
|