summaryrefslogtreecommitdiffstats
path: root/doc/README.semihosting
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2016-02-22 22:55:51 -0700
committerTom Rini <trini@konsulko.com>2016-03-14 19:18:28 -0400
commit8e35bb07eb68e524804f2ef53dd18c7cec0b06fc (patch)
tree6e4b4062aad571ec3b94243d06723bfc09fe74b6 /doc/README.semihosting
parentcef2e51489567260857984c3e95d98eb03c97fe9 (diff)
downloadtalos-obmc-uboot-8e35bb07eb68e524804f2ef53dd18c7cec0b06fc.tar.gz
talos-obmc-uboot-8e35bb07eb68e524804f2ef53dd18c7cec0b06fc.zip
mkimage: Support automatic creating of a FIT without a .its
At present, when generating a FIT, mkimage requires a .its file containing the structure of the FIT and referring to the images to be included. Creating the .its file is a separate step that makes it harder to use FIT. This is not required for creating legacy images. Often the FIT is pretty standard, consisting of an OS image, some device tree files and a single configuration. We can handle this case automatically and avoid needing a .its file at all. To start with, support automatically generate the FIT using a new '-f auto' option. Initially this only supports adding a single image (e.g. a linux kernel) and a single configuration. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/README.semihosting')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud