From: Yang Gu <yang.gu@intel.com>
To: ofono@ofono.org
Subject: [PATCH 11/17] Add parser for esn objects
Date: Tue, 20 Apr 2010 14:15:06 +0800 [thread overview]
Message-ID: <1271744112-32285-11-git-send-email-yang.gu@intel.com> (raw)
In-Reply-To: <1271744112-32285-1-git-send-email-yang.gu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
---
src/stkutil.c | 21 +++++++++++++++++++++
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/src/stkutil.c b/src/stkutil.c
index 4863989..db5b8b8 100644
--- a/src/stkutil.c
+++ b/src/stkutil.c
@@ -1414,6 +1414,25 @@ static gboolean parse_dataobj_remote_entity_address(
return TRUE;
}
+/* Defined in TS 102.223 Section 8.69 */
+static gboolean parse_dataobj_esn(
+ struct comprehension_tlv_iter *iter, void *user)
+{
+ unsigned char **esn = user;
+ const unsigned char *data;
+ unsigned int len = comprehension_tlv_iter_get_length(iter);
+
+ if (len != 4)
+ return FALSE;
+
+ data = comprehension_tlv_iter_get_data(iter);
+
+ /* Assume esn is 4 bytes long */
+ memcpy(*esn, data, len);
+
+ return TRUE;
+}
+
/* Defined in TS 102.223 Section 8.72 */
static gboolean parse_dataobj_text_attr(struct comprehension_tlv_iter *iter,
void *user)
@@ -1580,6 +1599,8 @@ static dataobj_handler handler_for_type(enum stk_data_object_type type)
return parse_dataobj_service_availability;
case STK_DATA_OBJECT_TYPE_REMOTE_ENTITY_ADDRESS:
return parse_dataobj_remote_entity_address;
+ case STK_DATA_OBJECT_TYPE_ESN:
+ return parse_dataobj_esn;
case STK_DATA_OBJECT_TYPE_TEXT_ATTRIBUTE:
return parse_dataobj_text_attr;
case STK_DATA_OBJECT_TYPE_FRAME_ID:
--
1.7.0.4
next prev parent reply other threads:[~2010-04-20 6:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 6:14 [PATCH 01/17] Add parser for item text attribute list objects Yang Gu
2010-04-20 6:14 ` [PATCH 02/17] Add parser for aid objects Yang Gu
2010-04-20 22:00 ` Denis Kenzior
2010-04-20 6:14 ` [PATCH 03/17] Add parser for access technology objects Yang Gu
2010-04-20 21:53 ` Denis Kenzior
2010-04-20 6:14 ` [PATCH 04/17] Add parser for display parameters objects Yang Gu
2010-04-20 6:15 ` [PATCH 05/17] Add parser for service record objects Yang Gu
2010-04-20 21:55 ` Denis Kenzior
2010-04-21 5:06 ` Gu, Yang
2010-04-20 6:15 ` [PATCH 06/17] Add parser for device filter objects Yang Gu
2010-04-20 21:56 ` Denis Kenzior
2010-04-20 6:15 ` [PATCH 07/17] Add parser for service search objects Yang Gu
2010-04-20 6:15 ` [PATCH 08/17] Add parser for attribute information objects Yang Gu
2010-04-20 6:15 ` [PATCH 09/17] Add parser for service availability objects Yang Gu
2010-04-20 6:15 ` [PATCH 10/17] Add parser for remote entity address objects Yang Gu
2010-04-20 21:58 ` Denis Kenzior
2010-04-20 6:15 ` Yang Gu [this message]
2010-04-20 6:15 ` [PATCH 12/17] Add parser for network access name objects Yang Gu
2010-04-20 6:15 ` [PATCH 13/17] Add parser for cdma sms tpdu objects Yang Gu
2010-04-20 6:15 ` [PATCH 14/17] Add parser for item text attribute list objects Yang Gu
2010-04-20 6:15 ` [PATCH 15/17] Add parser for imeisv objects Yang Gu
2010-04-20 6:15 ` [PATCH 16/17] Add parser for network search mode objects Yang Gu
2010-04-20 6:15 ` [PATCH 17/17] Add parser for battery state objects Yang Gu
2010-04-20 22:00 ` [PATCH 01/17] Add parser for item text attribute list 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=1271744112-32285-11-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