From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Daniel Golle <daniel@makrotopia.org>
Cc: "Nicolò Veronese" <nicveronese@gmail.com>,
netdev@vger.kernel.org, simonebortolin@hack-gpon.org,
nanomad@hack-gpon.org, "Federico Cappon" <dududede371@gmail.com>,
lorenzo@kernel.org, ftp21@ftp21.eu, pierto88@hack-gpon.org,
hitech95@hack-gpon.org, davem@davemloft.net, andrew@lunn.ch,
edumazet@google.com, hkallweit1@gmail.com, kuba@kernel.org,
pabeni@redhat.com, nbd@nbd.name
Subject: Re: [RFC] RJ45 to SFP auto-sensing and switching in mux-ed single-mac devices (XOR RJ/SFP)
Date: Tue, 29 Aug 2023 19:04:13 +0100 [thread overview]
Message-ID: <ZO4zHdeeMFGqCx3d@shell.armlinux.org.uk> (raw)
In-Reply-To: <ZO4sw2gOQjn1GXDg@makrotopia.org>
On Tue, Aug 29, 2023 at 06:37:07PM +0100, Daniel Golle wrote:
> Another thing which came to my mind is the existing port field in
> many ethtool ops which could be either PORT_TP or PORT_FIBRE to
> destinguish the TP PHY from the SFP at least for xLINKSETTINGS.
However, PORT_TP also gets used for RJ45 SFPs, so that doesn't
distinguish between a built-in PHY and a SFP PHY.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2023-08-29 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 15:12 [RFC] RJ45 to SFP auto-sensing and switching in mux-ed single-mac devices (XOR RJ/SFP) Nicolò Veronese
2023-08-29 15:38 ` Russell King (Oracle)
2023-08-29 17:37 ` Daniel Golle
2023-08-29 18:04 ` Russell King (Oracle) [this message]
2023-08-31 1:04 ` Jakub Kicinski
2023-09-03 22:51 ` Andrew Lunn
2023-09-04 6:06 ` Maxime Chevallier
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=ZO4zHdeeMFGqCx3d@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dududede371@gmail.com \
--cc=edumazet@google.com \
--cc=ftp21@ftp21.eu \
--cc=hitech95@hack-gpon.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=nanomad@hack-gpon.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=nicveronese@gmail.com \
--cc=pabeni@redhat.com \
--cc=pierto88@hack-gpon.org \
--cc=simonebortolin@hack-gpon.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).