From: Guillaume Zajac <guillaume.zajac@linux.intel.com>
To: ofono@ofono.org
Subject: Re: [PATCH 3/6] gathdlc: add mechanism to detect ppp suspension from DUN client.
Date: Mon, 21 Mar 2011 15:17:10 +0100 [thread overview]
Message-ID: <4D875DE6.8010609@linux.intel.com> (raw)
In-Reply-To: <4D826B7E.4020507@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
Hi Denis,
On 17/03/2011 21:13, Denis Kenzior wrote:
> Hi Guillaume,
>
> On 03/15/2011 04:19 AM, Guillaume Zajac wrote:
>> ---
>> gatchat/gathdlc.c | 58 +++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 files changed, 58 insertions(+), 0 deletions(-)
> http://en.wikipedia.org/wiki/Time_Independent_Escape_Sequence
>
> If you really want to do this, then lets do this properly, including the
> guard timeouts.
>
> Regards,
> -Denis
>
I noticed also this guard timeouts after having sent the set of patches.
I will send a 2nd version of patches.
However I can't test the "+++" sequence with telnet because it is adding
some '\r' '\n' characters when I do do "+++" then "Enter".
I could try to filter those characters but it would add some specific
code for telnet test case.
I have tried to modifiy gsmdial to send "+++" 5 seconds after the 2 ppp
devices have been set up for instance.
I have implemented a g_at_ppp_send_escape_sequence() function to send
it. (this function directly writes on the GIOChannel)
Then the GAtChat is resumed and an ATH0 is sent.
Should I commit first the test case over gsmdial and then commit the
escape sequence detection mechanism?
Kind regards,
Guillaume
next prev parent reply other threads:[~2011-03-21 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 9:19 [PATCH 3/6] gathdlc: add mechanism to detect ppp suspension from DUN client Guillaume Zajac
2011-03-17 20:13 ` Denis Kenzior
2011-03-21 14:17 ` Guillaume Zajac [this message]
2011-03-21 18:57 ` Denis Kenzior
2011-03-22 8:57 ` Guillaume Zajac
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=4D875DE6.8010609@linux.intel.com \
--to=guillaume.zajac@linux.intel.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 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.