From: Yang Gu <yang.gu@intel.com>
To: ofono@ofono.org
Subject: [PATCH 01/11] Adjust the sequence of comprehension tlv structures
Date: Wed, 31 Mar 2010 17:16:53 +0800 [thread overview]
Message-ID: <1270027023-21468-1-git-send-email-yang.gu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2159 bytes --]
---
src/stkutil.h | 35 ++++++++++++++++++-----------------
1 files changed, 18 insertions(+), 17 deletions(-)
diff --git a/src/stkutil.h b/src/stkutil.h
index a9495de..b0b09df 100644
--- a/src/stkutil.h
+++ b/src/stkutil.h
@@ -308,15 +308,6 @@ struct stk_ccp {
};
/*
- * 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
- */
-struct stk_icon_identifier {
- unsigned char qualifier;
- unsigned char id;
-};
-
-/*
* According to 102.223 Section 8.8 interval values of 0x00 are reserved.
* We use this to denote empty duration objects.
*/
@@ -347,6 +338,17 @@ struct stk_result {
unsigned char *additional;
};
+/* Define the struct of single file in TS102.223 Section 8.18.
+ * According to TS 11.11 Section 6.2, each file id has two bytes, and the
+ * maximum Dedicated File level is 2. So the maximum size of file is 8, which
+ * contains two bytes of Master File, 2 bytes of 1st level Dedicated File,
+ * 2 bytes of 2nd level Dedicated File and 2 bytes of Elementary File.
+ */
+struct stk_file {
+ unsigned char file[8];
+ unsigned int len;
+};
+
/* Defined in TS 102.223 Section 8.19 */
struct stk_location_info {
char mnc[OFONO_MAX_MNC_LENGTH + 1];
@@ -358,15 +360,14 @@ struct stk_location_info {
unsigned short ext_ci;
};
-/* Define the struct of single file in TS102.223 Section 8.18.
- * According to TS 11.11 Section 6.2, each file id has two bytes, and the
- * maximum Dedicated File level is 2. So the maximum size of file is 8, which
- * contains two bytes of Master File, 2 bytes of 1st level Dedicated File,
- * 2 bytes of 2nd level Dedicated File and 2 bytes of Elementary File.
+/*
+ * 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
*/
-struct stk_file {
- unsigned char file[8];
- unsigned int len;
+struct stk_icon_identifier {
+ unsigned char qualifier;
+ unsigned char id;
};
/*
--
1.6.3.3
next 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 Yang Gu [this message]
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 ` [PATCH 04/11] Add parser for cause objects Yang Gu
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-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