| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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>
|
|
|
MACHINEOVERRIDE
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 <denys@ti.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
