[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DS0PR11MB77853E17402518C2B56AF240F0FF2@DS0PR11MB7785.namprd11.prod.outlook.com>
Date: Thu, 13 Feb 2025 10:35:51 +0000
From: "Jagielski, Jedrzej" <jedrzej.jagielski@...el.com>
To: Jiri Pirko <jiri@...nulli.us>
CC: "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "horms@...nel.org" <horms@...nel.org>, "Polchlopek,
Mateusz" <mateusz.polchlopek@...el.com>
Subject: RE: [PATCH iwl-next v3 03/14] ixgbe: add handler for devlink
.info_get()
From: Jiri Pirko <jiri@...nulli.us>
Sent: Wednesday, February 12, 2025 4:05 PM
>Wed, Feb 12, 2025 at 02:14:02PM +0100, jedrzej.jagielski@...el.com wrote:
>>Provide devlink .info_get() callback implementation to allow the
>>driver to report detailed version information. The following info
>>is reported:
>>
>> "serial_number" -> The PCI DSN of the adapter
>> "fw.bundle_id" -> Unique identifier for the combined flash image
>> "fw.undi" -> Version of the Option ROM containing the UEFI driver
>> "board.id" -> The PBA ID string
>
>Do you have some board.serial_number by any chance? This could be handy
>in some cases, for example if you have a board with multiple nic asics.
Unfortunately i cannot spot nothing more for identification than
the PCI DSN number.
Powered by blists - more mailing lists