Lines Matching full:firmware
15 - `Acquiring Firmware`_
28 Acquiring Firmware
31 The NFP3800, NFP4000 and NFP6000 devices require application specific firmware
32 to function. Application firmware can be located either on the host file system
33 or in the device flash (if supported by management firmware).
35 Firmware files on the host filesystem contain card type (`AMDA-*` string), media
36 config etc. They should be placed in `/lib/firmware/netronome` directory to
37 load firmware from the host file system.
39 Firmware for basic NIC operation is available in the upstream
40 `linux-firmware.git` repository.
42 A more comprehensive list of firmware can be downloaded from the
45 Firmware in NVRAM
48 Recent versions of management firmware supports loading application
49 firmware from flash when the host driver gets probed. The firmware loading
52 Devlink or ethtool can be used to update the application firmware on the device
54 command. Users need to take care to write the correct firmware image for the
63 firmware images targeting different applications.
65 When using application firmware from host, we recommend placing
66 actual firmware files in application-named subdirectories in
67 `/lib/firmware/netronome` and linking the desired files, e.g.::
69 $ tree /lib/firmware/netronome/
70 /lib/firmware/netronome/
88 After changing firmware files you may need to regenerate the initramfs
89 image. Initramfs contains drivers and firmware files your system may
92 is system loading wrong driver or firmware on boot, but when driver is
95 Selecting firmware per device
98 Most commonly all cards on the system use the same type of firmware.
99 If you want to load a specific firmware image for a specific card, you
103 nfp: Looking for firmware file in order of priority:
109 or *pci-0000:02:00.0.nffw* is present in `/lib/firmware/netronome` this
110 firmware file will take precedence over `nic_AMDA*` files.
116 Running firmware version
119 The version of the loaded firmware for a particular <netdev> interface,
125 Firmware loading policy
128 Firmware loading policy is controlled via three HWinfo parameters
132 Defines which firmware should take precedence, 'Disk' (0), 'Flash' (1) or
133 the 'Preferred' (2) firmware. When 'Preferred' is selected, the management
134 firmware makes the decision over which firmware will be loaded by comparing
135 versions of the flash firmware and the host supplied firmware.
140 Defines if the driver should reset the firmware when
141 the driver is probed, either 'Disk' (0) if firmware was found on disk,
143 reset on driver unload if firmware was loaded when the driver was probed.
154 The devlink info command displays the running and stored firmware versions
183 This section explains how to use Agilio SmartNICs running basic NIC firmware.