From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Sean Anderson <sean.anderson@seco.com>
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Antoine Tenart <atenart@kernel.org>
Subject: Re: [PATCH v4] net: macb: Fix several edge cases in validate
Date: Tue, 26 Oct 2021 18:46:52 +0100 [thread overview]
Message-ID: <YXg/DP2d1UM831+c@shell.armlinux.org.uk> (raw)
In-Reply-To: <61d9f92e-78d8-5d14-50d1-1ed886ec0e17@seco.com>
On Tue, Oct 26, 2021 at 01:28:15PM -0400, Sean Anderson wrote:
> Actually, according to the Zynq UltraScale+ Devices Register Reference
> [1], the PCS does not support 10/100. So should SGMII even fall through
> here?
>
> [1] https://www.xilinx.com/html_docs/registers/ug1087/gem___pcs_control.html
Hmm. That brings with it fundamental question: if the PCS supports 1G
only, does it _actually_ support Cisco SGMII, or does it only support
1000base-X?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-10-26 17:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 17:24 [PATCH v4] net: macb: Fix several edge cases in validate Sean Anderson
2021-10-25 21:19 ` Russell King (Oracle)
2021-10-25 21:35 ` Sean Anderson
2021-10-26 16:37 ` Nicolas Ferre
2021-10-26 17:04 ` Russell King (Oracle)
2021-10-26 17:28 ` Sean Anderson
2021-10-26 17:46 ` Russell King (Oracle) [this message]
2021-10-26 17:49 ` Sean Anderson
2021-10-26 18:28 ` Russell King (Oracle)
2021-10-26 18:52 ` Sean Anderson
2021-10-27 7:02 ` Nicolas.Ferre
2021-10-26 0:44 ` Jakub Kicinski
2021-10-26 15:30 ` Sean Anderson
2021-10-26 15:39 ` Jakub Kicinski
2021-10-26 16:32 ` Nicolas Ferre
2021-10-26 15:51 ` Russell King (Oracle)
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=YXg/DP2d1UM831+c@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=atenart@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=sean.anderson@seco.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;
as well as URLs for NNTP newsgroup(s).