All of lore.kernel.org
 help / color / mirror / Atom feed
From: M. Dietrich <ofono@emdete.de>
To: ofono@ofono.org
Subject: Re:  fix for +CMER parser of AT driver (fixes registration)
Date: Sat, 19 Jan 2013 19:28:30 +0100	[thread overview]
Message-ID: <20130119182830.GT3604@emdete.de> (raw)
In-Reply-To: <50F9E334.4090901@gmail.com>

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

Hi Denis,

On Fri, Jan 18, 2013 at 06:05:08PM -0600, Denis Kenzior wrote:
> Case in point your patch, which doesn't even contain a code comment block on
> what it is trying to accomplish.

i understood the response of the modem follows the spec so i thought this would
be standard. but you are deeper in the specs and i won't tell otherwise.

> (And by the way your coding style is still wrong in several places...)

i just tried to intuitively follow the code standard i found in ofono, sorry if
i got that wrong.

> So far you are the first to report a modem that behaves in this manner when
> it comes to parameter lists.

yes, because i am probably the first that investigated the problem in depth. i
saw alot of complains that the registration state is not reached from many
ofono users. cause for that is exactly the +CMER answer of those modems.

as the modem in question is used in many thinkpads and other notebooks i assume
that the many people can't use ofono out of this reason.

so what do you suggest to support this modem? how would a quirk as you
suggested look like?


regards,
	michael

-- 
M. Dietrich

  reply	other threads:[~2013-01-19 18:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 20:58 fix for +CMER parser of AT driver (fixes registration) M. Dietrich
2013-01-17  3:28 ` Denis Kenzior
2013-01-18 22:44   ` M. Dietrich
2013-01-19  0:05     ` Denis Kenzior
2013-01-19 18:28       ` M. Dietrich [this message]
2013-01-19 19:05         ` 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=20130119182830.GT3604@emdete.de \
    --to=ofono@emdete.de \
    --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.