1. 24 9月, 2009 1 次提交
  2. 23 9月, 2009 1 次提交
    • B
      USB: gadget: Add EEM gadget driver · 9b39e9dd
      Brian Niebuhr 提交于
      This patch adds a CDC EEM ethernet gadget driver.  CDC EEM is a newer
      USB ethernet specification that uses a simpler interface than the older
      CDC ECM.  This makes CDC EEM usable by a wider set of USB hardware.
      By default the ethernet gadget will still use CDC ECM/Subset, but kernel
      configuration and/or a module parameter will allow alternative use of
      the CDC EEM protocol.
      
      Changes since last version:
      	- Brought in missing RNDIS changes that caused compile error
      	- Modified 'sentinel CRC' checking to match EEM host driver
      Signed-off-by: NBrian Niebuhr <bniebuhr@efjohnson.com>
      Cc: David Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      9b39e9dd
  3. 02 9月, 2009 1 次提交
  4. 01 9月, 2009 1 次提交
  5. 06 7月, 2009 1 次提交
  6. 13 6月, 2009 1 次提交
  7. 18 4月, 2009 1 次提交
  8. 08 1月, 2009 1 次提交
  9. 20 11月, 2008 1 次提交
  10. 28 10月, 2008 1 次提交
  11. 18 10月, 2008 1 次提交
    • D
      usb gadget: cdc ethernet notification bugfix · 29bac7b7
      David Brownell 提交于
      Bugfix for the new CDC Ethernet code:  as part of activating the
      network interface's USB link, make sure its link management code
      knows whether the interface is open or not.
      
      Without this fix, the link won't work right when it's brought up
      before the link is active ... because the initial notification it
      sends will have the wrong link state (down, not up).  Makes it
      hard to bridge these links (on the host side), among other things.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Cc: stable <stable@kernel.org> [2.6.27]
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      29bac7b7
  12. 17 10月, 2008 1 次提交
  13. 26 7月, 2008 1 次提交
  14. 22 7月, 2008 1 次提交
    • D
      usb ethernet gadget: split out network core · 2b3d942c
      David Brownell 提交于
      Abstract the peripheral side Ethernet-over-USB link layer code from
      the all-in-one Ethernet gadget driver into a component that can be
      called by various functions, so the various flavors can be split
      apart and selectively reused.
      
      A notable difference from the approach taken with the serial link
      layer code (beyond talking to NET not TTY) is that because of the
      initialization requirements, this only supports one network link.
      (And one set of Ethernet link addresses.)
      
      That is, each configuration may have only one instance of a network
      function.  This doesn't change behavior; the current code has that
      same restriction.  If you want multiple logical links, that can
      easily be done using network layer tools.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      2b3d942c