Re: SMS sending error with Telit module

[Dan Williams <dcbw redhat com>]

On Tue, 2013-04-16 at 10:23 +0200, Enrico Murador - Research &
Development - CET wrote:
> On 15/04/2013 17:26, Dan Williams wrote:
> > Like I said, we can "tag" the ports via udev rules.  But we need to know
> > whether the port layouts are the same between all devices that share the
> > same VID/PID, or whether we need to use things like ATI responses to
> > determine what specific model the device is and how to tag it.  Does the
> > modem have any windows drivers that we could look at to determine this?
> >
> > Dan
>
> Sorry, I thought there was a "user" way to do this...
>
> To get Windows driver sources, I think you have to sign an NDA with Telit.
> Linux GSM/CDMA USB driver (usb/serial/option.c) is customized for 
> working with Telit modules. The file I linked in my previous post:
> http://www.telit.com/files/en/products/evk_drivers/Telit_UC_CC_DE_USB_Driver_for_Linux_U0_00_04_r3.pdf
> tells that, for UC864-E, port ordering is: ttyUSB0=Modem port; 
> ttyUSB1=Diagnostic port; ttyUSB2=Auxiliary port. It seems that they 
> consider that this ordering is fixed (see table on page 10).

What are the USB IDs again?

> This is the serial port list (by-id) I have already posted. Supposing 
> that we can consider this as persistent naming of module's ports... is 
> still necessary to make udev rules?
> lrwxrwxrwx 1 root root 13 apr 11 09:31 
> usb-Telit_Wireless_Solutions_Telit_HSDPA_Wireless_Modem_000000000002-if00-port0 
> -> ../../ttyUSB2
> lrwxrwxrwx 1 root root 13 apr 11 09:31 
> usb-Telit_Wireless_Solutions_Telit_HSDPA_Wireless_Modem_000000000002-if01-port0 
> -> ../../ttyUSB3
> lrwxrwxrwx 1 root root 13 apr 11 09:31 
> usb-Telit_Wireless_Solutions_Telit_HSDPA_Wireless_Modem_000000000002-if02-port0 
> -> ../../ttyUSB4

Yes, we want udev rules here because we'll use the USB interface number
to match ports, to ensure they don't get renamed.  That's better to do
than hardcoding some random kernel/udev links into ModemManager itself.

Dan