From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [RFC 1/1] doc: Add modem technology type property
Date: Thu, 20 Jan 2011 23:05:49 +0100 [thread overview]
Message-ID: <1295561149.3873.302.camel@aeonflux> (raw)
In-Reply-To: <4D38B172.2040600@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
Hi Dara,
> >> doc/modem-api.txt | 11 +++++++++++
> >> 1 files changed, 11 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/doc/modem-api.txt b/doc/modem-api.txt
> >> index 45043b0..fe03833 100644
> >> --- a/doc/modem-api.txt
> >> +++ b/doc/modem-api.txt
> >> @@ -82,6 +82,17 @@ Properties boolean Powered [readwrite]
> >>
> >> This is usually obtained by using the +CGSN AT command.
> >>
> >> + string TechnologyType [readonly, optional, experimental]
> >> +
> >> + String representing the technology type of the current
> >> + modem device.
> >> +
> >> + The possible values are:
> >> + "gsm" The 3GPP family of technologies
> >> + including gsm, edge, umts, hspa, lte.
> >> + "cdma" The 3GPP2 family of technologies
> >> + including cdma 1x, evdo.
> >
> > I would just call this property "Type" and then we can also have a value
> > for "hfp" in case it is a Bluetooth HFP modem.
> >
> Thanks - sounds good to me. I'll prepare a patch to reflect this for
> gsm/cdma types and assume the hfp type extension is future work.
not really. Actually HFP support is part of oFono already.
Regards
Marcel
next prev parent reply other threads:[~2011-01-20 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 21:08 [RFC 1/1] doc: Add modem technology type property Dara Spieker-Doyle
2011-01-20 21:34 ` Marcel Holtmann
2011-01-20 22:04 ` Dara Spieker-Doyle
2011-01-20 22:05 ` Marcel Holtmann [this message]
2011-01-20 22:17 ` Dara Spieker-Doyle
2011-01-20 22:22 ` 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=1295561149.3873.302.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.