mvebu: rename Linksys devices based on their common names
authorPaul Spooren <mail@aparcar.org>
Fri, 10 Apr 2020 10:14:21 +0000 (00:14 -1000)
committerAdrian Schmutzler <freifunk@adrianschmutzler.de>
Fri, 5 Jun 2020 19:54:43 +0000 (21:54 +0200)
commitdf6f3090c48e3bafa0ace7450488b0a20a8074fb
treeb0f3285075a3b7544a588253d7c984e083bf6af8
parent8c31afb978016ef71fa3bf0d4db583cf6970042b
mvebu: rename Linksys devices based on their common names

The Linksys devices in mvebu target feature a mixed naming,
where parts are based on the official product name (device
node, image; e.g. WRT3200ACM) and parts are based on the
internal code name (DTS file name, compatible, LED labels;
e.g. rango). This inconsistent naming has been perceived
as quite confusing.

A recent attempt by Paul Spooren to harmonize this naming
in kernel has been declined there. However, for us it still
makes sense to apply at least a part of these changes
locally.

Primarily, this patch changes the compatible in DTS and thus
the board name used in various scripts to have them in line
with the device, model and image names. Due to the recent
switch from swconfig to DSA, this allows us to drop
SUPPORTED_DEVICES and thus prevent seamless upgrade between
these incompatible setups.

However, this does not include the LED label rename from
Paul's initial patch: I don't think it's worth keeping the
enormous diff locally for this case, as we can implement
this much easier in 01_leds if we have to live with the
inconsistency anyway.

Signed-off-by: Paul Spooren <mail@aparcar.org>
[rebase, extend to all devices, drop DT LED changes]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
22 files changed:
package/boot/uboot-envtools/files/mvebu
target/linux/mvebu/cortexa9/base-files/etc/board.d/01_leds
target/linux/mvebu/cortexa9/base-files/etc/board.d/02_network
target/linux/mvebu/cortexa9/base-files/etc/init.d/bootcount
target/linux/mvebu/cortexa9/base-files/etc/uci-defaults/03_wireless
target/linux/mvebu/cortexa9/base-files/etc/uci-defaults/04_mambafan
target/linux/mvebu/cortexa9/base-files/lib/preinit/81_linksys_syscfg
target/linux/mvebu/cortexa9/base-files/lib/upgrade/platform.sh
target/linux/mvebu/files-4.19/arch/arm/boot/dts/armada-385-linksys-venom.dts
target/linux/mvebu/files-5.4/arch/arm/boot/dts/armada-385-linksys-venom.dts
target/linux/mvebu/image/cortexa9.mk
target/linux/mvebu/patches-4.19/005-linksys_hardcode_nand_ecc_settings.patch
target/linux/mvebu/patches-4.19/230-armada-xp-linksys-mamba-broken-idle.patch
target/linux/mvebu/patches-4.19/231-armada-xp-linksys-mamba-wan.patch
target/linux/mvebu/patches-4.19/241-linksys-use-eth0-as-cpu-port.patch
target/linux/mvebu/patches-4.19/250-adjust-compatible-for-linksys.patch [new file with mode: 0644]
target/linux/mvebu/patches-4.19/415-ARM-dts-armada388-clearfog-document-MPP-usage.patch
target/linux/mvebu/patches-5.4/005-linksys_hardcode_nand_ecc_settings.patch
target/linux/mvebu/patches-5.4/230-armada-xp-linksys-mamba-broken-idle.patch
target/linux/mvebu/patches-5.4/231-armada-xp-linksys-mamba-wan.patch
target/linux/mvebu/patches-5.4/241-linksys-use-eth0-as-cpu-port.patch
target/linux/mvebu/patches-5.4/250-adjust-compatible-for-linksys.patch [new file with mode: 0644]