f3210db348
Some packages require different scripts, configuration files or installations depending on the wireless chip assembled on the target. In general, the way to support both chips in one image is to have the recipes install both versions of the aforementioned files, then leave only the strictly necessary version once the wireless chip can be deduced. In the case of the init-ifupdown recipe, this involves installing temporary configuration fragments that are later erased. In the case of the standby script, the logic can be implemented in a single file. https://onedigi.atlassian.net/browse/DEL-7661 https://onedigi.atlassian.net/browse/DEL-7666 Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com> |
||
|---|---|---|
| .. | ||
| ccimx6 | ||
| ccimx6sbc | ||
| ccimx6ul | ||
| ccimx8m | ||
| ccimx8x | ||
| use-mainline-bsp | ||
| 0001-hcitool-do-not-show-unsupported-refresh-option.patch | ||
| 0002-hcitool-increase-the-shown-connection-limit-to-20.patch | ||
| bluetooth-init.service | ||
| bluetooth.service-add-customizations.patch | ||
| main.conf | ||