22 Jul, 2008
4 commits
-
This is a RNDIS function driver, extracted from the all-in-one
Ethernet gadget driver.Lightly tested ... there seems to be a pre-existing problem when
talking to Windows XP SP2, not quite sure what's up with that yet.Signed-off-by: David Brownell
Signed-off-by: Greg Kroah-Hartman -
This is a "CDC Ethernet" (ECM) function driver, extracted from the
all-in-one Ethernet gadget driver.This is a good example of how to implement interface altsettings.
In fact it's currently the only such example in the gadget stack,
pending addition of OBEX support.Signed-off-by: David Brownell
Signed-off-by: Greg Kroah-Hartman -
This is a simple "CDC Subset" (and MCCI "SAFE") function driver, extracted
from the all-in-one Ethernet gadget driver.Signed-off-by: David Brownell
Signed-off-by: Greg Kroah-Hartman -
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: David Brownell
Signed-off-by: Greg Kroah-Hartman
