Odd QMI devices - ZTE MF60

Bjørn Mork bjorn at mork.no
Thu Jul 5 12:26:07 PDT 2012


Aleksander Morgado <aleksander at lanedo.com> writes:

>> If you want to give it a try, qmicli now supports it as well, e.g.:
>> $> sudo qmicli -d /dev/cdc-wdm0 \
>>                --device-open-instance-id=5 \
>>                --dms-get-manufacturer \
>>                --verbose
>> 
>
> So, new approach now. Instead of a flag for qmi_device_open(), I
> prepared a new qmi_device_set_instance_id() which does all the job. Much
> cleaner as no need to define the instance id value when creating the
> QmiDevice. qmicli also supports `--device-set-instance-id=X' as well.
> It's already in libqmi git master, so you can forget about that previous
> branch.

Looks good.  Makes the MF60 work as expected, as long as I stay away
from QMI_WDS.  And no QMI_DMS commands seem not crash the firmware, even
the unsupported ones.

I wonder if this helps with Dan's Novatel USB551L as well?  I've now
looked through the Windows snoop a couple of times, and it does *not*
contain any QMI_WDS connect commands. The only QMI_WDS commands there
are two "set family", one for IPv4 and one for IPv6.  And it does have a
"set instance id" before issues these.

Maybe the Novatel firmware also prefers to manage connections, need "set
instance id", and refuse most QMI_WDS commands?


Bjørn


More information about the libqmi-devel mailing list