On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote: > On 2016-02-19 17:31, Bjørn Mork wrote: > > Daniel Johnson <teknotus@xxxxxxxxx> writes: > > > > > > > Currently 4 ttyUSB devices are detected, but only the second > > > > > two respond to > > > > > AT commands. The first two serial ports may be falsely > > > > > detected. > > > > > > > > One of them is likely a QCDM port if this is really a Qualcomm > > > > based > > > > device. The other might be an inactive NMEA port. Serial > > > > doesn't > > > > necessarily imply AT commands... > > > > > > cfg #1 > MI_00 HP Mobile Connect - PC UI Interface > MI_01 HP Mobile Connect - Application Interface > MI_02 HP Mobile Connect - Modem > MI_03 HP Mobile Connect - Network Card (jungo ncm) > MI_04 HP Mobile Connect - GPS Interface > > cfg#2 > MI_00 HP Mobile Connect - Network Card (cdc_ether) > MI_02 HP Mobile Connect - Modem > MI_03 HP Mobile Connect - Application Interface > MI_04 HP Mobile Connect - PC UI Interface > MI_05 HP Mobile Connect - GPS Interface > > cfg#3 > MI_00 HP Mobile Connect - Network Card (cdc_mbim) > MI_02 HP Mobile Connect - GPS Interface Bjorn, with these devices that technically "support" a bunch of different modes, what should our advice be on mode select? Personally I'd love to switch modems that support MBIM into MBIM by default... Dan -- 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
