From: Christopher Vogl <christopher.vogl@hale.at>
To: ofono@ofono.org
Subject: Re: [PATCH 2/3] Drop checking whether +CMER is supported.
Date: Tue, 18 Dec 2012 11:08:14 +0100 [thread overview]
Message-ID: <50D0408E.40100@hale.at> (raw)
In-Reply-To: <1355761338-9081-3-git-send-email-mingli@southpole.se>
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
On 17/12/12 17:22, Mingli Wu wrote:
> For Telit HE910, ofono always got "\r\n+CME ERROR: 14\r\n"
> after issuing "AT+CMER=3,0,0,2\r" command. "CME ERROR: 14"
> means that SIM is busy. Now we igonre the result of the
> command "AT+CMER=3,0,0,2\r", and register network anyway.
> ---
I submitted some patches which will solve this problem.
You should not get CME ERROR: 14 anymore and hence
the netreg atom will not be removed.
There is not need to make changes in the network registration atom.
Telit supports +CMER but without waiting for the modem to be ready
the command will fail.
Regards,
Christopher
--
Scanned by MailScanner.
next prev parent reply other threads:[~2012-12-18 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 16:22 [PATCH 0/3] Telit HE910 Mingli Wu
2012-12-17 16:22 ` [PATCH 1/3] Support Telit cdc acm device Mingli Wu
2012-12-17 16:34 ` Denis Kenzior
2012-12-17 18:39 ` Ming Li Wu
2012-12-17 16:22 ` [PATCH 2/3] Drop checking whether +CMER is supported Mingli Wu
2012-12-17 16:27 ` Denis Kenzior
2012-12-18 10:08 ` Christopher Vogl [this message]
2012-12-17 16:22 ` [PATCH 3/3] Delay 10 seconds between CFUN=4 and CFUN=1 Mingli Wu
-- strict thread matches above, loose matches on Subject: below --
2013-03-29 15:40 [PATCH 2/3] Drop checking whether +CMER is supported Etienne Mabille
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50D0408E.40100@hale.at \
--to=christopher.vogl@hale.at \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox