[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-dab715b9-3953-40da-bc25-c4c2a5e9b7c3-1676715866453@3c-app-gmx-bap53>
Date: Sat, 18 Feb 2023 11:24:26 +0100
From: Frank Wunderlich <frank-w@...lic-files.de>
To: Arınç ÜNAL <arinc.unal@...nc9.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, erkin.bozoglu@...ont.com
Subject: Aw: Re: [PATCH v3 0/5] arm: dts: mt7623: relocate gmacs, mt7530
switch, and add port@5
Hi,
finally get some time to bootup with this series on my r2.
I see that inserting the port@5 as cpu-port maps this as default-cpu because dsa-core uses first found cpu-port as
default (dsa_tree_setup_cpu_ports in dsa.c) and because of lower bandwidth (rgmii instead of trgmii) not the best choice.
But it look worse...network is currently broken (set both gmacs up).
I see arp-packets reaching remote side, but reponse is not received by r2
I have tested it on 6.2-rc8 (wan-port), maybe additional patches are needed?...userspace setup should be right.
so i added series on top of net-next (no additional patches except some basic like build-script,defconfig and such)...same result...
i'm not sure if i change the mapping from userspace back to eth0, so disabled port@5 in switch, now port6 is
cpu-port again and it works...so something is wrong with port5 of switch or gmac1.
regards Frank
Powered by blists - more mailing lists