From: Stephen Hemminger <stephen@networkplumber.org>
To: Ivan Malov <ivan.malov@arknetworks.am>
Cc: dev@dpdk.org, Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Andy Moreton <andy.moreton@amd.com>,
Pieter Jansen Van Vuuren <pieter.jansen-van-vuuren@amd.com>,
Viacheslav Galaktionov <viacheslav.galaktionov@arknetworks.am>,
stable@dpdk.org
Subject: Re: [PATCH 1/1] common/sfc_efx/base: revise legacy port controls on Medford4
Date: Wed, 13 Aug 2025 08:20:40 -0700 [thread overview]
Message-ID: <20250813082041.3edfc0fa@hermes.local> (raw)
In-Reply-To: <20250813123636.16363-1-ivan.malov@arknetworks.am>
On Wed, 13 Aug 2025 16:36:36 +0400
Ivan Malov <ivan.malov@arknetworks.am> wrote:
> Theoretically, adaptor firmware may not support new netport API. Currently,
> efx_np_supported() assumes Medford4 always supports the API, however, this
> can be improved in the future by checking some capability bit during probe.
>
> If efx_np_supported() returns B_FALSE, then one should not invoke Medford4
> PHY and MAC methods that are inherently dependent on new netport API. Pick
> EF10-generic PHY and MAC methods in this case to maintain legacy behaviour.
>
> Fixes: 8dac31d073af ("common/sfc_efx/base: introduce Medford4 stub for MAC methods")
> Fixes: d65a7129c413 ("common/sfc_efx/base: introduce Medford4 stub for PHY methods")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ivan Malov <ivan.malov@arknetworks.am>
> Reviewed-by: Andy Moreton <andy.moreton@amd.com>
> ---
Applied to next-net
prev parent reply other threads:[~2025-08-13 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 12:36 [PATCH 1/1] common/sfc_efx/base: revise legacy port controls on Medford4 Ivan Malov
2025-08-13 15:20 ` Stephen Hemminger [this message]
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=20250813082041.3edfc0fa@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=andy.moreton@amd.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@arknetworks.am \
--cc=pieter.jansen-van-vuuren@amd.com \
--cc=stable@dpdk.org \
--cc=viacheslav.galaktionov@arknetworks.am \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.