All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [ofono] vendor code
Date: Tue, 30 Nov 2010 06:22:29 -0600	[thread overview]
Message-ID: <4CF4EC85.9050003@gmail.com> (raw)
In-Reply-To: <AANLkTimcBqdNK=ZLnc=8nReMujJDxc5UfmRKMiOU4A6m@mail.gmail.com>

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

Hi Tonny,

On 11/30/2010 04:45 AM, Tonny Tzeng wrote:
> Hi List,
> 
> While debugging a connection issue using huawei EM770W modem, I added
> a DBG code to print out the status value received in at_cgreg_cb() in
> drivers/atmodem/gprs.c, I found the status got from the
> at_util_parse_reg() is incorrect sometimes, because ofono does not set
> vendor ID in the gprs_data, and it looks to me the vendor code is
> required so that the at_util_parse_reg() will read unquoted strings in
> the solicited events for huawei modem.  For example, when we got
> "+CGREG: 1, 2833, 1231B60" followed by "+CGREG: 2,1, 2733, 1B60"
> unsolicited codes, the status parsed from this code is 2833 (i.e. the
> 1st code), instead of the expected 1 in the 2nd code.
> 

I suggest you complain to the vendor that they do not follow standards,
and ask them to fix their firmware.

> It looks like all modem plugins invoke ofono_gprs_context_create()
> with vendor=0, is this on purpose?  then how could at_util_parse_reg()
> parses strings correctly without knowing vendor code?

This can be added to the huawei driver, however this won't help you
completely as the firmware still reports bizarre values.  Care to send a
patch?

Regards,
-Denis

  reply	other threads:[~2010-11-30 12:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 10:45 [ofono] vendor code Tonny Tzeng
2010-11-30 12:22 ` Denis Kenzior [this message]
2010-12-01  2:15   ` Tonny Tzeng
2010-12-01 17:52     ` Pekka Pessi

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=4CF4EC85.9050003@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.