netdev - Re: Aw: Re: [PATCH net-next v4 11/11] net: dsa: realtek: rtl8365mb: multiple cpu ports, non cpu extint

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87r19e5e8w.fsf@bang-olufsen.dk>
Date:   Tue, 11 Jan 2022 18:17:03 +0000
From:   Alvin Šipraga <ALSI@...g-olufsen.dk>
To:     Frank Wunderlich <frank-w@...lic-files.de>
CC:     Luiz Angelo Daros de Luca <luizluca@...il.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linus.walleij@...aro.org" <linus.walleij@...aro.org>,
        "andrew@...n.ch" <andrew@...n.ch>,
        "vivien.didelot@...il.com" <vivien.didelot@...il.com>,
        "f.fainelli@...il.com" <f.fainelli@...il.com>,
        "olteanv@...il.com" <olteanv@...il.com>,
        "arinc.unal@...nc9.com" <arinc.unal@...nc9.com>
Subject: Re: Aw: Re: [PATCH net-next v4 11/11] net: dsa: realtek: rtl8365mb:
 multiple cpu ports, non cpu extint

Frank Wunderlich <frank-w@...lic-files.de> writes:

> Hi,
>
> i have 2 devices here i currently try this series.
>
> 1x Bananapi R64 v0.1 (mt7622 SOC) with rtl8367s (sgmii+rgmii) - configured to use extport 2 in rgmii mode
> 1x Bananapi R2 Pro v0 (rk3568 SOC) with rtl8367RB (rgmii+rgmii) - configured to use extport 1 in rgmii mode
>
> on both devices i get mdio running after additional reset in probe and ports are
> recognizing link up (got the real port-reg-mapping)
>
> on r64 i get pings working but tcp (ssh, http) seems not working.
> on r2pro i cannot get even ping working (but rk3568 gmac seems to come
> up).

Luiz, any comments regarding this? I suppose if the chip ID/revision is
the same for both 67S and 67RB, they should work pretty much the same,
right?

>
> but i'm not deep enough in driver coding to find out whats wrong not having technical documents for checking registers to values needed.

Ping working but TCP not working is a bit strange. You could check the
output of ethtool -S and see if that meets your expectations. If you
have a relatively modern ethtool you can also append --all-groups to the
comment to get a more standard output.

You can also try adjusting the RGMII TX/RX delay and pause settings -
that might help for the R2 where you aren't getting any packets
through.