From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] telit: disable auto attach procedures with AUTOATT
Date: Mon, 20 Aug 2012 08:23:33 -0500 [thread overview]
Message-ID: <50323A55.1050709@gmail.com> (raw)
In-Reply-To: <50321B49.7020008@hale.at>
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
Hi Christopher,
On 08/20/2012 06:11 AM, Christopher Vogl wrote:
> Hi Denis,
>
> On 16/08/12 08:26, Denis Kenzior wrote:
>> Hi Christopher,
>>
>> On 08/16/2012 04:48 AM, Christopher Vogl wrote:
>>> ---
>>> plugins/telit.c | 6 ++++++
>>> 1 files changed, 6 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/plugins/telit.c b/plugins/telit.c
>>> index 6ae7249..feedd18 100644
>>> --- a/plugins/telit.c
>>> +++ b/plugins/telit.c
>>> @@ -307,6 +307,12 @@ static void cfun_enable_cb(gboolean ok,
>>> GAtResult *result, gpointer user_data)
>>>
>>> ofono_modem_set_powered(m, TRUE);
>>>
>>> + /*
>>> + * Tell the modem not to automatically initiate auto-attach
>>> + * proceedures on its own.
>>> + */
>>> + g_at_chat_send(data->chat, "AT#AUTOATT=0", none_prefix, NULL, NULL,
>>> NULL);
>>
>> This line is over 80 character limit.
>
> This will not happen again now. I will correct that in the new patch.
>
Cool ;)
>>
>> Also, are you sure this can be sent even if the PIN is locked?
>
> I have tried it with and without PIN locked and I always get an OK back.
> Where would you logically put it? Better move it to 'post sim'?
>
If it needed to be done after the SIM PIN was entered, then the best
place is in the gprs driver using a vendor quirk. If it can always be
sent, then doing it like you had originally is just fine.
Regards,
-Denis
next prev parent reply other threads:[~2012-08-20 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 9:48 [PATCH] telit: disable auto attach procedures with AUTOATT Christopher Vogl
2012-08-16 6:26 ` Denis Kenzior
2012-08-20 11:11 ` Christopher Vogl
2012-08-20 13:23 ` Denis Kenzior [this message]
2012-08-21 15:06 ` Christopher Vogl
2012-08-21 19:35 ` Denis Kenzior
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=50323A55.1050709@gmail.com \
--to=denkenz@gmail.com \
--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