mirror of
https://github.com/smaeul/u-boot.git
synced 2025-11-04 05:50:17 +00:00
8ee4ec9bf5
Binman entries can use other executables to compute their data, usually in their ObtainContents() methods. Subclasses of Entry_section would use bintools in their BuildSectionData() method instead, which is called from several places including their Pack(). These binary tools are resolved correctly while building an image from a device-tree description so that they can be used from these methods. However, this is not being done when replacing entries in an image, which can result in an error as the Pack() methods attempt to use them. Collect and resolve entries' bintools also when replacing entries to fix Pack() errors. Add a way to mock bintool usage in the testing entry type and tests that check bintools are being resolved for such an entry. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
40 lines
404 B
Plaintext
40 lines
404 B
Plaintext
// SPDX-License-Identifier: GPL-2.0+
|
|
|
|
/dts-v1/;
|
|
|
|
/ {
|
|
#address-cells = <1>;
|
|
#size-cells = <1>;
|
|
|
|
binman {
|
|
size = <0xc00>;
|
|
allow-repack;
|
|
|
|
u-boot {
|
|
};
|
|
|
|
_testing {
|
|
require-bintool-for-contents;
|
|
require-bintool-for-pack;
|
|
};
|
|
|
|
fdtmap {
|
|
};
|
|
|
|
u-boot2 {
|
|
type = "u-boot";
|
|
};
|
|
|
|
text {
|
|
text = "some text";
|
|
};
|
|
|
|
u-boot-dtb {
|
|
};
|
|
|
|
image-header {
|
|
location = "end";
|
|
};
|
|
};
|
|
};
|