From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5974812125792153840==" MIME-Version: 1.0 From: Marcel Holtmann Subject: Re: [RFC 1/1] doc: Add modem technology type property Date: Thu, 20 Jan 2011 23:05:49 +0100 Message-ID: <1295561149.3873.302.camel@aeonflux> In-Reply-To: <4D38B172.2040600@nokia.com> List-Id: To: ofono@ofono.org --===============5974812125792153840== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 --===============5974812125792153840==--