summaryrefslogtreecommitdiffstats
path: root/conf/machine/imx6qsabresd.conf
diff options
context:
space:
mode:
authorOtavio Salvador <otavio@ossystems.com.br>2013-04-11 10:06:55 -0300
committerOtavio Salvador <otavio@ossystems.com.br>2013-04-17 18:20:22 -0300
commit74af82332fcec03f19f278024ad131c7c6eb3f53 (patch)
tree93e14278c4c38cd7f984dc5097956d5fe48409a7 /conf/machine/imx6qsabresd.conf
parent6c2aaf765191194db83440c79c112d594648ecbf (diff)
downloadmeta-fsl-arm-74af82332fcec03f19f278024ad131c7c6eb3f53.tar.gz
Fix use of SOC_FAMILY as the most right value is preferred
The SOC_FAMILY uses the MACHINEOVERRIDES and it evaluates from left to right. In this case, the most SoC specific value needs to be kept in the right so it take precedence. This has been catch when finding out why i.MX6SL EVK where using the wrong value as entry point, and this was the root cause. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Diffstat (limited to 'conf/machine/imx6qsabresd.conf')
-rw-r--r--conf/machine/imx6qsabresd.conf2
1 files changed, 1 insertions, 1 deletions
diff --git a/conf/machine/imx6qsabresd.conf b/conf/machine/imx6qsabresd.conf
index d5a5192..67bdc65 100644
--- a/conf/machine/imx6qsabresd.conf
+++ b/conf/machine/imx6qsabresd.conf
@@ -5,7 +5,7 @@
5include conf/machine/include/imx-base.inc 5include conf/machine/include/imx-base.inc
6include conf/machine/include/tune-cortexa9.inc 6include conf/machine/include/tune-cortexa9.inc
7 7
8SOC_FAMILY = "mx6q:mx6" 8SOC_FAMILY = "mx6:mx6q"
9 9
10KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx6q-sabresd.dts" 10KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx6q-sabresd.dts"
11 11