how to support EM7565 modem
dailijin126 at 126.com
Mon Nov 20 09:50:33 UTC 2017
I don't know how to commit the patch. so need you do that.
The modem information as below :
[ 11.420430] usb 1-5.6: new high-speed USB device number 9 using xhci_hcd
[ 11.513262] usb 1-5.6: config 1 has an invalid interface number: 8 but max is 3
[ 11.513265] usb 1-5.6: config 1 has no interface number 1
[ 11.514059] usb 1-5.6: New USB device found, idVendor=1199, idProduct=9091
[ 11.514061] usb 1-5.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 11.514062] usb 1-5.6: Product: Sierra Wireless EM7565 Qualcomm® Snapdragon™ X16 LTE-A
[ 11.514063] usb 1-5.6: Manufacturer: Sierra Wireless, Incorporated
[ 11.514064] usb 1-5.6: SerialNumber: dbb8769f
[ 11.516208] qmi_wwan 1-5.6:1.8: cdc-wdm1: USB WDM device
[ 11.516330] qmi_wwan 1-5.6:1.8 wwan0: register 'qmi_wwan' at usb-0000:00:14.0-5.6, WWAN/QMI device, e2:e8:55:d3:8a:cc
[ 11.520855] GobiSerial 1-5.6:1.0: GobiSerial converter detected
[ 11.520913] usb 1-5.6: GobiSerial converter now attached to ttyUSB1
[ 11.521378] GobiSerial 1-5.6:1.2: GobiSerial converter detected
[ 11.521420] usb 1-5.6: GobiSerial converter now attached to ttyUSB2
[ 11.521974] GobiSerial 1-5.6:1.3: GobiSerial converter detected
[ 11.522026] usb 1-5.6: GobiSerial converter now attached to ttyUSB3
Now only ttyUSB3 can respond AT command, should be modem port. not sure the other two serial is NMEA port or DM port
在 2017-11-20 17:34:12，"Bjørn Mork" <bjorn at mork.no> 写道：
>Great! Thanks. Will you submit a patch, or should I? How about the
>serial functions? Er they mapped similar to previous Sierra modems
>(0 - diag, 2 - nmea, 3 - modem)? If so, then the ID should also be
>added as DEVICE_SWI to qcserial.
>dailijin <dailijin126 at 126.com> writes:
>> Hi Bjorn,
>> Only update investigation result.
>> After add 1199:9091 into qmi_wwan, the modem will create one wwan interface and one cdc-wdmx interface. then I can make it work with RAW-IP mode.
>> Best Regards,
>> At 2017-11-14 22:27:34, "Bjørn Mork" <bjorn at mork.no> wrote:
>>>dailijin <dailijin126 at 126.com> writes:
>>>> I just tested GobiNet driver for the modem, seems only the latest
>>>> GobiNet driver can support the modem. so not sure whether also need
>>>> new qmi_wwan driver to support it. the modem pid:vid is 1199:9091
>>>> which is not included in qmi_wwan driver now.
>>>> I have no environment now. will update my investigation result when I
>>>> have the modem again.
>>>Looking forward to that. Please post as much details as you can about
>>>the modem and testing. I guess it will take some time before this modem
>>>is generally available, based on the MC/EM7455 experiences.
>>>Adding a new ID to qmi_wwan should be no problem if you are able to
>>>build GobiNet. It's also possible to test the modem by adding the ID
>>>dynamically, using the new_id attribute. But then you have to take
>>>special care to make sure only the QMI interface(s) are bound to the
>>>If you can do any testing in MBIM mode, then those results would also be
>>>interesting. This should just work without any driver or userspace
>>>changes. In theory...
>>>libqmi-devel mailing list
>>>libqmi-devel at lists.freedesktop.org
>libqmi-devel mailing list
>libqmi-devel at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the libqmi-devel