All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 2/2] gatchat: add a GARBAGE state to handle random crud from a terminal adapter
Date: Thu, 06 Aug 2009 17:06:41 -0500	[thread overview]
Message-ID: <200908061706.41763.denkenz@gmail.com> (raw)
In-Reply-To: <20090805175131.2054657b@mycelium.queued.net>

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

Hi Andres,

> I've got a version of this that works w/ denkenz's new parser stuff;
> let me know if I should send that instead.
>
>
>
> From d6e942c2e0e2f51c5391e61aa7b5ac7326de28ea Mon Sep 17 00:00:00 2001
> From: Andres Salomon <dilinger@collabora.co.uk>
> Date: Tue, 4 Aug 2009 21:33:09 -0400
> Subject: [PATCH 2/2] gatchat: add a GARBAGE state to handle random crud
> from a terminal adapter
>
> When the TA sends random crap, oFono's parser gets confused and doesn't
> process the next few results (which causes oFono not to send further
> commands, and thus initialization never finishes).  This is less than
> ideal.
>
> This patch adds a new state; when the parser gets something that doesn't
> look like a proper response, it will simply ignore the entire line.  This
> allows initialization to continue when the TA does send spurious lines.

I've incorporated a modified version of this into the new default gsmv1 parser 
as part of the customizable parser patch.  This is now upstream, and I'd like 
to hear about how well it works.

Regards,
-Denis




      reply	other threads:[~2009-08-06 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 21:51 [PATCH 2/2] gatchat: add a GARBAGE state to handle random crud from a terminal adapter Andres Salomon
2009-08-06 22:06 ` Denis Kenzior [this message]

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=200908061706.41763.denkenz@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 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.