From: Yang Gu <yang.gu@intel.com>
To: ofono@ofono.org
Subject: [PATCH 01/15] Add parser for access technology objects
Date: Wed, 21 Apr 2010 12:55:45 +0800 [thread overview]
Message-ID: <1271825759-8898-1-git-send-email-yang.gu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
---
src/stkutil.c | 14 ++++++++++++++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/src/stkutil.c b/src/stkutil.c
index 0d4be68..69d5a4a 100644
--- a/src/stkutil.c
+++ b/src/stkutil.c
@@ -1243,6 +1243,18 @@ static gboolean parse_dataobj_aid(struct comprehension_tlv_iter *iter,
return TRUE;
}
+/*
+ * Defined in TS 102.223 Section 8.61. According to it, the technology field
+ * can have at most 127 bytes. However, all the defined values are only 1 byte,
+ * so we just use 1 byte to represent it.
+ */
+static gboolean parse_dataobj_access_technology(
+ struct comprehension_tlv_iter *iter, void *user)
+{
+ unsigned char *byte = user;
+ return parse_dataobj_common_byte(iter, byte);
+}
+
/* Defined in TS 102.223 Section 8.72 */
static gboolean parse_dataobj_text_attr(struct comprehension_tlv_iter *iter,
void *user)
@@ -1393,6 +1405,8 @@ static dataobj_handler handler_for_type(enum stk_data_object_type type)
return parse_dataobj_uicc_te_interface;
case STK_DATA_OBJECT_TYPE_AID:
return parse_dataobj_aid;
+ case STK_DATA_OBJECT_TYPE_ACCESS_TECHNOLOGY:
+ return parse_dataobj_access_technology;
case STK_DATA_OBJECT_TYPE_TEXT_ATTRIBUTE:
return parse_dataobj_text_attr;
case STK_DATA_OBJECT_TYPE_FRAME_ID:
--
1.7.0.4
next reply other threads:[~2010-04-21 4:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 4:55 Yang Gu [this message]
2010-04-21 4:55 ` [PATCH 02/15] Add parser for display parameters objects Yang Gu
2010-04-21 4:55 ` [PATCH 03/15] Add parser for service record objects Yang Gu
2010-04-21 4:55 ` [PATCH 04/15] Add parser for device filter objects Yang Gu
2010-04-21 4:55 ` [PATCH 05/15] Add parser for service search objects Yang Gu
2010-04-21 4:55 ` [PATCH 06/15] Add parser for attribute information objects Yang Gu
2010-04-21 4:55 ` [PATCH 07/15] Add parser for service availability objects Yang Gu
2010-04-21 4:55 ` [PATCH 08/15] Add parser for remote entity address objects Yang Gu
2010-04-21 4:55 ` [PATCH 09/15] Add parser for esn objects Yang Gu
2010-04-21 4:55 ` [PATCH 10/15] Add parser for network access name objects Yang Gu
2010-04-21 4:55 ` [PATCH 11/15] Add parser for cdma sms tpdu objects Yang Gu
2010-04-21 4:55 ` [PATCH 12/15] Add parser for item text attribute list objects Yang Gu
2010-04-21 4:55 ` [PATCH 13/15] Add parser for imeisv objects Yang Gu
2010-04-21 4:55 ` [PATCH 14/15] Add parser for network search mode objects Yang Gu
2010-04-21 4:55 ` [PATCH 15/15] Add parser for battery state objects Yang Gu
2010-04-21 15:34 ` [PATCH 01/15] Add parser for access technology objects 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=1271825759-8898-1-git-send-email-yang.gu@intel.com \
--to=yang.gu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox