Dan Williams <dcbw@xxxxxxxxxx> writes: > So the Pantech UML290 has the following layout: > > 0 (2/2/1): CDC-ACM for AT commands > 1 (10/0/0): CDC-DATA for interface 0 > 2 (ff/ff/ff): Qualcomm DIAG > 3 (ff/fd/ff): NMEA > 4 (ff/fe/ff): Pantech WMC > 5 (ff/f0/ff): RMNET/QMI port I assume this is after som modeswitch command? The same as the Windows driver uses? And you don't know if there are other options? > Interface 5 is obviously the one we want here. And the WDM driver is > only looking for certain descriptors. Do we hack CDC-WDM and qmi_wwan > up for these types of devices? Interface 5 has three endpoints? Bulk in/out and interrupt in? OK, this is where the fun begins. I knew there was some reason why I was struggling with the interface sharing... I guess we cannot expect every vendor to provide a "Linux mode" with two separate interfaces for the RMNET/QMI port. > Second, on Gobi devices, we have four USB interfaces, all FF/FF/FF. > Intf 0 and 2 have interrupt endpoints. One of them is a DIAG interface, > one is NMEA, and the other two are AT and RMNET/QMI. What kind of endpoints are on the RMNET/QMI interface? If you have these devices, then it would be useful to verify that the cdc-wdm driver can be used to provide access to QMI without any further changes. This should in theory just work if you unload any other drivers binding to the RMNET/QMI interface, and bind cdc-wdm to it instead. This requires that you have the minimum buffer size patch installed, but should not require any other changes. > I think so far the Huawei device is the only one that I've seen that > exposes descriptors that are quasi-CDC at all. How should we handle the > rest of these? Good question. Guess I'm going to see if I can make qmi_wwan and cdc-wdm share an interface after all. Bjørn -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
