linux-stable.git/drivers/net/usb/plusb.c, branch linux-3.2.y

usb: plusb: Add support for National Instruments host-to-host cable

2015-05-09T22:16:38+00:00

[ Upstream commit 42c972a1f390e3bc51ca1e434b7e28764992067f ]

The National Instruments USB Host-to-Host Cable is based on the Prolific
PL-25A1 chipset.  Add its VID/PID so the plusb driver will recognize it.

Signed-off-by: Ben Shelton 
Signed-off-by: David S. Miller 
Signed-off-by: Ben Hutchings

usb: plusb: Add debug to reset function

2011-04-11T01:46:45+00:00

This patch adds some debug to the reset function to print out the
reason why it fails.

Signed-off-by: Simon Wood 
Signed-off-by: David S. Miller

usb: plusb: Add support for PL-25A1

2011-04-11T01:46:44+00:00

This patch adds support for the PL-25A1 by adding the appropriate
USB ID's. This chip is used in the Belkin 'Windows Easy Transfer'
Cables.

Signed-off-by: Simon Wood 
Signed-off-by: David S. Miller

usb: plusb: Whitespace

2011-04-11T01:46:44+00:00

This patch cleans up a couple of instances of incorrect whitespace

Signed-off-by: Simon Wood 
Signed-off-by: David S. Miller

usbnet: use eth%d name for known ethernet devices

2011-04-02T03:12:02+00:00

The documentation for the USB ethernet devices suggests that
only some devices are supposed to use usb0 as the network interface
name instead of eth0. The logic used there, and documented in
Kconfig for CDC is that eth0 will be used when the mac address
is a globally assigned one, but usb0 is used for the locally
managed range that is typically used on point-to-point links.

Unfortunately, this has caused a lot of pain on the smsc95xx
device that is used on the popular pandaboard without an
EEPROM to store the MAC address, which causes the driver to
call random_ether_address().

Obviously, there should be a proper MAC addressed assigned to
the device, and discussions are ongoing about how to solve
this, but this patch at least makes sure that the default
interface naming gets a little saner and matches what the
user can expect based on the documentation, including for
new devices.

The approach taken here is to flag whether a device might be a
point-to-point link with the new FLAG_POINTTOPOINT setting in
the usbnet driver_info. A driver can set both FLAG_POINTTOPOINT
and FLAG_ETHER if it is not sure (e.g. cdc_ether), or just one
of the two.  The usbnet framework only looks at the MAC address
for device naming if both flags are set, otherwise it trusts the
flag.

Signed-off-by: Arnd Bergmann 
Tested-by: Andy Green 
Signed-off-by: David S. Miller

Update broken web addresses in the kernel.

2010-10-18T09:03:14+00:00

The patch below updates broken web addresses in the kernel

Signed-off-by: Justin P. Mattock 
Cc: Maciej W. Rozycki 
Cc: Geert Uytterhoeven 
Cc: Finn Thain 
Cc: Randy Dunlap 
Cc: Matt Turner 
Cc: Dimitry Torokhov 
Cc: Mike Frysinger 
Acked-by: Ben Pfaff 
Acked-by: Hans J. Koch 
Reviewed-by: Finn Thain 
Signed-off-by: Jiri Kosina

Move usbnet.h and rndis_host.h to include/linux/usb

2008-02-01T03:27:00+00:00

Move headers usbnet.h and rndis_host.h to include/linux/usb and fix includes
for drivers/net/usb modules. Headers are moved because rndis_wlan will be
outside drivers/net/usb in drivers/net/wireless and yet need these headers.

Signed-off-by: Jussi Kivilinna 
Acked-by: David Brownell 
Signed-off-by: John W. Linville 
Signed-off-by: David S. Miller

Move USB network drivers to drivers/net/usb.

2007-05-10T01:31:55+00:00

It is preferable to group drivers by usage (net, scsi, ATA, ...) than
by bus.  When reviewing drivers, the [PCI|USB|PCMCIA|...] maintainer
is probably less qualified on networking issues than a networking
maintainer.  Also, from a practical standpoint, chips often
appear on multiple buses, which is why we do not put drivers into
drivers/pci/net.

Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Jeff Garzik