From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH v2 3/3] gprs: Quectel EC21 does not understand AT+CPSB
Date: Wed, 12 Aug 2020 09:44:09 -0500 [thread overview]
Message-ID: <e637090b-8a4d-e5ef-028c-35052ec36f9b@gmail.com> (raw)
In-Reply-To: <20200812092057.w2h2oqc476x3cmxi@lem-wkst-02.lemonage>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
Hi Lars,
>> oFono driver interface is based on 27.007. So that means values defined in
>> 27.007 do not need to be 'converted'. You can simply feed them in directly
>> if they follow 27.007.
>
> Well, yes. I saw this. But unfortunately at this point what is expected
> are the 27.007 values from AT+CPSB defined in 7.29 (that EC21 quectel
> modem does not support) and I get the values from AT+CGREG defined in 7.2.
>
Ok, I gotcha. I see now what you're trying to do.
The problem is that +CGREG is not really the same as +CPSB. +CGREG only reports
the capability of the cell, not the actual bearer being used. This could be for
example due to signal strength being too low, etc.
If you look at the gprs driver, we never use +CGREG info this way and many
modems have a vendor-specific unsolicited notification if +CPSB isn't supported.
Since the Bearer is an optional property, maybe its just easier to omit it.
Unless you know +CGREG information is the same as +CPSB on Quectel firmware...
Regards,
-Denis
next prev parent reply other threads:[~2020-08-12 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 11:42 [PATCH v2 1/3] Add a vendor OFONO_VENDOR_QUECTEL_EC2X poeschel
2020-08-11 11:42 ` [PATCH v2 2/3] atmodem: Get strength and tech the quectel way on EC21 poeschel
2020-08-11 11:42 ` [PATCH v2 3/3] gprs: Quectel EC21 does not understand AT+CPSB poeschel
2020-08-11 15:55 ` Denis Kenzior
2020-08-12 9:20 ` Lars Poeschel
2020-08-12 14:44 ` Denis Kenzior [this message]
2020-08-11 15:51 ` [PATCH v2 1/3] Add a vendor OFONO_VENDOR_QUECTEL_EC2X 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=e637090b-8a4d-e5ef-028c-35052ec36f9b@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