Telit LE910-NVG

[Randy Yates]

Bjorn, first, thank you very much for your help. I respond
to you below. Also note that my mail server went down
just after I posted this message to the list. It is now
back up.

Bjorn Mork write:
> Randy Yates <yates at digitalsignallabs.com> writes:
> 
> > After running this code, the 910 enumerates on the USB bus. I see
> > /dev/ttyUSB0 through /dev/ttyUSB4. I can also connect to /dev/ttyUSB2
> > and issue AT commands successfully, e.g., "AT+GSN" and receive the
> > IMEI number back.
> >
> > Also the result of lsusb looks right:
> >
> >   root at arm:~# lsusb
> >   Bus 001 Device 002: ID 1bc7:1201 Telit 
> >   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> ..
> > The qmi_wwan kernel module also appears to be loaded as evidenced
> > from the lsmod:
> 
> qmi_wwan is supposed to bind to interface #2 on that device.  I don't
> know why it hasn't.  dmesg output would be good.  Maybe there is some
> error?  Or maybe some other driver has bound to that interface already?
> It is blacklisted in the option driver, but if you (or some script) has
> messed with dynamic IDs then it could still be taken.

This is all new information to me. I've been clueless. Thank you!

> A few commands to try debug this further:
>  lsusb -vd 1bc7:1201

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lsusb.txt
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20160205/52d7341d/attachment-0003.txt>
-------------- next part --------------

>  ls -ld /sys/bus/usb/devices/*/driver

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ls.txt
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20160205/52d7341d/attachment-0004.txt>
-------------- next part --------------

>  dmesg

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dmesg.txt
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20160205/52d7341d/attachment-0005.txt>
-------------- next part --------------

>  cat /sys/bus/usb-serial/drivers/option1/new_id

Nothing resulted. 
-- 
Randy Yates, DSP/Embedded Firmware Developer
Digital Signal Labs
http://www.digitalsignallabs.com