netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <simon.horman@corigine.com>
Cc: David Miller <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: Re: [PATCH net-next 3/3] nfp: add support for eeprom get and set command
Date: Thu, 25 Aug 2022 14:49:20 -0700	[thread overview]
Message-ID: <20220825144920.5c709331@kernel.org> (raw)
In-Reply-To: <20220825141223.22346-4-simon.horman@corigine.com>

On Thu, 25 Aug 2022 16:12:23 +0200 Simon Horman wrote:
> From: Baowen Zheng <baowen.zheng@corigine.com>
> 
> Add support for eeprom get and set operation with ethtool command.
> with this change, we can support commands as:
> 
>  #ethtool -e enp101s0np0 offset 0 length 6
>  Offset          Values
>  ------          ------
>  0x0000:         00 15 4d 16 66 33
> 
>  #ethtool -E enp101s0np0 magic 0x400019ee offset 5 length 1 value 0x88
> 
> We make this change to persist MAC change during driver reload and system
> reboot.

Is there any precedent for writing the MAC address with way?

  reply	other threads:[~2022-08-25 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 14:12 [PATCH net-next 0/3] nfp: port speed and eeprom get/set updates Simon Horman
2022-08-25 14:12 ` [PATCH net-next 1/3] nfp: propagate port speed from management firmware Simon Horman
2022-08-25 14:12 ` [PATCH net-next 2/3] nfp: check if application firmware is indifferent to port speed Simon Horman
2022-08-25 14:12 ` [PATCH net-next 3/3] nfp: add support for eeprom get and set command Simon Horman
2022-08-25 21:49   ` Jakub Kicinski [this message]
2022-08-26  0:54     ` Baowen Zheng
2022-08-30  9:50 ` [PATCH net-next 0/3] nfp: port speed and eeprom get/set updates patchwork-bot+netdevbpf

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=20220825144920.5c709331@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.com \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.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).