From: Michal Kubecek <mkubecek@suse.cz>
To: netdev@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>, linville@redhat.com
Subject: Re: [PATCH v2 2/2] ethtool: Add 100BaseT1 and 1000BaseT1 link modes
Date: Fri, 31 May 2019 17:50:07 +0200 [thread overview]
Message-ID: <20190531155007.GF15954@unicorn.suse.cz> (raw)
In-Reply-To: <20190531135748.23740-3-andrew@lunn.ch>
On Fri, May 31, 2019 at 03:57:48PM +0200, Andrew Lunn wrote:
> The kernel can now indicate if the PHY supports operating over a
> single pair at 100Mbps or 1000Mbps.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
Reviewed-by: Michal Kubecek <mkubecek@suse.cz>
> ethtool.8.in | 2 ++
> ethtool.c | 6 ++++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/ethtool.8.in b/ethtool.8.in
> index 430d11b915af..6af63455c636 100644
> --- a/ethtool.8.in
> +++ b/ethtool.8.in
> @@ -639,8 +639,10 @@ lB l lB.
> 0x002 10baseT Full
> 0x004 100baseT Half
> 0x008 100baseT Full
> +0x80000000000000000 100baseT1 Full
> 0x010 1000baseT Half (not supported by IEEE standards)
> 0x020 1000baseT Full
> +0x100000000000000000 1000baseT1 Full
> 0x20000 1000baseKX Full
> 0x20000000000 1000baseX Full
> 0x800000000000 2500baseT Full
This reminds me the earlier discussion about which syntax extension
would be more useful:
ethtool -s <dev> advertise 100baseT1/Full 1000baseT1/Full
(listing modes to be advertised) or
ethtool -s <dev> advertise 100baseT1/Full off 1000baseT1/Full on
(enabling/disabling selected modes). But maybe we could support both;
after all, it's unlikely there would ever be a link mode named "on" or
"off".
Michal
next prev parent reply other threads:[~2019-05-31 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 13:57 [PATCH v2 0/2] Add 100BaseT1 and 1000BaseT1 Andrew Lunn
2019-05-31 13:57 ` [PATCH v2 1/2] ethtool: sync ethtool-copy.h with linux-next from 30/05/2019 Andrew Lunn
2019-05-31 15:53 ` Michal Kubecek
2019-05-31 16:04 ` Andrew Lunn
2019-05-31 13:57 ` [PATCH v2 2/2] ethtool: Add 100BaseT1 and 1000BaseT1 link modes Andrew Lunn
2019-05-31 15:50 ` Michal Kubecek [this message]
2019-06-14 18:40 ` [PATCH v2 0/2] Add 100BaseT1 and 1000BaseT1 John W. Linville
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=20190531155007.GF15954@unicorn.suse.cz \
--to=mkubecek@suse.cz \
--cc=andrew@lunn.ch \
--cc=linville@redhat.com \
--cc=netdev@vger.kernel.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).