From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Inochi Amaoto <inochiama@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chen Wang <unicorn_wang@outlook.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Richard Cochran <richardcochran@gmail.com>,
Yixun Lan <dlan@gentoo.org>,
Thomas Bonnefille <thomas.bonnefille@bootlin.com>,
Ze Huang <huangze@whut.edu.cn>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
sophgo@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
Longbin Li <looong.bin@gmail.com>
Subject: Re: [PATCH net-next RFC 0/3] riscv: dts: sophgo: Add ethernet support for cv18xx
Date: Sun, 15 Jun 2025 00:34:24 +0200 [thread overview]
Message-ID: <55df35f66eeb8580b21337e4b2738801117c125a.camel@gmail.com> (raw)
In-Reply-To: <05194937-8db3-4d90-9d03-9836c734fce1@lunn.ch>
Sorry for confusion Andrew,
On Sun, 2025-06-15 at 00:20 +0200, Andrew Lunn wrote:
> > Also ethtool seems to be incompatible with mdio muxes :(
>
> Please could you expand on that, because i don't know of a problem
> with mdio muxes and ethtool.
everything seems to be fine with ethtool and mdio mux!
(I accidentally mixed up host and target consoles)
# ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: external
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x0000003f (63)
drv probe link timer ifdown ifup
Link detected: yes
But we do have some troubles with the internal PHY with Inochi's patches
on SG2000, the above "Link detected: yes" is actually without cable
inserted.
--
Alexander Sverdlin.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-06-14 22:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 8:07 [PATCH net-next RFC 0/3] riscv: dts: sophgo: Add ethernet support for cv18xx Inochi Amaoto
2025-06-11 8:07 ` [PATCH net-next RFC 1/3] dt-bindings: net: Add support for Sophgo CV1800 dwmac Inochi Amaoto
2025-06-12 16:08 ` Conor Dooley
2025-06-11 8:07 ` [PATCH net-next RFC 2/3] riscv: dts: sophgo: Add ethernet device for cv18xx Inochi Amaoto
2025-06-11 8:07 ` [PATCH net-next RFC 3/3] riscv: dts: sophgo: Add mdio multiplexer " Inochi Amaoto
2025-06-11 10:12 ` [PATCH net-next RFC 0/3] riscv: dts: sophgo: Add ethernet support " Chen Wang
2025-06-11 10:18 ` Inochi Amaoto
2025-06-14 21:01 ` Alexander Sverdlin
2025-06-14 21:52 ` Alexander Sverdlin
2025-06-14 22:20 ` Andrew Lunn
2025-06-14 22:34 ` Alexander Sverdlin [this message]
2025-06-15 1:53 ` Inochi Amaoto
2025-06-14 21:19 ` Alexander Sverdlin
2025-06-16 0:55 ` Inochi Amaoto
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=55df35f66eeb8580b21337e4b2738801117c125a.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=alex@ghiti.fr \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=edumazet@google.com \
--cc=huangze@whut.edu.cn \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=looong.bin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=thomas.bonnefille@bootlin.com \
--cc=unicorn_wang@outlook.com \
/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