Cannot subscribe to ModemManager-devel

[David McCullough]

Aleksander Morgado wrote the following:
> On Wed, Feb 12, 2014 at 10:18 AM, Aleksander Morgado
> <aleksander at aleksander.es> wrote:
> > On Wed, Feb 12, 2014 at 10:04 AM, Aleksander Morgado
> > <aleksander at aleksander.es> wrote:
> >> On Wed, Feb 5, 2014 at 11:15 AM, Aleksander Morgado
> >> <aleksander at aleksander.es> wrote:
> >>>>>
> >>>>> Are you testing all three with the same SIM card?
> >>>>
> >>>> Yes,  same host system, same software,  same SIM,  different cards.
> >>>>
> >>>> I was under the impression that "card makers" could reduce costs by not
> >>>> including various modules in their firmware.  Perhaps the PPP support or
> >>>> something else is just not there.
> >>>>
> >>>
> >>> I keep on thinking that the PXS8 is QMI-based, same as the PLS8 that I
> >>> have myself. Likely the VID/PIDs are just missing in qmi_wwan.
> >>>
> >>
> >> I got a Cinterion PHS8-P now, branded by MC technologies (not a PXS8),
> >> and it actually only shows one tty and I see no QMI capabilities in
> >> that one...
> >>
> >
> > Ah, look:
> >
> > ModemManager[25133]: <debug> [1392196544.656494]
> > [mm-at-serial-port.c:436] debug_log(): (ttyUSB2): -->
> > 'ATD*99***1#<CR>'
> > ModemManager[25133]: <debug> [1392196544.693918]
> > [mm-at-serial-port.c:436] debug_log(): (ttyUSB2): <-- '<CR><LF>+CME
> > ERROR: 2<CR><LF>'
> > ModemManager[25133]: <debug> [1392196544.693990]
> > [mm-serial-parsers.c:364] mm_serial_parser_v1_parse(): Got failure
> > code 2: Phone-adaptor link reserved
> >
> > I used a cinterion-specific command, which I'm not sure I'm able to
> > disclose, to get multiple ttys in the device instead of the single
> > ttyACM0, and now I get that error you were seeing. I wonder if it's
> > just the wrong tty being picked for the data connection...
> >
> 
> So yeah, in my case using ttyUSB2 gets me the Phone-adaptor link
> reserved error, but when using ttyUSB3 it gets connected properly:
> 
> ModemManager[26453]: <debug> [1392197119.981303]
> [mm-at-serial-port.c:436] debug_log(): (ttyUSB3): -->
> 'ATD*99***1#<CR>'
> ModemManager[26453]: <debug> [1392197120.030457]
> [mm-at-serial-port.c:436] debug_log(): (ttyUSB3): <--
> '<CR><LF>CONNECT<CR><LF>'
> 
> I'll try to dig a bit more to see if the modem tells us with some AT
> command which port is supposed to do what. Otherwise, I guess we'll
> need to add some port type hints in udev rules...

Ok,  sounds like I have the same modem.  The MFG responded to me just
recently about the tty issue and I had't got around to replying to you
guys about it.

ttyUSB3 works,  but I also got QMI working with mine as well.  The
following entry in qmi_wwan.c:

	{QMI_FIXED_INTF(0x1e2d, 0x0053, 4)},    /* Cinterion PX8 */

The VID/PID is 1e2d:0053 and it looks pretty standard with 3 tty's and
a QMI interface.  The ttys were already supported,  just MM selecting the
wrong one,

Cheers,
Davidm

-- 
David McCullough,  david.mccullough at accelecon.com,   Ph: 0410 560 763