diff options
| author | Vasundhara Volam <vasundhara.volam@emulex.com> | 2015-02-06 08:18:39 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2015-02-07 22:50:58 -0800 |
| commit | 70a7b5257018c518007c7212977bab6ccacd9468 (patch) | |
| tree | dd2d2df029bbba6d5bfe7abb533cca3f2be074aa /virt | |
| parent | 81a9e226ff2c5cf963a79c1cbecd6e68c0e35a21 (diff) | |
be2net: use offset based FW flashing for Skyhawk chip
While sending FW update cmds to the FW, the driver specifies the "type"
of each component that needs to be flashed. The FW then picks the offset
in the flash area at which the componnet is to be flashed. This doesn't work
when new components that the current FW doesn't recognize, need to be
flashed. Recent FWs (10.2 and above) support a scheme of FW-update wherein
the "offset" of the component in the flash area can be specified instead
of the "type". This patch uses the "offset" based FW-update mechanism and
only when it fails, it fallsback to the old "type" based update.
Signed-off-by: Vasundhara Volam <vasundhara.volam@emulex.com>
Signed-off-by: Sathya Perla <sathya.perla@emulex.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions