Dan Williams <dcbw@xxxxxxxxxx> writes: > On Wed, 2014-07-23 at 14:33 +0000, Stanescu Victor wrote: >> /dev/cdc-wdm2 doesn't work. Further more, instead of freezing at cat, it >> freezes from echo. >> >> Ctrl-c doesn't stop the frozen echo. > > I'm pretty sure this device does not expose QMI at all, from looking at > through the drivers. The driver package from HP *does* have QMI > drivers, but only for the lt4112/lt4124/lt4126. The hs3110/hs3114 are > assigned to the "Jungo"-type driver for Win < 8. For example: > > <DeviceInfo> > <item module="MU736" VID="03F0" PID="521D" Baseline="JUNGO" Remark="HP"/> > <item module="MU736" VID="03F0" PID="541D" Baseline="JUNGO" Remark="HP"/> > <item module="ME906" VID="03F0" PID="581D" Baseline="QUALCOMM" Remark="HP"/> > <item module="ME906" VID="03F0" PID="561D" Baseline="QUALCOMM" Remark="HP"/> > <item module="ME906" VID="03F0" PID="591D" Baseline="QUALCOMM" Remark="HP"/> > </DeviceInfo> Doesn't look like qmi_wwan currently supports those QUALCOMM devices. It probably should? Do you know if all these use Huawei's vendor specific subclass+protocol scheme? > In any case, if the devices have MBIM descriptors, then we should try to > drive them via MBIM, since that appears to be what happens with these > devices on Windows 8. Yes, that should be the priority. We need to figure out why the modem cannot(?) be switched to cfg #2. That's where we primarily want it. > Otherwise, it should be AT+ECM I think, but not > QMI for the 3110/3114. Ah, OK. Then we probably don't have a 100% matching driver candidate, do we? Can't be a big problem to fix though. But I'm leaving for a 4 week motorcycling/fishing/hiking/whatever vacation tomorrow, so I guess I shouldn't promise anything :-) 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
