summaryrefslogtreecommitdiff
path: root/boards.cfg
diff options
context:
space:
mode:
authorGabe Black <gabeblack@chromium.org>2012-10-25 16:31:10 +0000
committerGerald Van Baren <gvb@unssw.com>2012-11-12 23:14:57 -0500
commitd95f6ec7334076a1e4b13f3748ebfd1b58ac90f6 (patch)
treeb45f3e30b135e0af09a7005920205fc8470147f7 /boards.cfg
parent67e1ea26e89e19a550d86d6408f39d815eedaa7f (diff)
downloadu-boot-imx-d95f6ec7334076a1e4b13f3748ebfd1b58ac90f6.zip
u-boot-imx-d95f6ec7334076a1e4b13f3748ebfd1b58ac90f6.tar.gz
u-boot-imx-d95f6ec7334076a1e4b13f3748ebfd1b58ac90f6.tar.bz2
fdt: Add option to default to most compatible conf in a fit image
When booting a fit image with multiple configurations, the user either has to specify which configuration to use explicitly, or there has to be a default defined which is chosen automatically. This change adds an option to change that behavior so that a configuration can be selected explicitly, or the configuration which has the device tree that claims to be compatible with the earliest item in U-Boot's device tree. In other words, if U-Boot claimed to be compatible with A, B, and then C, and the configurations claimed to be compatible with A, D and B, D and D, E, the first configuration, A, D, would be chosen. Both the first and second configurations match, but the first one matches a more specific entry in U-Boot's device tree. The order in the kernel's device tree is ignored. Signed-off-by: Gabe Black <gabeblack@google.com> Commit-Ready: Gabe Black <gabeblack@chromium.org> Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'boards.cfg')
0 files changed, 0 insertions, 0 deletions