summaryrefslogtreecommitdiffstats
path: root/meta-yocto-bsp/recipes-core
diff options
context:
space:
mode:
authorLee Nipper <lee.nipper@linux.com>2015-08-12 23:08:52 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-08-19 18:05:42 +0100
commit7ed4a91863252c60e5c6c8997d6dac99b85854bc (patch)
tree0edc950a22165948655e3ec39c06cbfa13dff393 /meta-yocto-bsp/recipes-core
parentd4618ff16753cd176b1cd661e91bab18c0a42249 (diff)
downloadpoky-7ed4a91863252c60e5c6c8997d6dac99b85854bc.tar.gz
u-boot.inc: Add UBOOT_BINARY sym links for UBOOT_CONFIG types
An additional use case of UBOOT_CONFIG is when a machine has applicability to boards of the same architecture but different in other ways to require a different UBOOT_BINARY build. The UBOOT_CONFIG default value can be a list of these board types. For example: UBOOT_CONFIG ??= "boardA boardB" UBOOT_CONFIG[boardA] = "boardA_defconfig" UBOOT_CONFIG[boardB] = "boardB_defconfig" Change do_install and do_deploy sections which process a UBOOT_CONFIG list to create short symbolic links to each of the config types for UBOOT_BINARY. This is similar to the links currently being created for SPL_BINARY when it is defined with a UBOOT_CONFIG list. For the above example, and UBOOT_BINARY as u-boot.bin, the additional symbolic links created in the DEPLOYDIR would be u-boot.bin-boardA u-boot.bin-boardB (From OE-Core rev: 12551f4ca214cfc2528b42da8574a6622228ce0b) Signed-off-by: Lee Nipper <lee.nipper@linux.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto-bsp/recipes-core')
0 files changed, 0 insertions, 0 deletions