aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/mvebu/base-files
diff options
context:
space:
mode:
authorPaul Spooren <mail@aparcar.org>2020-04-10 00:14:21 -1000
committerAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-06-05 21:54:43 +0200
commitdf6f3090c48e3bafa0ace7450488b0a20a8074fb (patch)
treeb0f3285075a3b7544a588253d7c984e083bf6af8 /target/linux/mvebu/base-files
parent8c31afb978016ef71fa3bf0d4db583cf6970042b (diff)
downloadupstream-df6f3090c48e3bafa0ace7450488b0a20a8074fb.tar.gz
upstream-df6f3090c48e3bafa0ace7450488b0a20a8074fb.tar.bz2
upstream-df6f3090c48e3bafa0ace7450488b0a20a8074fb.zip
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>
Diffstat (limited to 'target/linux/mvebu/base-files')
0 files changed, 0 insertions, 0 deletions