From: Frank Wunderlich <frank-w@public-files.de>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, erkin.bozoglu@xeront.com
Subject: Aw: Re: Re: Re: Re: [PATCH v3 0/5] arm: dts: mt7623: relocate gmacs, mt7530 switch, and add port@5
Date: Wed, 12 Apr 2023 17:11:17 +0200 [thread overview]
Message-ID: <trinity-489cdc3b-e861-49d0-b1ec-e964f00388df-1681312277092@3c-app-gmx-bap50> (raw)
In-Reply-To: <703ad8a8-f84e-6404-4cce-5386bfaa2bd7@arinc9.com>
Hi
> Gesendet: Mittwoch, 12. April 2023 um 16:31 Uhr
> Von: "Arınç ÜNAL" <arinc.unal@arinc9.com>
> > looks good so far, but i have not managed how to change dsa master from the preferred port (eth0) to the second one...
> > any idea how the correct syntax is for iproute2?
>
> https://www.kernel.org/doc/html/latest/networking/dsa/configuration.html#affinity-of-user-ports-to-cpu-ports
>
> In short: ip link set lan0 type dsa conduit eth1
thanks, it changes the master when i upgrade iproute to 6.1 (from debian bullseye-backports), but i cannot do any traffic on it after switching to gmac1...
5: wan@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether f2:d2:51:56:cd:3d brd ff:ff:ff:ff:ff:ff
inet 192.168.0.11/24 scope global wan
valid_lft forever preferred_lft forever
see no p5-TX/gmac-rx
root@bpi-r2:~# ethtool -S eth1
NIC statistics:
tx_bytes: 5156
tx_packets: 61
tx_skip: 0
tx_collisions: 0
rx_bytes: 0
rx_packets: 0
rx_overflow: 0
rx_fcs_errors: 0
rx_short_errors: 0
rx_long_errors: 0
rx_checksum_errors: 0
rx_flow_control_packets: 0
rx_xdp_redirect: 0
rx_xdp_pass: 0
rx_xdp_drop: 0
rx_xdp_tx: 0
rx_xdp_tx_errors: 0
tx_xdp_xmit: 0
tx_xdp_xmit_errors: 0
p05_TxDrop: 0
p05_TxCrcErr: 0
p05_TxUnicast: 0
p05_TxMulticast: 0
p05_TxBroadcast: 0
p05_TxCollision: 0
p05_TxSingleCollision: 0
p05_TxMultipleCollision: 0
p05_TxDeferred: 0
p05_TxLateCollision: 0
p05_TxExcessiveCollistion: 0
p05_TxPause: 0
p05_TxPktSz64: 0
p05_TxPktSz65To127: 0
p05_TxPktSz128To255: 0
p05_TxPktSz256To511: 0
p05_TxPktSz512To1023: 0
p05_Tx1024ToMax: 0
p05_TxBytes: 0
p05_RxDrop: 0
p05_RxFiltering: 16
p05_RxUnicast: 11
p05_RxMulticast: 38
p05_RxBroadcast: 12
p05_RxAlignErr: 0
p05_RxCrcErr: 0
p05_RxUnderSizeErr: 0
p05_RxFragErr: 0
p05_RxOverSzErr: 0
p05_RxJabberErr: 0
p05_RxPause: 0
p05_RxPktSz64: 17
p05_RxPktSz65To127: 44
p05_RxPktSz128To255: 0
p05_RxPktSz256To511: 0
p05_RxPktSz512To1023: 0
p05_RxPktSz1024ToMax: 0
p05_RxBytes: 5156
p05_RxCtrlDrop: 0
p05_RxIngressDrop: 0
p05_RxArlDrop: 0
maybe i miss something?
i'm not sure it is a problem with richards Patch or p5/gmac1
> > at least vladimirs patch should be included when applying this series
>
> I'm currently cleaning up the DSA driver, I'll get to this at some point.
regards Frank
next prev parent reply other threads:[~2023-04-12 15:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 18:25 [PATCH v3 0/5] arm: dts: mt7623: relocate gmacs, mt7530 switch, and add port@5 arinc9.unal
2023-02-10 18:25 ` [PATCH v3 1/5] arm: dts: mt7623: add gmacs to mt7623.dtsi arinc9.unal
2023-02-10 18:25 ` [PATCH v3 2/5] arm: dts: mt7623: add mt7530 switch to mt7623a.dtsi arinc9.unal
2023-02-10 18:25 ` [PATCH v3 3/5] arm: dts: mt7623: change mt7530 switch address arinc9.unal
2023-02-10 18:25 ` [PATCH v3 4/5] arm: dts: mt7623: enable flow control on port@6 arinc9.unal
2023-02-10 18:25 ` [PATCH v3 5/5] arm: dts: mt7623: add port@5 as CPU port arinc9.unal
2023-02-18 7:00 ` [PATCH v3 0/5] arm: dts: mt7623: relocate gmacs, mt7530 switch, and add port@5 Arınç ÜNAL
2023-02-18 10:24 ` Aw: " Frank Wunderlich
2023-02-18 10:49 ` Arınç ÜNAL
2023-02-18 12:18 ` Aw: " Frank Wunderlich
2023-02-18 17:02 ` Arınç ÜNAL
2023-02-18 19:11 ` Frank Wunderlich
2023-02-18 19:34 ` Arınç ÜNAL
2023-02-19 13:52 ` Aw: " Frank Wunderlich
2023-04-12 12:49 ` Frank Wunderlich
2023-04-12 14:31 ` Arınç ÜNAL
2023-04-12 15:11 ` Frank Wunderlich [this message]
2023-04-12 16:21 ` Aw: " Arınç ÜNAL
2023-04-12 16:53 ` Aw: " Frank Wunderlich
2023-04-12 17:06 ` Arınç ÜNAL
2023-05-29 13:40 ` Matthias Brugger
2023-06-03 10:48 ` Arınç ÜNAL
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-489cdc3b-e861-49d0-b1ec-e964f00388df-1681312277092@3c-app-gmx-bap50 \
--to=frank-w@public-files.de \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=erkin.bozoglu@xeront.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).