All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 3/4] Bearer documentation
Date: Mon, 10 Jan 2011 16:26:23 -0800	[thread overview]
Message-ID: <1294705583.3873.3.camel@aeonflux> (raw)
In-Reply-To: <201101101834.55049.remi.denis-courmont@nokia.com>

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

Hi Remi,

> > > On Friday 07 January 2011 18:23:25 ext Denis Kenzior, you wrote:
> > >> The other question I have is whether we should report this at the
> > >> context level or at the ConnectionManager level.  Can different contexts
> > >> truly have different bearers?
> > > 
> > > At least for 3G with HS*PA, I believe we can. In my understanding, HSPA
> > > channels are allocated per contexts. Correct me if I'm wrong.
> > 
> > I don't know, to me it would not make sense to allocate different
> > bearers per context, but I'm not an RF engineer.  Do note that at least
> > several vendors provide extension commands that report the global active
> > bearer, not per context.  For instance, see the Ericsson *CPSB command...
> 
> The UI wants to show a single icon for the number of "G's". I would assume 
> that's meant to address this use case. Then you don't need to iterate over all 
> contexts, especially those not allocated through that this particular AT 
> serial port.

I am confused by your answer.

So from what I understand so far it is that with AT modems the bearer
information is a per context information. So the real question is if
this is just an AT command thing of how they defined it or if it can be
really independent.

As Denis said, the vendor commands indicate that it is a global bearer
information. If one context is on HSPA, then others will be as well. So
how does ISI provide this information? Is it globally or per context?

Regards

Marcel



  reply	other threads:[~2011-01-11  0:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 16:02 [PATCH 1/4] Define packet switched bearers =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-07 16:02 ` [PATCH 2/4] Core support for packet switched bearer reporting =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-07 16:25   ` Denis Kenzior
2011-01-10 11:19     ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-10 16:16       ` Denis Kenzior
2011-01-10 11:33     ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-10 16:19       ` Denis Kenzior
2011-01-07 16:02 ` [PATCH 3/4] Bearer documentation =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-07 16:23   ` Denis Kenzior
2011-01-10 11:21     ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-10 16:27       ` Denis Kenzior
2011-01-10 16:34         ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-11  0:26           ` Marcel Holtmann [this message]
2011-01-11  7:53             ` Aki Niemi
2011-01-12 16:40               ` Marcel Holtmann
2011-01-13  8:17                 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-10 12:41     ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-10 16:20       ` Denis Kenzior
2011-01-07 16:02 ` [PATCH 4/4] atmodem: packet switch bearer support =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-07 16:27   ` Denis Kenzior
2011-01-07 16:23 ` [PATCH 1/4] Define packet switched bearers 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=1294705583.3873.3.camel@aeonflux \
    --to=marcel@holtmann.org \
    --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.