[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACKFLinzVbqyXFMURZzs-d5HYCsxoo9V+PkhvL-ncBKm7wJSCw@mail.gmail.com>
Date: Tue, 6 Sep 2022 20:44:48 -0700
From: Michael Chan <michael.chan@...adcom.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Jacob Keller <jacob.e.keller@...el.com>,
Gal Pressman <gal@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Simon Horman <horms@...ge.net.au>,
Andy Gospodarek <andy@...yhouse.net>
Subject: Re: [PATCH net-next 0/2] ice: support FEC automatic disable
On Tue, Aug 30, 2022 at 2:45 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Tue, 30 Aug 2022 13:09:20 -0700 Jacob Keller wrote:
> > I have no way to verify whether other vendors actually follow this or
> > not, as it essentially requires checking with modules that wouldn't link
> > otherwise and likely requires a lot of trial and error.
>
> Getting some input from Broadcom or Netronome would be useful, yes :(
Sorry for the late comment. I needed to consult with the firmware
engineer first. The bnxt driver does not support auto FEC if
auto-negotiation is disabled. But firmware has a "media detect"
fallback mode if auto-negotiation fails to link up. It is similar to
the parallel detect mode but done in firmware. I think this fallback
mode may be relevant to the discussion here. In this fallback mode,
firmware will cycle through all the supported speeds and supported FEC
combinations (including no FEC) and try to link up.
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4209 bytes)
Powered by blists - more mailing lists