From: Reinhard Speyerer <rspmn@arcor.de>
To: ofono@ofono.org
Subject: Re: [PATCH 6/8] gprs-context : Force use of atd99
Date: Mon, 18 Feb 2019 17:42:04 +0100 [thread overview]
Message-ID: <20190218164204.GA8209@arcor.de> (raw)
In-Reply-To: <b1c57503-11b3-4eab-56c8-eb94fa475df8@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
On Sun, Feb 17, 2019 at 09:08:12PM -0600, Denis Kenzior wrote:
> Hi Philippe,
>
> On 02/15/2019 06:11 AM, philippedeswert(a)gmail.com wrote:
> > From: Philippe De Swert <philippe.deswert@digitalistgroup.com>
> >
> > QUIRCK: For some reason I really need to force the use of the atd99 command here.
> > ---
> > drivers/atmodem/gprs-context.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/atmodem/gprs-context.c b/drivers/atmodem/gprs-context.c
> > index 93894efd..a0776f2a 100644
> > --- a/drivers/atmodem/gprs-context.c
> > +++ b/drivers/atmodem/gprs-context.c
> > @@ -214,7 +214,7 @@ static void at_cgdcont_cb(gboolean ok, GAtResult *result, gpointer user_data)
> > return;
> > }
> > - if (gcd->use_atd99)
> > + if (gcd->use_atd99 || gcd->vendor == OFONO_VENDOR_UBLOX)
> > sprintf(buf, "ATD*99***%u#", gcd->active_context);
> > else
> > sprintf(buf, "AT+CGDATA=\"PPP\",%u", gcd->active_context);
> > @@ -457,6 +457,9 @@ static int at_gprs_context_probe(struct ofono_gprs_context *gc,
> > case OFONO_VENDOR_SIMCOM_SIM900:
> > gcd->use_atd99 = FALSE;
> > break;
> > + case OFONO_VENDOR_UBLOX:
> > + gcd->use_atd99 = TRUE;
> > + break;
>
> So why use both use_atd99 and a vendor quirk above? Also, you're affecting
> other uBlox users, so do you want to introduce a different VENDOR quirk
> instead?
Hi Denis,
the effect observed by Philippe is caused by the fact that Qualcomm
firmwares typically do not support the use of AT+CGDATA="PPP",<cid>
for contexts which have already been activated with AT+CGACT although
they respond with +CGDATA: ("PPP") to AT+CGDATA=?.
To minimize changes for other uBlox users it might make sense to limit
the use of ATD*99# to Qualcomm-based devices like their SARA R4 series.
Regards,
Reinhard
next prev parent reply other threads:[~2019-02-18 16:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 12:11 [PATCH 0/8] [RFC] Support for serial u-blox NB-IoT modems philippedeswert
2019-02-15 12:11 ` [PATCH 1/8] ublox-serial: add new plugin for u-blox philippedeswert
2019-02-16 12:25 ` Jonas Bonn
2019-02-16 13:55 ` Philippe De Swert
2019-02-17 14:46 ` Jonas Bonn
2019-02-17 15:08 ` Jonas Bonn
2019-02-15 12:11 ` [PATCH 2/8] Makefile.am : include new u-blox serial modem driver philippedeswert
2019-02-15 12:11 ` [PATCH 3/8] gprs.h: Add ofono_gprs_get_netreg function philippedeswert
2019-02-15 12:11 ` [PATCH 4/8] gprs.c: " philippedeswert
2019-02-15 12:11 ` [PATCH 5/8] atmodem/gprs.c: Add CEREG support philippedeswert
2019-02-18 4:04 ` Denis Kenzior
2019-02-15 12:11 ` [PATCH 6/8] gprs-context : Force use of atd99 philippedeswert
2019-02-18 3:08 ` Denis Kenzior
2019-02-18 16:42 ` Reinhard Speyerer [this message]
2019-03-13 8:19 ` Jonas Bonn
2019-03-13 13:00 ` Reinhard Speyerer
2019-03-15 12:37 ` Philippe De Swert
2019-02-15 12:11 ` [PATCH 7/8] common: Add new NB-IoT technologies philippedeswert
2019-02-18 3:19 ` Denis Kenzior
2019-02-15 12:11 ` [PATCH 8/8] Fix gprs_netreg_update behaviour if PPP connection active philippedeswert
2019-02-18 4:00 ` 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=20190218164204.GA8209@arcor.de \
--to=rspmn@arcor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox