sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

soc-family: fix SOC_FAMILY override order 

* 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 <Chase.Maupin@ti.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Chase Maupin 2013-03-08 11:51:04 -06:00 committed by Richard Purdie
parent 0c02924f63
commit 5ecdb3edba
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
meta/conf/machine/include/soc-family.inc
View File

@ -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}' != '']}"