aboutsummaryrefslogtreecommitdiffstats
path: root/include/trusted-firmware-a.mk
diff options
context:
space:
mode:
authorPaul Spooren <mail@aparcar.org>2022-06-07 13:26:43 +0200
committerPaul Spooren <mail@aparcar.org>2022-06-09 17:14:28 +0200
commit2a07270180ed0e295d854d6e9e59c78c40549efc (patch)
tree02a3add206a23f26ab7ed087f28c131bd72c856b /include/trusted-firmware-a.mk
parentab1f3a87063b94f485bd582f32a066b80007bac9 (diff)
downloadupstream-2a07270180ed0e295d854d6e9e59c78c40549efc.tar.gz
upstream-2a07270180ed0e295d854d6e9e59c78c40549efc.tar.bz2
upstream-2a07270180ed0e295d854d6e9e59c78c40549efc.zip
octeon: add SUPPORTED_DEVICES to er/erlite
Using the BOARD_NAME variable results for both er and erlite devices to identify themselfs as `er` and `erlite` (via `ubus call system board`). This is problematic when devices search for firmware upgrades since the OpenWrt profile is actually called `ubnt_edgerouter` and `ubnt_edgerouter-lite`. By adding the `SUPPORTED_DEVICE` a mapping is created to point devices called `er` or `erlite` to the corresponding profile. FIXES: https://github.com/openwrt/asu/issues/348 Signed-off-by: Paul Spooren <mail@aparcar.org>
Diffstat (limited to 'include/trusted-firmware-a.mk')
0 files changed, 0 insertions, 0 deletions