Paul Spooren a409bd7705 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> (cherry picked from commit 2a07270180)		2022-07-29 15:12:49 +02:00
..
imagebuilder	imagebuilder: export SOURCE_DATE_EPOCH to environment	2022-04-10 16:32:20 +01:00
linux	octeon: add SUPPORTED_DEVICES to er/erlite	2022-07-29 15:12:49 +02:00
llvm-bpf	llvm-bpf: fix rebuild check for generating tarball	2021-11-26 11:37:19 +01:00
sdk	sdk: add spidev-test to the bundle of userspace sources	2022-07-22 22:26:26 +02:00
toolchain	toolchain: switch packaged toolchain to tar.xz	2021-10-21 08:25:38 -10:00
Config.in	base-files: add eMMC sysupgrade support	2021-12-02 20:42:58 +00:00
Makefile	tools/llvm-bpf: move tarball packing to target/llvm-bpf	2021-11-22 12:00:40 +01:00