Commit 786e3dfb authored by Bjorge Dijkstra's avatar Bjorge Dijkstra Committed by David S. Miller

cdc_ether: Hardwire CDC descriptors when missing

Just as ActiveSync devices, some regular RNDIS devices also lack
the CDC descriptors (e.g. devices based on BCM4320 WLAN chip).
This patch hardwires the CDC descriptors for all RNDIS style devices
when they are missing.
Signed-off-by: default avatarBjorge Dijkstra <bjd@jooz.net>
Signed-off-by: default avatarJussi Kivilinna <jussi.kivilinna@mbnet.fi>
Acked-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 2bfa2e1f
...@@ -228,15 +228,16 @@ next_desc: ...@@ -228,15 +228,16 @@ next_desc:
buf += buf [0]; buf += buf [0];
} }
/* Microsoft ActiveSync based RNDIS devices lack the CDC descriptors, /* Microsoft ActiveSync based and some regular RNDIS devices lack the
* so we'll hard-wire the interfaces and not check for descriptors. * CDC descriptors, so we'll hard-wire the interfaces and not check
* for descriptors.
*/ */
if (is_activesync(&intf->cur_altsetting->desc) && !info->u) { if (rndis && !info->u) {
info->control = usb_ifnum_to_if(dev->udev, 0); info->control = usb_ifnum_to_if(dev->udev, 0);
info->data = usb_ifnum_to_if(dev->udev, 1); info->data = usb_ifnum_to_if(dev->udev, 1);
if (!info->control || !info->data) { if (!info->control || !info->data) {
dev_dbg(&intf->dev, dev_dbg(&intf->dev,
"activesync: master #0/%p slave #1/%p\n", "rndis: master #0/%p slave #1/%p\n",
info->control, info->control,
info->data); info->data);
goto bad_desc; goto bad_desc;
...@@ -316,7 +317,6 @@ void usbnet_cdc_unbind(struct usbnet *dev, struct usb_interface *intf) ...@@ -316,7 +317,6 @@ void usbnet_cdc_unbind(struct usbnet *dev, struct usb_interface *intf)
} }
EXPORT_SYMBOL_GPL(usbnet_cdc_unbind); EXPORT_SYMBOL_GPL(usbnet_cdc_unbind);
/*------------------------------------------------------------------------- /*-------------------------------------------------------------------------
* *
* Communications Device Class, Ethernet Control model * Communications Device Class, Ethernet Control model
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment