diff options
| author | Alexandru Gagniuc <mr.nuke.me@gmail.com> | 2021-04-01 13:25:31 -0500 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2021-04-14 16:02:43 -0400 |
| commit | 033ac4ebbad82241e2d7da3ead662ccb495b9e89 (patch) | |
| tree | 613d46ebfa0cefd2362862efb27dfd3bec1d680d /doc | |
| parent | 47b6f7f8451117546dd12af3eccd58961a9f7f05 (diff) | |
| download | u-boot-033ac4ebbad82241e2d7da3ead662ccb495b9e89.tar.gz | |
image-fit: Accept OP-TEE images when booting a FIT
OP-TEE images are normally packaged with
type = "tee;
os = "tee";
However, fit_image_load() thinks that is somehow invalid. However if
they were declared as type = "kernel", os = "linux", fit_image_load()
would happily accept them and allow the boot to continue. There is no
technical limitation to excluding "tee".
Allowing "tee" images is useful in a boot flow where OP-TEE is
executed before linux.
In fact, I think it's unintuitive for a "load"ing function to also do
parsing and contain a bunch ad-hoc heuristics that only its caller
might know. But I don't make the rules, I just write fixes. In more
polite terms: refactoring the fit_image API is beyond the scope of
this change.
Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions