Certain platforms share a processor family but need to be differentiated between them. DEY was using the variable DIGI_FAMILY as the SOM name rather than the family. It becomes useful to have both (DIGI_SOM as the more specific, and DIGI_FAMILY as the more generic). This is the case, for example, of: - ccmp1 (family) - ccmp15 (SOM) - ccmp13 (SOM) - ccimx8m (family) - ccimx8mm (SOM) - ccimx8mn (SOM) Both variables are used on the machine overrides. Where DIGI_FAMILY was used, use now DIGI_SOM. Signed-off-by: Hector Palacios <hector.palacios@digi.com> |
||
|---|---|---|
| .. | ||
| alsa-state | ||
| ath-prop-tools | ||
| digi-sc-firmware | ||
| firmware-atheros | ||
| firmware-murata | ||
| firmware-qualcomm | ||
| formfactor | ||
| libedgetpu | ||
| libubootenv | ||
| tensorflow-lite | ||
| trustfence-cst | ||
| trustfence-stm-signtools | ||
| u-boot | ||
| usbutils | ||