From: Simon Glass <sjg@chromium.org> It is not obvious that PXE supports FIT, but it does, by detecting whether an image is a FIT or not. In many cases a FIT is more convenient than using separate files for the kernel, initrd and devicetree. Really we should promote FIT as an important format, rather than silentily dealing with it if detected. Add a new 'fit' token which indicates that a FIT is being used. When the 'fit' token is used, the expectation is that the devicetree is within the FIT, but this is not required, for now. Signed-off-by: Simon Glass <sjg@chromium.org> --- boot/pxe_parse.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/boot/pxe_parse.c b/boot/pxe_parse.c index bc1a15238b1..633b218a7cd 100644 --- a/boot/pxe_parse.c +++ b/boot/pxe_parse.c @@ -37,6 +37,7 @@ enum token_type { T_KASLRSEED, T_FALLBACK, T_SAY, + T_FIT, T_INVALID }; @@ -72,6 +73,7 @@ static const struct token keywords[] = { {"kaslrseed", T_KASLRSEED,}, {"fallback", T_FALLBACK,}, {"say", T_SAY,}, + {"fit", T_FIT,}, {NULL, T_INVALID} }; @@ -502,6 +504,7 @@ static int parse_label(char **c, struct pxe_menu *cfg) break; case T_KERNEL: case T_LINUX: + case T_FIT: err = parse_label_kernel(c, label); break; case T_APPEND: -- 2.43.0