diff options
| author | Alexandru Gagniuc <mr.nuke.me@gmail.com> | 2021-03-29 20:05:15 +0300 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2021-04-14 22:23:01 +0300 |
| commit | df51ae767ecb8e5e10c0709a5674e2ef0fe20961 (patch) | |
| tree | f7262fc8dbd3c5e789e0df62fded503061250cfc /doc/uImage.FIT | |
| parent | 35f4f8e6fc670c73fe418f87249ec9b52ada1e14 (diff) | |
| download | u-boot-df51ae767ecb8e5e10c0709a5674e2ef0fe20961.tar.xz | |
Kconfig: Document the limitations of the simple SPL_LOAD_FIT path
The "simple" SPL_LOAD_FIT path is the most compliant with the format
documented in doc/uImage.FIT/source_file_format.txt. The other two
paths to load a FIT are SPL_LOAD_FIT_FULL and the "bootm" command.
Since the Kconfig menu is the most likely place for a new user to see
these options, it seems like the most logical candidate to document
the limitations. This documents the _known_ issues, and is not
intended to be a complete list of all follies.
Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/uImage.FIT')
0 files changed, 0 insertions, 0 deletions