1. 30 8月, 2009 9 次提交
  2. 27 8月, 2009 6 次提交
  3. 21 4月, 2009 4 次提交
  4. 27 2月, 2009 3 次提交
  5. 20 1月, 2009 1 次提交
    • M
      tg3: Fix firmware loading · 9e9fd12d
      Matt Carlson 提交于
      This patch modifies how the tg3 driver handles device firmware.
      
      The patch starts by consolidating David Woodhouse's earlier patch under
      the same name.  Specifically, the patch moves the request_firmware call
      into a separate tg3_request_firmware() function and calls that function
      from tg3_open() rather than tg3_init_one().
      
      The patch then goes on to limit the number of devices that will make
      request_firmware calls.  The original firmware patch unnecessarily
      requested TSO firmware for devices that did not need it.  This patch
      reduces the set of devices making TSO firmware patches to approximately
      the following device set : 5703, 5704, and 5705.
      
      Finally, the patch reduces the effects of a request_firmware() failure.
      For those devices that are requesting TSO firmware, the driver will turn
      off the TSO capability.  If TSO firmware becomes available at a later
      time, the device can be closed and then opened again to reacquire the
      TSO capability.
      Signed-off-by: NMatt Carlson <mcarlson@broadcom.com>
      Signed-off-by: NMichael Chan <mchan@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      9e9fd12d
  6. 05 1月, 2009 1 次提交
  7. 22 12月, 2008 3 次提交
  8. 16 12月, 2008 1 次提交
  9. 22 11月, 2008 4 次提交
  10. 04 11月, 2008 5 次提交
  11. 09 10月, 2008 1 次提交
  12. 11 9月, 2008 1 次提交
  13. 16 8月, 2008 1 次提交
    • M
      tg3: Fix firmware event timeouts · 4ba526ce
      Matt Carlson 提交于
      The git commit 7c5026aa ("tg3: Add
      link state reporting to UMP firmware") introduced code that waits for
      previous firmware events to be serviced before attempting to submit a
      new event.  Unfortunately that patch contained a bug that cause the
      driver to wait 2.5 seconds, rather than 2.5 milliseconds as intended.
      This patch fixes that bug.
      
      This bug revealed that not all firmware versions service driver events
      though.  Since we do not know which versions of the firmware do and don't
      service these events, the driver needs some way to minimize the effects
      of the delay.  This patch solves the problem by recording a jiffies
      timestamp when it submits an event to the hardware.  If the jiffies
      counter shows that 2.5 milliseconds have already passed, a wait is not
      needed and the driver can proceed to submit a new event.
      Signed-off-by: NMatt Carlson <mcarlson@broadcom.com>
      Signed-off-by: NMichael Chan <mchan@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4ba526ce