[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM5PR1301MB2172EA32966B95D195FC0B5AE7759@DM5PR1301MB2172.namprd13.prod.outlook.com>
Date: Fri, 26 Aug 2022 00:54:10 +0000
From: Baowen Zheng <baowen.zheng@...igine.com>
To: Jakub Kicinski <kuba@...nel.org>,
Simon Horman <simon.horman@...igine.com>
CC: David Miller <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
oss-drivers <oss-drivers@...igine.com>
Subject: RE: [PATCH net-next 3/3] nfp: add support for eeprom get and set
command
On August 26, 2022 5:49 AM, Jakub wrote:
>On Thu, 25 Aug 2022 16:12:23 +0200 Simon Horman wrote:
>> From: Baowen Zheng <baowen.zheng@...igine.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?
Hi Jakub, actually it is a general way to persist MAC change during driver reload or system reboot. AFAIK, the 82599E series NIC of Intel supports this way to change MAC.
The difference is the offset of MAC in EEPROM to store the MAC, it is defined by vendor.
Powered by blists - more mailing lists