RE: Failed to find primary AT port

Hello Dan, Thank you for your response. The next question I have for you is how to cross compile ModemManager for ARM architecture. I am using ModemManager version 1.4.2 to build. Is that version stable enough to run on ARM based processor? The version of ModemManager on my target is 1.4.0 and

Re: [PATCH] novatel-lte: revert to original plugin library name

On Mon, 2017-04-03 at 13:05 -0700, Ben Chan wrote: > Commit f9c63bfa0 "build,plugins: update build rules" accidentally > changed the Novatel LTE plugin from 'libmm-plugins-novatel-lte.so' to > 'libmm-plugins-novatel_lte.so'. The name becomes inconsistent with > other > plugin names. Seems fine to

[PATCH] novatel-lte: revert to original plugin library name

Commit f9c63bfa0 "build,plugins: update build rules" accidentally changed the Novatel LTE plugin from 'libmm-plugins-novatel-lte.so' to 'libmm-plugins-novatel_lte.so'. The name becomes inconsistent with other plugin names. --- It probably doesn't matter how the plugin library is named, but the

[PATCH] telit: fix AT+SERVICE 3GPP2 access technology reporting

Looks like a C error from the AT#PSNT codepath; all the docs I can find indicate that AT+SERVICE returns only an integer and no commas: (ttyUSB2): --> 'AT+SERVICE?' (ttyUSB2): <-- '+SERVICE: 3OK' Couldn't refresh access technologies: 'Failed to parse +SERVICE response: '+SERVICE: 3'' ---  

Re: [PATCH] novatel: port custom init and IMSI loading to use GTask

sgtm. Forgot to add --in-reply-to, so the revised patches are sent to: https://lists.freedesktop.org/archives/modemmanager-devel/2017-April/004394.html https://lists.freedesktop.org/archives/modemmanager-devel/2017-April/004395.html On Sun, Apr 2, 2017 at 12:28 AM, Aleksander Morgado

[PATCH 2/2] novatel: port IMSI loading to use GTask

--- plugins/novatel/mm-sim-novatel-lte.c | 89 +++- 1 file changed, 36 insertions(+), 53 deletions(-) diff --git a/plugins/novatel/mm-sim-novatel-lte.c b/plugins/novatel/mm-sim-novatel-lte.c index 41d30411..1088d0d0 100644 ---

[PATCH 1/2] novatel: port custom init to use GTask

--- plugins/novatel/mm-common-novatel.c | 62 + 1 file changed, 29 insertions(+), 33 deletions(-) diff --git a/plugins/novatel/mm-common-novatel.c b/plugins/novatel/mm-common-novatel.c index 4c39c7c7..a8f2da90 100644 --- a/plugins/novatel/mm-common-novatel.c

Re: [PATCH] telit: add error_code recognition to +CSIM parser

On Mon, 2017-04-03 at 17:01 +0200, Carlo Lobrano wrote: > Updated mm_telit_parse_csim_response in order to correctly recognize > the > following +CSIM error codes: > > * 6300 - Verification failed > * 6983 - Authentication method blocked > * 6984 - Reference data invalidated > * 6A86 - Incorrect

[PATCH] telit: add error_code recognition to +CSIM parser

Updated mm_telit_parse_csim_response in order to correctly recognize the following +CSIM error codes: * 6300 - Verification failed * 6983 - Authentication method blocked * 6984 - Reference data invalidated * 6A86 - Incorrect parameters * 6A88 - Reference data not found Fixes:

Re: Quectel UC20: Correct way to get it up and running on embedded?

Hi again. This is still a mess... On 28 March 2017 at 22:45, Aleksander Morgado wrote: > On Tue, Mar 28, 2017 at 8:39 PM, Dan Williams wrote: >>> > > RE PolicyMismatch: we're not quite sure what that error >>> > > represents; >>> > > we've determined

Re: [PATCH 1/1] mbim-modem: disable location interface

On Mon, Apr 3, 2017 at 8:52 AM, Thomas Voß wrote: > On Sun, Apr 2, 2017 at 10:37 AM, Aleksander Morgado > wrote: >> >> On Sat, Apr 1, 2017 at 10:11 PM, Thomas Voß >> wrote: >> > MBIM does not support 3gpp location data

Re: [PATCH 0/1] mbim modem: disable location interface

On Sun, Apr 2, 2017 at 9:18 AM, Aleksander Morgado wrote: > On Sat, Apr 1, 2017 at 10:11 PM, Thomas Voß > wrote: >> A simple patch to avoid MBIM modems reporting that they support the location >> interface. >> I haven't submitted patches

Re: [PATCH 1/1] mbim-modem: disable location interface

On Sun, Apr 2, 2017 at 10:37 AM, Aleksander Morgado wrote: > > On Sat, Apr 1, 2017 at 10:11 PM, Thomas Voß > wrote: > > MBIM does not support 3gpp location data right now. For that, > > we make sure that the location interface is not