From: Yang Gu <gyagp0@gmail.com>
To: ofono@ofono.org
Subject: [PATCH 13/13] Add parser for broadcast network information objects
Date: Thu, 22 Apr 2010 23:12:30 +0800 [thread overview]
Message-ID: <1271949150-9085-13-git-send-email-yang.gu@intel.com> (raw)
In-Reply-To: <1271949150-9085-1-git-send-email-yang.gu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2547 bytes --]
---
src/stkutil.c | 25 +++++++++++++++++++++++++
src/stkutil.h | 19 +++++++++++++++++++
2 files changed, 44 insertions(+), 0 deletions(-)
diff --git a/src/stkutil.c b/src/stkutil.c
index 75b0035..a457e36 100644
--- a/src/stkutil.c
+++ b/src/stkutil.c
@@ -1803,6 +1803,29 @@ static gboolean parse_dataobj_activate_descriptor(
return TRUE;
}
+/* Defined in TS 102.223 Section 8.90 */
+static gboolean parse_dataobj_broadcast_network_info(
+ struct comprehension_tlv_iter *iter, void *user)
+{
+ struct stk_broadcast_network_information *bni = user;
+ const unsigned char *data;
+ unsigned int len = comprehension_tlv_iter_get_length(iter);
+
+ if (len < 2)
+ return FALSE;
+
+ data = comprehension_tlv_iter_get_data(iter);
+
+ if (data[0] > 0x03)
+ return FALSE;
+
+ bni->tech = data[0];
+ bni->len = len - 1;
+ memcpy(bni->loc_info, data + 1, bni->len);
+
+ return TRUE;
+}
+
static dataobj_handler handler_for_type(enum stk_data_object_type type)
{
switch (type) {
@@ -1970,6 +1993,8 @@ static dataobj_handler handler_for_type(enum stk_data_object_type type)
return parse_dataobj_registry_application_data;
case STK_DATA_OBJECT_TYPE_ACTIVATE_DESCRIPTOR:
return parse_dataobj_activate_descriptor;
+ case STK_DATA_OBJECT_TYPE_BROADCAST_NETWORK_INFO:
+ return parse_dataobj_broadcast_network_info;
default:
return NULL;
};
diff --git a/src/stkutil.h b/src/stkutil.h
index b7341c7..5d2a818 100644
--- a/src/stkutil.h
+++ b/src/stkutil.h
@@ -370,6 +370,13 @@ enum stk_frame_layout_type {
STK_LAYOUT_VERTICAL = 0x02
};
+enum stk_broadcast_network_technology {
+ STK_BROADCAST_NETWORK_DVB_H = 0x00,
+ STK_BROADCAST_NETWORK_DVB_T = 0x01,
+ STK_BROADCAST_NETWORK_DVB_SH = 0x02,
+ STK_BROADCAST_NETWORK_T_DMB = 0x03
+};
+
/* For data object that only has a byte array with undetermined length */
struct stk_common_byte_array {
unsigned char *array;
@@ -764,6 +771,18 @@ struct stk_registry_application_data {
char *name;
};
+/*
+ * According to 102.223 Section 8.90 the length of CTLV is 1 byte. This means
+ * that the maximum length is 127 bytes for the total length of broadcast
+ * network technology and location information. Thus the maximum length of
+ * location information is 126 bytes.
+ */
+struct stk_broadcast_network_information {
+ unsigned char tech;
+ unsigned char loc_info[126];
+ unsigned int len;
+};
+
struct stk_command_display_text {
char *text;
struct stk_icon_id icon_id;
--
1.7.0.4
next prev parent reply other threads:[~2010-04-22 15:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 15:12 [PATCH 01/13] Add parser for browsing status objects Yang Gu
2010-04-22 15:12 ` [PATCH 02/13] Add parser for frame layout objects Yang Gu
2010-04-22 15:12 ` [PATCH 03/13] Add parser for frames information objects Yang Gu
2010-04-22 15:12 ` [PATCH 04/13] Add parser for meid objects Yang Gu
2010-04-22 15:12 ` [PATCH 05/13] Add parser for multimedia message reference objects Yang Gu
2010-04-22 15:12 ` [PATCH 06/13] Add parser for multimedia message identifier objects Yang Gu
2010-04-22 15:12 ` [PATCH 07/13] Add parser for multimedia message transfer status objects Yang Gu
2010-04-22 15:12 ` [PATCH 08/13] Add parser for mm content identifier objects Yang Gu
2010-04-22 15:12 ` [PATCH 09/13] Add parser for multimedia message notification objects Yang Gu
2010-04-22 15:12 ` [PATCH 10/13] Add parser for last envelope objects Yang Gu
2010-04-22 15:12 ` [PATCH 11/13] Add parser for registry application data objects Yang Gu
2010-04-22 15:12 ` [PATCH 12/13] Add parser for activate descriptor objects Yang Gu
2010-04-22 15:12 ` Yang Gu [this message]
2010-04-23 16:54 ` [PATCH 01/13] Add parser for browsing status 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=1271949150-9085-13-git-send-email-yang.gu@intel.com \
--to=gyagp0@gmail.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