aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/mt7620a_zbtlink_zbt-ape522ii.dts
diff options
context:
space:
mode:
authorAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-08-03 23:11:01 +0200
committerAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-08-07 13:01:18 +0200
commit7c07a0f4c335bd79b0cac3d91192e76a42bc4e18 (patch)
tree1282e56d6b5af269339bdf94f06cc5c0684e661b /target/linux/ramips/dts/mt7620a_zbtlink_zbt-ape522ii.dts
parentc487cf8e94cbdf582dfc3c2bdaab913a146a2100 (diff)
downloadupstream-7c07a0f4c335bd79b0cac3d91192e76a42bc4e18.tar.gz
upstream-7c07a0f4c335bd79b0cac3d91192e76a42bc4e18.tar.bz2
upstream-7c07a0f4c335bd79b0cac3d91192e76a42bc4e18.zip
ramips/mt7620: fix portmap based on board.d port assignment
When comparing to the port assignment in board.d/02_network, many devices seem to use the wrong setup of mediatek,portmap. The corrects the values for mt7620 subtarget based on the location of the wan port. A previous cleanup of obviously wrong values has already been done in d3c0a944059b ("ramips: mt7620/mt7621: remove invalid mediatek,portmap") Cc: Sungbo Eo <mans0n@gorani.run> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Diffstat (limited to 'target/linux/ramips/dts/mt7620a_zbtlink_zbt-ape522ii.dts')
-rw-r--r--target/linux/ramips/dts/mt7620a_zbtlink_zbt-ape522ii.dts2
1 files changed, 1 insertions, 1 deletions
diff --git a/target/linux/ramips/dts/mt7620a_zbtlink_zbt-ape522ii.dts b/target/linux/ramips/dts/mt7620a_zbtlink_zbt-ape522ii.dts
index 4aa404542f..53d98cf35a 100644
--- a/target/linux/ramips/dts/mt7620a_zbtlink_zbt-ape522ii.dts
+++ b/target/linux/ramips/dts/mt7620a_zbtlink_zbt-ape522ii.dts
@@ -114,7 +114,7 @@
mtd-mac-address = <&factory 0x4>;
- mediatek,portmap = "wllll";
+ mediatek,portmap = "llllw";
};
&wmac {