Bjørn Mork <bjorn@xxxxxxx> writes: > Anyone? Should I just submit this set as-is? > > New "Gobi 4000" device IDs are popping up as laptop vendors start > selling these things pre-installed. Just noticed Lenovo adding MC7700 > and MC7750 modules using different vendor IDs from the MC77xx we've got > covered. And Sony have added a "wwan lte" option to some of their European models, providing Windows QMI drivers from Sierra Wireless: http://www.sony.no/support/no/product/SVZ1311C5E/downloads/WWAN_LTE_Driver__6325 Based on the Windows driver, I assume the card is a plain QMI version MC7710. > These should be added to some serial driver, but I'd really > like to avoid "sierra" as the modules don't support that protocol and we > end up waiting for it to time out on probing. Just to make it clear: We currently punish owners of these modems with a 3 x 5 second pause while the sierra driver waits for the unsupported vendor specific "set power state" request to time out. As wwan cards are usually powered down on suspend, we also add the 15 seconds before the card is ready after resuming. All completely unnecessary... Just a bad driver choice. > Do we want qcserial to handle them? I've convinced myself that we do, based on the fact that the Windows driver label them as "Gobi" or "Gobi 4000", and that they do provide a Qualcomm Device Management port, a NMEA port and an AT port, just like any other Gobi modems. But I do not have access to any Gobi 1k or 2k modems, making it a bit risky doing more than minor changes to the driver. I was hoping someone with a previously supported modem would test these patches, so that it wasn't completely blind coded... Well, time is running out for 3.6, if it hasn't already run out... I'll brush up the patches, incorporate the single editorial comment I got, and submit them formally for usb-next. We can always fix or revert if everything went bananas :-) 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
