diff options
| author | Simon Glass | 2019-07-08 14:25:25 -0600 |
|---|---|---|
| committer | Simon Glass | 2019-07-24 12:53:46 -0700 |
| commit | 57460184686f83386712c366cd7722d1aa35f09d (patch) | |
| tree | 0cca8a3cd473c8c542eeda5c7f91e6e3b6d58584 | |
| parent | 488b2251fecd9eeb5241e75947923b114ffbb154 (diff) | |
binman: Update help for new features
A few new features have been added. This has rendered part of the README
obsolete. Update it.
Signed-off-by: Simon Glass <sjg@chromium.org>
| -rw-r--r-- | tools/binman/README | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/tools/binman/README b/tools/binman/README index 1851a4e536d..b067d3b78cf 100644 --- a/tools/binman/README +++ b/tools/binman/README @@ -36,10 +36,9 @@ suitable padding and alignment. It provides a way to process binaries before they are included, by adding a Python plug-in. The device tree is available to U-Boot at run-time so that the images can be interpreted. -Binman does not yet update the device tree with the final location of -everything when it is done. A simple C structure could be generated for -constrained environments like SPL (using dtoc) but this is also not -implemented. +Binman can update the device tree with the final location of everything when it +is done. Entry positions can be provided to U-Boot SPL as run-time symbols, +avoiding device-tree code overhead. Binman can also support incorporating filesystems in the image if required. For example x86 platforms may use CBFS in some cases. |