RE: Failed to find primary AT port

Hello Dan, I have built ModemManager1.4.0 (only this version is running properly on Quectel UC20 modem currently) for ARM architecture with your suggestions: > The UC20 should be using QMI, not AT ports. qmi_wwan support for the > UC20 has been there since 2013. But to use it, you need to: >

RE: Failed to find primary AT port

Hello Dan, Thank you for your response. I have looked into ModemManager version 1.6.4 and this patch you are mentioning in your e-mail does not reflect the line number in src/mm-base-modem.c: @@ -219,6 +219,12 @@ mm_base_modem_grab_port (MMBaseModem *self,

Re: Failed to find primary AT port

On Wed, 2017-04-05 at 17:29 +, Jan Graczyk wrote: > Hello Dan, > > Is ModemManager baud rate configurable to a different value? I know > that by default ModemManager runs properly with modem baud rate set > to 57600. Aleksander committed a patch two weeks ago that allow configuring the baud

RE: Failed to find primary AT port

Hello Dan, Is ModemManager baud rate configurable to a different value? I know that by default ModemManager runs properly with modem baud rate set to 57600. Best Regards, Jan Graczyk -Original Message- From: Dan Williams [mailto:d...@redhat.com] Sent: Tuesday, April 4, 2017 12:19 PM

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

Hi Dan, 2017-04-03 21:52 GMT+02:00 Dan Williams : > 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: Confirmed, when this command is supported as far as I know there is only one integer.