sandbox: Remove OF_HOSTFILE
OF_HOSTFILE is used on sandbox configs only. Although it's pretty unique and not causing any confusions, we are better of having simpler config options for the DTB. So let's replace that with the existing OF_BOARD. U-Boot would then have only three config options for the DTB origin. - OF_SEPARATE, build separately from U-Boot - OF_BOARD, board specific way of providing the DTB - OF_EMBED embedded in the u-boot binary(should not be used in production Signed-off-by: Ilias Apalodimas <ilias.apalodimas@linaro.org> Reviewed-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
committed by
Tom Rini
parent
670d657dfb
commit
e7fb789612
@@ -108,10 +108,9 @@ If CONFIG_OF_BOARD is defined, a board-specific routine will provide the
|
||||
devicetree at runtime, for example if an earlier bootloader stage creates
|
||||
it and passes it to U-Boot.
|
||||
|
||||
If CONFIG_OF_HOSTFILE is defined, then it will be read from a file on
|
||||
startup. This is only useful for sandbox. Use the -d flag to U-Boot to
|
||||
specify the file to read, -D for the default and -T for the test devicetree,
|
||||
used to run sandbox unit tests.
|
||||
If CONFIG_SANDBOX is defined, then it will be read from a file on
|
||||
startup. Use the -d flag to U-Boot to specify the file to read, -D for the
|
||||
default and -T for the test devicetree, used to run sandbox unit tests.
|
||||
|
||||
You cannot use more than one of these options at the same time.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user