linux/poky.git/meta/conf/machine/include/soc-family.inc, branch master-test

soc-family.inc: Add a default SOC_FAMILY value

2015-06-03T15:38:45+00:00

Otherwise, if MACHINEOVERRIDES is expanded before SOC_FAMILY is set (which may happen as MACHINEOVERRIDES is included in OVERRIDES) we can see: ExpansionError: Failure expanding variable MACHINEOVERRIDES, expression was ${@['', '${SOC_FAMILY}:']['${SOC_FAMILY}' != '']}p1022ds which triggered exception SyntaxError: EOL while scanning string literal (MACHINEOVERRIDES, line 1) To avoid this, give SOC_FAMILY a default empty value so it doesn't get read as None. (From OE-Core rev: dee005b6e1bc353230f9f27a469b2054a644e542) Signed-off-by: Richard Purdie

soc-family: fix SOC_FAMILY override order

2013-03-10T04:36:50+00:00

* the current order has SOC_FAMILY settings, which are generic settings for a group of devices, overriding the machine specific settings. For example: KERNEL_DEVICETREE_ti33x = "xxxx" KERNEL_DEVICETREE_beaglebone = "yyyy" Should yield "yyyy" when building for the beaglebone because that is a more specific device than ti33x. However, without this change the result is that the value is set to "xxxx" meaning the more generic setting overrides the more specific setting. (From OE-Core rev: 0b836b9d79255a5b2f358fe718c67638f52ecf72) Signed-off-by: Chase Maupin Signed-off-by: Richard Purdie

soc-family.inc: to be included in machine.conf to add SOC_FAMILY to MACHINEOVERRIDE

2012-03-04T13:41:11+00:00

Add a soc-family.inc file that can be included in a machine.conf to enable the use of SOC_FAMILY in MACHINEOVERRIDE, which could be useful to group multiple machines with the same common base. Some examples can be seen in meta-ti BSP layer. (From OE-Core rev: 641cdbc7ee0186053dd541e0dd5fb7b03b1c10d1) Signed-off-by: Denys Dmytriyenko Signed-off-by: Richard Purdie