aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/xrx200
diff options
context:
space:
mode:
authorMathias Kresin <dev@kresin.me>2016-09-10 11:05:56 +0200
committerHauke Mehrtens <hauke@hauke-m.de>2017-06-03 16:09:33 +0200
commit254bf7961e57f65bad849dbab4b135d2a73b1f9b (patch)
tree9ca9f4753a8c74edb46a245598f69ec9a49f8911 /target/linux/lantiq/xrx200
parentb78bcdf6195c6ead5095489e8bb5e85eece44622 (diff)
downloadupstream-254bf7961e57f65bad849dbab4b135d2a73b1f9b.tar.gz
upstream-254bf7961e57f65bad849dbab4b135d2a73b1f9b.tar.bz2
upstream-254bf7961e57f65bad849dbab4b135d2a73b1f9b.zip
lantiq: xrx200: use vlan for ethernet wan port
Using the lantiq,wan device tree property for one interface node and the lantiq,switch device tree property for another interface node at the same time was never intended/isn't supported at the moment. The property is meant to be used in two phy operation mode where one phy is assigned to an interface without lantiq,* device tree property and the other phy is assigned to an interface with the lantiq,wan device property to have two netdevs. If both properties are used at the same time, the lantiq,wan interface is shown as independent netdev but not able to operate independent. The port needs to be managed via swconfig. These dependency is not obvious and fooled already a lot of users. Add a default WAN vlan for xrx200 devices having an ethernet WAN port and remove the lantiq,wan device tree property. Leave it up to the user to set the ethernet WAN port as default WAN interface or to use this port as additional LAN port. Signed-off-by: Mathias Kresin <dev@kresin.me>
Diffstat (limited to 'target/linux/lantiq/xrx200')
0 files changed, 0 insertions, 0 deletions