1. 16 2月, 2010 1 次提交
  2. 12 2月, 2010 1 次提交
  3. 11 2月, 2010 1 次提交
  4. 07 10月, 2009 1 次提交
    • B
      ethtool: Add reset operation · d73d3a8c
      Ben Hutchings 提交于
      After updating firmware stored in flash, users may wish to reset the
      relevant hardware and start the new firmware immediately.  This should
      not be completely automatic as it may be disruptive.
      
      A selective reset may also be useful for debugging or diagnostics.
      
      This adds a separate reset operation which takes flags indicating the
      components to be reset.  Drivers are allowed to reset only a subset of
      those requested, and must indicate the actual subset.  This allows the
      use of generic component masks and some future expansion.
      Signed-off-by: NBen Hutchings <bhutchings@solarflare.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d73d3a8c
  5. 05 10月, 2009 1 次提交
  6. 03 9月, 2009 1 次提交
  7. 28 7月, 2009 1 次提交
  8. 27 7月, 2009 1 次提交
  9. 01 4月, 2009 1 次提交
  10. 20 2月, 2009 1 次提交
  11. 16 12月, 2008 1 次提交
  12. 02 7月, 2008 1 次提交
  13. 25 4月, 2008 1 次提交
    • M
      ethtool: EEPROM dump no longer works for tg3 and natsemi · c5835df9
      Mandeep Singh Baines 提交于
      In the ethtool user-space application, tg3 and natsemi over-ride the
      default implementation of dump_eeprom(). In both tg3_dump_eeprom() and
      natsemi_dump_eeprom(), there is a magic number check which is not
      present in the default implementation.
      
      Commit b131dd5d ("[ETHTOOL]: Add support for large eeproms") snipped
      the code which copied the ethtool_eeprom structure back to
      user-space. tg3 and natsemi are over-writing the magic number field
      and then checking it in user-space. With the ethtool_eeprom copy
      removed, the check is failing.
      
      The fix is simple. Add the ethtool_eeprom copy back.
      Signed-off-by: NMandeep Singh Baines <msb@google.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c5835df9
  14. 16 4月, 2008 1 次提交
  15. 11 10月, 2007 6 次提交
  16. 15 8月, 2007 1 次提交
  17. 01 8月, 2007 2 次提交
  18. 15 7月, 2007 1 次提交
  19. 26 4月, 2007 1 次提交
  20. 11 2月, 2007 1 次提交
  21. 29 9月, 2006 2 次提交
  22. 14 9月, 2006 1 次提交
  23. 18 7月, 2006 1 次提交
  24. 23 6月, 2006 1 次提交
  25. 18 6月, 2006 2 次提交
  26. 12 1月, 2006 1 次提交
  27. 29 10月, 2005 1 次提交
    • A
      [IPv4/IPv6]: UFO Scatter-gather approach · e89e9cf5
      Ananda Raju 提交于
      Attached is kernel patch for UDP Fragmentation Offload (UFO) feature.
      
      1. This patch incorporate the review comments by Jeff Garzik.
      2. Renamed USO as UFO (UDP Fragmentation Offload)
      3. udp sendfile support with UFO
      
      This patches uses scatter-gather feature of skb to generate large UDP
      datagram. Below is a "how-to" on changes required in network device
      driver to use the UFO interface.
      
      UDP Fragmentation Offload (UFO) Interface:
      -------------------------------------------
      UFO is a feature wherein the Linux kernel network stack will offload the
      IP fragmentation functionality of large UDP datagram to hardware. This
      will reduce the overhead of stack in fragmenting the large UDP datagram to
      MTU sized packets
      
      1) Drivers indicate their capability of UFO using
      dev->features |= NETIF_F_UFO | NETIF_F_HW_CSUM | NETIF_F_SG
      
      NETIF_F_HW_CSUM is required for UFO over ipv6.
      
      2) UFO packet will be submitted for transmission using driver xmit routine.
      UFO packet will have a non-zero value for
      
      "skb_shinfo(skb)->ufo_size"
      
      skb_shinfo(skb)->ufo_size will indicate the length of data part in each IP
      fragment going out of the adapter after IP fragmentation by hardware.
      
      skb->data will contain MAC/IP/UDP header and skb_shinfo(skb)->frags[]
      contains the data payload. The skb->ip_summed will be set to CHECKSUM_HW
      indicating that hardware has to do checksum calculation. Hardware should
      compute the UDP checksum of complete datagram and also ip header checksum of
      each fragmented IP packet.
      
      For IPV6 the UFO provides the fragment identification-id in
      skb_shinfo(skb)->ip6_frag_id. The adapter should use this ID for generating
      IPv6 fragments.
      Signed-off-by: NAnanda Raju <ananda.raju@neterion.com>
      Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (forwarded)
      Signed-off-by: NArnaldo Carvalho de Melo <acme@mandriva.com>
      e89e9cf5
  28. 06 9月, 2005 1 次提交
  29. 30 8月, 2005 1 次提交
  30. 07 6月, 2005 1 次提交
  31. 30 5月, 2005 2 次提交