mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-05 02:51:00 +00:00
5af9ebc4bc
At present if a devicetree blob is included in a vblock it does not deal with updates. This is because the vblock is created once at the start and does not have a method to update itself later, after all the entry contents are finalised. Fix this by adjusting how the vblock is created. Also simplify Image.ProcessEntryContents() since it effectively duplicates the code in Section.ProcessContents(). Signed-off-by: Simon Glass <sjg@chromium.org>
31 lines
643 B
Text
31 lines
643 B
Text
// SPDX-License-Identifier: GPL-2.0+
|
|
/dts-v1/;
|
|
|
|
/ {
|
|
#address-cells = <1>;
|
|
#size-cells = <1>;
|
|
|
|
binman {
|
|
u_boot: u-boot {
|
|
};
|
|
|
|
dtb: u-boot-dtb {
|
|
};
|
|
|
|
/*
|
|
* Put the vblock after the dtb so that the dtb is updated
|
|
* before the vblock reads its data. At present binman does not
|
|
* understand dependencies between entries, but simply
|
|
* iterates again when it thinks something needs to be
|
|
* recalculated.
|
|
*/
|
|
vblock {
|
|
content = <&u_boot &dtb>;
|
|
keyblock = "firmware.keyblock";
|
|
signprivate = "firmware_data_key.vbprivk";
|
|
version = <1>;
|
|
kernelkey = "kernel_subkey.vbpubk";
|
|
preamble-flags = <1>;
|
|
};
|
|
};
|
|
};
|