All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giacinto Cifelli <gciofono@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH v7 6/7] gemalto/lte: Gemalto vendor lte atom
Date: Sat, 20 Oct 2018 18:24:45 +0200	[thread overview]
Message-ID: <CAKSBH7GBW5BpWXqui2W3=qv5t2gfYhq8-4OUo0uaBq6m3K0ifg@mail.gmail.com> (raw)
In-Reply-To: <ec6a85f6-f138-f3d3-6171-3237a59e2900@gmail.com>

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

Hi Denis,
>
> I still don't get this explanation.  You have a gemalto specific
> function, which is being passed the CID directly by the caller.  Why is
> there weird logic here to mess with the CID, just have the caller pass
> in the proper CID directly.
>
> Also note that cid 1 and 3 are by default valid CIDs for context
> activations.  So your 'default attach' profile can be overridden by the
> core at any time.  So you may want to address this by setting the cid
> range appropriately.

The function is to be called also from gprs-context, therefore passing
0 it knows it has to check whether it has to use 1 or 3 or something
else.
The cid-ranges are set in the plugin, also because I cannot use
AT+CGDCONT=? with all models.
There are some that return an answer to this command like (1-16),
which is ok, but then we have some that return (1,2,3,4,5,6), and
still other (1-10,17)...

>
> Regards,
> -Denis

Regards,
Giacinto

  reply	other threads:[~2018-10-20 16:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 18:49 [PATCH v7 0/7] lte atom auth and IP protocol Giacinto Cifelli
2018-10-18 18:49 ` [PATCH v7 1/7] lte-api: protocol and authentication properties Giacinto Cifelli
2018-10-18 18:49 ` [PATCH v7 2/7] lte.h: added proto and authentication handling Giacinto Cifelli
2018-10-18 18:49 ` [PATCH v7 3/7] lte: protocol and authentication for default ctx Giacinto Cifelli
2018-10-18 18:49 ` [PATCH v7 4/7] atmodem/atutil: shared functions for cgdcont Giacinto Cifelli
2018-10-18 18:49 ` [PATCH v7 5/7] atmodem/lte: proto and authentication handling Giacinto Cifelli
2018-10-18 18:49 ` [PATCH v7 6/7] gemalto/lte: Gemalto vendor lte atom Giacinto Cifelli
2018-10-18 19:32   ` Jonas Bonn
2018-10-18 22:59     ` Slava Monich
2018-10-19  3:21     ` Giacinto Cifelli
2018-10-19  6:04       ` Jonas Bonn
2018-10-20 16:18       ` Denis Kenzior
2018-10-20 16:24         ` Giacinto Cifelli [this message]
2018-10-20 16:27           ` Denis Kenzior
2018-10-20 16:29             ` Giacinto Cifelli
2018-10-20 16:13     ` Denis Kenzior
2018-10-18 18:49 ` [PATCH v7 7/7] plugins/gemalto: use Gemalto " Giacinto Cifelli
2018-10-18 19:41   ` Jonas Bonn
2018-10-19  3:09     ` Giacinto Cifelli
2018-10-19  5:57       ` Jonas Bonn
2018-10-19  6:04         ` Giacinto Cifelli

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='CAKSBH7GBW5BpWXqui2W3=qv5t2gfYhq8-4OUo0uaBq6m3K0ifg@mail.gmail.com' \
    --to=gciofono@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.