From: Chase Maupin <chase.mau...@ti.com>
* 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.
Signed-off-by: Chase Maupin <chase.mau...@ti.com>
Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org>
---
meta/conf/machine/include/soc-family.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/machine/include/soc-family.inc
b/meta/conf/machine/include/soc-family.inc
index 612039c..0251da0 100644
--- a/meta/conf/machine/include/soc-family.inc
+++ b/meta/conf/machine/include/soc-family.inc
@@ -1,2 +1,2 @@
# Add SOC_FAMILY to machine overrides so we get access to e.g. 'omap3' and
'ti335x'
-MACHINEOVERRIDES .= "${@['', ':${SOC_FAMILY}']['${SOC_FAMILY}' != '']}"
+MACHINEOVERRIDES =. "${@['', '${SOC_FAMILY}:']['${SOC_FAMILY}' != '']}"
--
1.8.1.5
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
