Ah, OK. I stand corrected then. Just from reading the docs, I was under the impression it was interacting directly with the smartphone’s modem.
In that case, just looking at the code that was changed:
}, {
/* RNDIS for tethering */
USB_INTERFACE_INFO(USB_CLASS_WIRELESS_CONTROLLER, 1, 3),
.driver_info = (unsigned long) &rndis_info,
}, {
/* Mobile Broadband Modem, seen in Novatel Verizon USB730L and
* Telit FN990A (RNDIS)
*/
USB_INTERFACE_INFO(USB_CLASS_MISC, 4, 1),
- .driver_info = (unsigned long) &rndis_info,
+ .driver_info = (unsigned long)&wwan_rndis_info,
},
{ }, // END
};
I see that there is a condition right above the USB_CLASS_MISC that is labeled USB_CLASS_WIRELESS_CONTROLLER and it states in the comment that it is specifically meant for “tethering”. If you can get your device to be recognized as USB_CLASS_WIRELESS_CONTROLLER instead of USB_CLASS_MISC then it will probably work like it used to. I don’t know how that code is determining those classes though. Someone would need to dig a little deeper.