1. 24 2月, 2012 1 次提交
  2. 23 2月, 2012 1 次提交
  3. 16 2月, 2012 7 次提交
  4. 14 2月, 2012 3 次提交
  5. 27 1月, 2012 11 次提交
  6. 10 1月, 2012 3 次提交
  7. 06 1月, 2012 2 次提交
  8. 17 12月, 2011 1 次提交
  9. 07 12月, 2011 1 次提交
  10. 17 11月, 2011 1 次提交
  11. 17 9月, 2011 3 次提交
  12. 18 8月, 2011 1 次提交
  13. 11 8月, 2011 1 次提交
  14. 14 7月, 2011 1 次提交
  15. 25 6月, 2011 2 次提交
    • B
      sfc: Fix mapping of reset reasons and flags to methods · 0e2a9c7c
      Ben Hutchings 提交于
      There are certain hardware bugs that may occur on Falcon during normal
      operation, that require a reset to recover from.  We try to minimise
      disruption by keeping the PHY running, following a reset sequence
      labelled as 'invisible'.
      
      Siena does not suffer from these hardware bugs, so we have not
      implemented an 'invisible' reset sequence.  However, if a similar
      error does occur (due to a hardware fault or software bug) then the
      code shared with Falcon will wrongly assume that the PHY is not being
      reset.
      
      Since the mapping of reset reasons (internal) and flags (ethtool) to
      methods must differ significantly between NIC types, move it into
      per-NIC-type functions (replacing the insufficient reset_world_flags
      field).
      Signed-off-by: NBen Hutchings <bhutchings@solarflare.com>
      0e2a9c7c
    • B
      sfc: Allow resets to be upgraded; use atomic ops for safety · a7d529ae
      Ben Hutchings 提交于
      Currently an attempt to schedule any reset is ignored if a reset
      is already pending.  This ignores the relative scopes - if the
      requested reset is greater in scope then the scheduled reset should
      be upgraded accordingly.
      
      There are also some race conditions which could lead to a reset
      request being lost.  Deal with them by using atomic operations on a
      bitmask.  This also makes tests on reset_pending easier to get right.
      Signed-off-by: NBen Hutchings <bhutchings@solarflare.com>
      a7d529ae
  16. 18 5月, 2011 1 次提交