aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-08-07 12:18:41 +0200
committerAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-08-10 12:33:38 +0200
commit04b99d9539b0fa239f95a2eef804c0ac864e1944 (patch)
tree1440db9ffb75f092650b57e52f5a685dba92fa47
parentab74def0db93b5b958320ea083de559bc1870537 (diff)
downloadupstream-04b99d9539b0fa239f95a2eef804c0ac864e1944.tar.gz
upstream-04b99d9539b0fa239f95a2eef804c0ac864e1944.tar.bz2
upstream-04b99d9539b0fa239f95a2eef804c0ac864e1944.zip
ramips/mt7628: fix portmap based on board.d port assignment
When comparing to the port assignment in board.d/02_network, a few devices seem to use the wrong setup of mediatek,portmap. The corrects the values for mt76x8 subtarget based on the location of the wan port. A previous cleanup of obviously wrong values has already been done in 7a387bf9a0d7 ("ramips: mt76x8: fix bogus mediatek,portmap") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
-rw-r--r--target/linux/ramips/dts/mt7628an_duzun_dm06.dts2
-rw-r--r--target/linux/ramips/dts/mt7628an_xiaomi_mir4a-100m.dts2
2 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/ramips/dts/mt7628an_duzun_dm06.dts b/target/linux/ramips/dts/mt7628an_duzun_dm06.dts
index 447e0dcf7b..96e60b55f1 100644
--- a/target/linux/ramips/dts/mt7628an_duzun_dm06.dts
+++ b/target/linux/ramips/dts/mt7628an_duzun_dm06.dts
@@ -72,7 +72,7 @@
};
&esw {
- mediatek,portmap = <0x3>;
+ mediatek,portmap = <0x3e>;
mediatek,portdisable = <0x3c>;
};
diff --git a/target/linux/ramips/dts/mt7628an_xiaomi_mir4a-100m.dts b/target/linux/ramips/dts/mt7628an_xiaomi_mir4a-100m.dts
index 377f71186c..009a75a9d0 100644
--- a/target/linux/ramips/dts/mt7628an_xiaomi_mir4a-100m.dts
+++ b/target/linux/ramips/dts/mt7628an_xiaomi_mir4a-100m.dts
@@ -130,7 +130,7 @@
};
&esw {
- mediatek,portmap = <0x2f>;
+ mediatek,portmap = <0x3e>;
mediatek,portdisable = <0x2a>;
};