be2net: Fix Lancer error recovery to distinguish FW download
authorSomnath Kotur <somnath.kotur@emulex.com>
Thu, 5 Dec 2013 06:37:55 +0000 (12:07 +0530)
committerDavid S. Miller <davem@davemloft.net>
Fri, 6 Dec 2013 20:03:40 +0000 (15:03 -0500)
commit4bebb56a6d50ca50a34048194877dca34f572f8f
treed2a8e95cfa4af553885b57ca1c819fcb31ad1bbe
parentd0b7da8afa079ffe018ab3e92879b7138977fc8f
be2net: Fix Lancer error recovery to distinguish FW download

The Firmware update would be detected by looking at the sliport_error1/
sliport_error2 register values(0x02/0x00). If its not a FW reset the current
messaging would take place. If the error is due to FW reset, log a message to
user that "Firmware update in progress" and also do not log sliport_status and
sliport_error register values.

Signed-off-by: Kalesh AP <kalesh.purayil@emulex.com>
Signed-off-by: Somnath Kotur <somnath.kotur@emulex.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/net/ethernet/emulex/benet/be_hw.h
drivers/net/ethernet/emulex/benet/be_main.c