All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Vogl <christopher.vogl@hale.at>
To: ofono@ofono.org
Subject: Re: [PATCH 2/2] netreg: Add telit version for ciev notification
Date: Wed, 12 Sep 2012 10:13:57 +0200	[thread overview]
Message-ID: <50504445.1000908@hale.at> (raw)
In-Reply-To: <50500E73.1090202@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2057 bytes --]

Hi Denis,

>
> Patch has been applied, however:
>
>> @@ -1618,6 +1649,19 @@ static void cind_support_cb(gboolean ok, 
>> GAtResult *result, gpointer user_data)
>>                   at_cmer_query_cb, netreg, NULL);
>>       g_at_chat_register(nd->chat, "+CIEV:",
>>                   ciev_notify, FALSE, netreg, NULL);
>> +
>> +    /*
>> +     * Telit uses strings instead of numbers to identify indicators
>> +     * in a +CIEV URC.
>> +     * Handle them in a separate function to keep the code clean.
>> +     */
>> +    if (nd->vendor == OFONO_VENDOR_TELIT)
>> +        g_at_chat_register(nd->chat, "+CIEV:",
>> +                telit_ciev_notify, FALSE, netreg, NULL);
>> +    else
>> +        g_at_chat_register(nd->chat, "+CIEV:",
>> +                ciev_notify, FALSE, netreg, NULL);
>> +
>
> You ended up registering for +CIEV twice, so I took that out in commit 
> bb0f308223816e53de0a5a6a2cdb6eb1f11856c8.

Thanks for fixing this! I missed to remove the previous code.

>
> Also, I made failing to initialize +CMER fatal in commit 
> b274e74102c7a4b96c06dba895cf0cb444fa54c3.  Can you please double-check 
> that it is working as intended, I only performed basic sanity checking 
> on my end.

I sent the CMER-string that is not supported by Telit (3,0,0,1) and the 
netreg atom gets removed after a corresponding error message (the modem 
still sets up a ppp connection afterwards):

...
Sep  12 03:39:01 mx31tt01 daemon.info ofonod[719]: Aux: > AT+CMER=?\r
Sep  12 03:39:01 mx31tt01 daemon.info ofonod[719]: Aux: < \r\n+CMER: 
(0-3),(0),(0),(0,2),(0)\r\n\r\nOK\r\n
Sep  12 03:39:01 mx31tt01 daemon.debug ofonod[719]: 
drivers/atmodem/network-registration.c:build_cmer_string()
Sep  12 03:39:01 mx31tt01 daemon.err ofonod[719]: +CMER not supported by 
this modem.  If this is an error please submit patches to support this 
hardware
Sep  12 03:39:01 mx31tt01 daemon.debug ofonod[719]: 
src/network.c:netreg_remove() atom: 0x17ab810
...

Regards,
Christopher

--
Scanned by MailScanner.


  reply	other threads:[~2012-09-12  8:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 13:23 [PATCH 7/8] netreg: adapt CMER and CIEV for telit Christopher Vogl
2012-08-13 16:25 ` Denis Kenzior
2012-08-14 14:16   ` Christopher Vogl
2012-08-14  6:46     ` Denis Kenzior
2012-08-16  6:57       ` Christopher Vogl
2012-08-16  5:57         ` Denis Kenzior
2012-09-06  9:25   ` [PATCH 2/2] netreg: Add telit version for ciev notification christopher.vogl
2012-09-06  9:25     ` [PATCH 1/2] netreg: Query and select supported CMER modes christopher.vogl
2012-09-06  9:36   ` [PATCH 2/2] netreg: Add telit version for ciev notification christopher.vogl
2012-09-06  9:49   ` christopher.vogl
2012-09-06  9:49     ` [PATCH 1/2] netreg: Query and select supported CMER modes christopher.vogl
2012-09-12  4:22       ` Denis Kenzior
2012-09-12  4:24     ` [PATCH 2/2] netreg: Add telit version for ciev notification Denis Kenzior
2012-09-12  8:13       ` Christopher Vogl [this message]
2012-09-12 13:53         ` Denis Kenzior
2012-09-12 15:07           ` Christopher Vogl

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=50504445.1000908@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.