From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Klaus Kudielka" <klaus.kudielka@gmail.com>,
netdev@vger.kernel.org, "Heiner Kallweit" <hkallweit1@gmail.com>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Tomas Hlavacek" <tmshlvck@gmail.com>
Subject: Re: [RFC] phylink: support for devices with MAC sharing SFP cage & PHY (e.g. Turris Omnia)
Date: Fri, 4 Jan 2019 09:45:44 +0000 [thread overview]
Message-ID: <20190104094544.GM26090@n2100.armlinux.org.uk> (raw)
In-Reply-To: <3c9d3f80-f42e-fd6d-693f-cd190b444398@gmail.com>
On Sun, Dec 30, 2018 at 02:35:32PM -0800, Florian Fainelli wrote:
> There are at least two user space configuration knobs that we could
> extend to support dynamically switching between copper and fiber interface:
>
> ethtool -s <iface> port tp|mii|fiber..
How does that work if you have a SFP plugged in that gives you a RJ45
socket (and hence shows "IP" in the ethtool output) ?
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-01-04 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 8:25 [RFC] phylink: support for devices with MAC sharing SFP cage & PHY (e.g. Turris Omnia) Klaus Kudielka
2018-12-30 9:51 ` Andrew Lunn
2018-12-30 22:35 ` Florian Fainelli
2018-12-30 22:41 ` Andrew Lunn
2019-01-04 9:45 ` Russell King - ARM Linux [this message]
2018-12-31 11:24 ` Klaus Kudielka
2018-12-31 17:43 ` Andrew Lunn
2019-01-04 6:26 ` Klaus Kudielka
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=20190104094544.GM26090@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=klaus.kudielka@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tmshlvck@gmail.com \
--cc=uwe@kleine-koenig.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).