On Sun, 2 Aug 2020 13:08:28 +0300 Igor Russkikh wrote: > Here we return existing fw & mfw versions, we also fetch device's > serial number: > > ~$ sudo ~/iproute2/devlink/devlink dev info > pci/0000:01:00.0: > driver qed > serial_number REE1915E44552
Just to confirm - this is not: * - ``board.serial_number`` - Board serial number of the device. This is usually the serial number of the board, often available in PCI *Vital Product Data*. > versions: > running: > fw 8.42.2.0 > stored: > fw.mgmt 8.52.10.0 > pci/0000:01:00.1: > driver qed > serial_number REE1915E44552 > versions: > running: > fw 8.42.2.0 > stored: > fw.mgmt 8.52.10.0 > > MFW and FW are different firmwares on device. > Management is a firmware responsible for link configuration and > various control plane features. Its permanent and resides in NVM. > > Running FW (or fastpath FW) is an embedded microprogram implementing > all the packet processing, offloads, etc. This FW is being loaded > on each start by the driver from FW binary blob. Sounds like you should use: fw.app - Data path microcode controlling high-speed packet processing. Rather than: fw - Overall firmware version, often representing the collection of fw.mgmt, fw.app, etc. All quotes from devlink-info.rst in the kernel sources.