diff options
| author | David S. Miller <davem@davemloft.net> | 2017-07-27 17:26:26 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-07-27 17:26:26 -0700 |
| commit | 122323f798120a53c3ef90da4fadd9a458e10c21 (patch) | |
| tree | 3d4171f978507af2e36ce56035d54ef9134579ce /drivers/net/phy | |
| parent | 53d56f79a0b2e4bc5bbc04988e5bfde768db604f (diff) | |
| parent | 1680a3705b00e90c1e1de91a9fec421b23cef719 (diff) | |
Merge branch 'nfp-extend-firmware-request-logic'
Jakub Kicinski says:
====================
nfp: extend firmware request logic
We have been pondering for some time how to support loading different
application firmwares onto NFP. We want to support both users selecting
one of the firmware images provided by Netronome (which are optimized
for different use cases each) as well as firmware images created by
users themselves or other companies.
In the end we decided to go with the simplest solution - depending on
the right firmware image being placed in /lib/firmware. This vastly
simplifies driver logic and also doesn't require any new API.
Different NICs on one system may want to run different applications
therefore we first try to load firmware specific to the device (by
serial number of PCI slot) and if not present try the device model
based name we have been using so far.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/phy')
0 files changed, 0 insertions, 0 deletions