From: Yang Gu <yang.gu@intel.com>
To: ofono@ofono.org
Subject: [PATCH 04/11] Add parser for cause objects
Date: Wed, 31 Mar 2010 17:16:56 +0800 [thread overview]
Message-ID: <1270027023-21468-4-git-send-email-yang.gu@intel.com> (raw)
In-Reply-To: <1270027023-21468-3-git-send-email-yang.gu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
---
src/stkutil.c | 25 +++++++++++++++++++++++++
src/stkutil.h | 9 +++++++++
2 files changed, 34 insertions(+), 0 deletions(-)
diff --git a/src/stkutil.c b/src/stkutil.c
index ec64af3..08d013b 100644
--- a/src/stkutil.c
+++ b/src/stkutil.c
@@ -628,6 +628,29 @@ static gboolean parse_dataobj_event_list(
return TRUE;
}
+/* Defined in TS 102.223 Section 8.26 */
+static gboolean parse_dataobj_cause(
+ struct comprehension_tlv_iter *iter, void *user)
+{
+ struct stk_cause *cause = user;
+ const unsigned char *data;
+ unsigned int len = comprehension_tlv_iter_get_length(iter);
+
+ if ((len == 1) || (len > sizeof(cause->cause)))
+ return FALSE;
+
+ cause->has_cause = TRUE;
+
+ if (len == 0)
+ return TRUE;
+
+ data = comprehension_tlv_iter_get_data(iter);
+ cause->len = len;
+ memcpy(cause->cause, data, len);
+
+ return TRUE;
+}
+
/* Defined in TS 102.223 Section 8.31 */
static gboolean parse_dataobj_icon_id(struct comprehension_tlv_iter *iter,
void *user)
@@ -738,6 +761,8 @@ static dataobj_handler handler_for_type(enum stk_data_object_type type)
return parse_dataobj_items_next_action_indicator;
case STK_DATA_OBJECT_TYPE_EVENT_LIST:
return parse_dataobj_event_list;
+ case STK_DATA_OBJECT_TYPE_CAUSE:
+ return parse_dataobj_cause;
case STK_DATA_OBJECT_TYPE_ICON_ID:
return parse_dataobj_icon_id;
case STK_DATA_OBJECT_TYPE_IMMEDIATE_RESPONSE:
diff --git a/src/stkutil.h b/src/stkutil.h
index be89c9b..21f6e8a 100644
--- a/src/stkutil.h
+++ b/src/stkutil.h
@@ -403,6 +403,15 @@ struct stk_event_list {
};
/*
+ * According to 102.223 Section 8.26, the maximum length of cause is 30.
+ */
+struct stk_cause {
+ unsigned char cause[30];
+ unsigned int len;
+ ofono_bool_t has_cause;
+};
+
+/*
* Defined in TS 102.223 Section 8.31
* Icon ID denotes a file on the SIM filesystem. Since EF cannot have record
* ids of 0, we use icon_id with 0 to denote empty icon_identifier objects
--
1.6.3.3
next prev parent reply other threads:[~2010-03-31 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:16 [PATCH 01/11] Adjust the sequence of comprehension tlv structures Yang Gu
2010-03-31 9:16 ` [PATCH 02/11] Add parser for items next action indicator objects Yang Gu
2010-03-31 9:16 ` [PATCH 03/11] Add parser for event list objects Yang Gu
2010-03-31 9:16 ` Yang Gu [this message]
2010-03-31 9:16 ` [PATCH 05/11] Add parser for location status objects Yang Gu
2010-03-31 9:16 ` [PATCH 06/11] Add parser for transaction identifier objects Yang Gu
2010-03-31 9:16 ` [PATCH 07/11] Add parser for call control requested action objects Yang Gu
2010-03-31 9:17 ` [PATCH 08/11] Add enum for icon qualifier Yang Gu
2010-03-31 9:17 ` [PATCH 09/11] Add parser for item icon identifier list objects Yang Gu
2010-03-31 9:17 ` [PATCH 10/11] Rename stk_icon_identifier to stk_icon_id Yang Gu
2010-03-31 9:17 ` [PATCH 11/11] Handle the comprehension tlv with bad format in parse_dataobj() Yang Gu
2010-03-31 17:25 ` [PATCH 01/11] Adjust the sequence of comprehension tlv structures 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=1270027023-21468-4-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