linux.git/drivers/net/ethernet/broadcom, branch v3.2-rc2

tg3: Update version to 3.121

2011-11-04T21:31:49+00:00

This patch updates the tg3 version to 3.121.

Signed-off-by: Matt Carlson 
Reviewed-by: Michael Chan 
Signed-off-by: David S. Miller

tg3: Eliminate timer race with reset_task

2011-11-04T21:31:48+00:00

During shutdown, it is impossible to reliably disable the timer and
reset_task threads.  Each thread can schedule the other, which leads to
shutdown code that chases its tail.

To fix the problem, this patch removes the ability of tg3_reset_task to
schedule a new timer thread.  To support this change, tg3_timer no
longer terminates itself, but rather goes into a polling mode.

Signed-off-by: Matt Carlson 
Reviewed-by: Michael Chan 
Signed-off-by: David S. Miller

tg3: Schedule at most one tg3_reset_task run

2011-11-04T21:31:48+00:00

It is possible for multiple threads in the tg3 driver to each attempt to
schedule a run of tg3_reset_task().  The multiple tg3_reset_task
executions could all wind up on the same queue (and execute serially) or
wind up on the queues of another processor (which could execute in
parallel).  Either scenario is not what was truly desired.

This patch adds a new flag, TG3_FLAG_RESET_TASK_PENDING, and uses it to
determine whether or not to schedule another run of tg3_reset_task().
With the new flag comes two new functions to facilitate scheduling and
descheduling of tg3_reset_task().

Signed-off-by: Matt Carlson 
Reviewed-by: Michael Chan 
Signed-off-by: David S. Miller

tg3: Obtain PCI function number from device

2011-11-04T21:31:48+00:00

This patch adds code to attempt to obtain the PCI function number from
the device rather than accept the number handed by the kernel.  In
pass-through scenarios, the function number handed by the kernel may not
reflect the true function of the device.

Signed-off-by: Matt Carlson 
Reviewed-by: Michael Chan 
Signed-off-by: David S. Miller

tg3: Fix irq alloc error cleanup path

2011-11-04T21:31:47+00:00

This patch fixes a bug where the irq error cleanup path did not free all
the resources it allocated.

Signed-off-by: Matt Carlson 
Signed-off-by: Ben Li 
Signed-off-by: Akinobu Mita 
Reviewed-by: Michael Chan 
Signed-off-by: David S. Miller

tg3: Fix 4k skb error recovery path

2011-11-04T21:31:47+00:00

On the error recovery resource unwind path, it is possible for the
driver to attempt to unmap a fragment that hadn't been mapped.  This
patch fixes the problem by correcting the "last" parameter supplied.

Signed-off-by: Matt Carlson 
Reviewed-by: Michael Chan 
Signed-off-by: David S. Miller

tg3: Fix 4k tx bd segmentation code

2011-11-04T21:31:47+00:00

The new 4k tx bd segmentation code had a bug in the error cleanup path.
If the driver did not map all the physical fragments, the abort path
would wind up advancing the producer index beyond the point where the
setup code stopped.  This would ultimately turn into a tx recovery error
where the driver would expect the skb pointer to be set when it isn't.
This patch fixes the problem, and then makes the code a little easier to
understand.

Signed-off-by: Matt Carlson 
Reviewed-by: Michael Chan 
Signed-off-by: David S. Miller

tg3: Fix APE mutex init and use

2011-11-04T21:31:46+00:00

APE mutex register blocks are shared by all ports of multiport devices.
For some mutexing purposes, each function is assigned their own
register.  For other cases, each function is assigned its own request
and grant bits of a single register.  For the latter cases, the tg3
driver is incorrectly allowing each function to use the same set of
grant / request bits.  This patch fixes the code so that each function
uses the appropriate bitset.

Signed-off-by: Matt Carlson 
Signed-off-by: Michael Chan 
Signed-off-by: David S. Miller

bnx2x: update driver version to 1.70.30-0

2011-10-27T20:14:17+00:00

Signed-off-by: Dmitry Kravkov 
Signed-off-by: Eilon Greenstein 
Signed-off-by: David S. Miller

bnx2x: use FW 7.0.29.0

2011-10-27T20:14:16+00:00

The FW includes the following fixes:
  1. (iSCSI) Arrival of un-solicited ASYNC message causes
     firmware to abort the connection with RST.
  2. (FCoE) There is a probability that truncated FCoE packet on
     RX path won't get detected which might lead to FW assert.
  3. (iSCSI) Arrival of target-initiated NOP-IN during intense
     ISCSI traffic might lead to FW assert.
  4. (iSCSI) Chip hangs when in case of retransmission not aligned
     to 4-bytes from the beginning of iSCSI PDU.
  5. (FCoE) Arrival of packets beyond task IO size can lead to crash.

Signed-off-by: Dmitry Kravkov 
Signed-off-by: Eilon Greenstein 
Signed-off-by: David S. Miller