From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 2/3] atmodem: add a huawei hack to check attachment status
Date: Fri, 23 Apr 2010 10:50:33 -0500 [thread overview]
Message-ID: <201004231050.34095.denkenz@gmail.com> (raw)
In-Reply-To: <87ljcerx6y.fsf@potku.valot.fi>
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
Hi Kalle,
> Marcel Holtmann <marcel@holtmann.org> writes:
> > Hi Kalle,
>
> Hi Marcel,
>
> >> Huawei doesn't seem to send CGREG notifications (or I wasn't able to
> >> properly configure the modem to do it), so add an ugly to hack poll the
> >> state with CGATT.
> >
> > shouldn't be polling AT+CGREG? the better way to do this?
>
> Most probably, I'll try with that command and test how it goes.
>
> But is polling acceptable way to do this? And is there anything else I
> could do except poll? I'm open to all suggestions.
>
These devices are sometimes quite weird, especially if they have multiple
ports. Sometimes unsolicited notifications are not sent to a particular port,
and that port is for control only. This could be the case here...
Regards,
-Denis
next prev parent reply other threads:[~2010-04-23 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 13:40 [PATCH 0/3] Huawei E1552 hacks Kalle Valo
2010-04-23 13:40 ` [PATCH 1/3] atmodem: add signal strength support for huawei Kalle Valo
2010-04-23 14:22 ` Marcel Holtmann
2010-04-23 15:40 ` Kalle Valo
2010-04-23 15:53 ` Denis Kenzior
2010-04-26 10:45 ` Kalle Valo
2010-04-23 13:40 ` [PATCH 2/3] atmodem: add a huawei hack to check attachment status Kalle Valo
2010-04-23 14:24 ` Marcel Holtmann
2010-04-23 15:43 ` Kalle Valo
2010-04-23 15:50 ` Denis Kenzior [this message]
2010-04-26 10:44 ` Kalle Valo
2010-04-23 13:40 ` [PATCH 3/3] huawei: add gprs context Kalle Valo
2010-04-23 14:26 ` Marcel Holtmann
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=201004231050.34095.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox