diff options
| author | Paul Spooren <mail@aparcar.org> | 2022-06-07 13:26:43 +0200 |
|---|---|---|
| committer | Paul Spooren <mail@aparcar.org> | 2022-07-29 15:12:49 +0200 |
| commit | a409bd7705154045141e8fde408a33c19dfe9be9 (patch) | |
| tree | 0a38c8a07f749bf05ed1b719d3950660cec01f83 /target/linux/bcm27xx/patches-5.10/950-0361-ARM-dts-Expand-PCIe-space-on-BCM2711.patch | |
| parent | e0d3dc5de195d70f740178fe49b0928ca39ae58f (diff) | |
| download | upstream-a409bd7705154045141e8fde408a33c19dfe9be9.tar.gz upstream-a409bd7705154045141e8fde408a33c19dfe9be9.tar.bz2 upstream-a409bd7705154045141e8fde408a33c19dfe9be9.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>
(cherry picked from commit 2a07270180ed0e295d854d6e9e59c78c40549efc)
Diffstat (limited to 'target/linux/bcm27xx/patches-5.10/950-0361-ARM-dts-Expand-PCIe-space-on-BCM2711.patch')
0 files changed, 0 insertions, 0 deletions