Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 5/6] stkutil: Complete the TLV parsing/builder to support BIP commands
Date: Fri, 25 Mar 2011 12:15:31 -0500	[thread overview]
Message-ID: <4D8CCDB3.6040206@gmail.com> (raw)
In-Reply-To: <4D8CC805.30205@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

Hi Philippe,

<snip>

> Indeed the size to be returned in the Terminal response is encoded with
> one byte (reason why you can find an unsigned char in the structures
> stk_response_receive_data and stk_response_send_data).
> I understand also the logic that fills the Data Length structure:
>     stk_tlv_builder_append_byte(tlv, MIN(*length, 255))
> 
> but I really need to store the real number of bytes remaining/available,
> and this number can exceed 255. So, I would like to keep this data type
> or at least go for an unsigned short.
> 
>

Then go with unsigned short for now and I'll try to pay attention as to
why you think you need this on my next review.

> 
> Regarding the modifications I did in the enum section/structures, you
> wrote:
> 
>>Can you do me a favor and add the Section # for the enums / structs
>>you're modifying / introducing where needed.  We were supposed to be
>>doing this but somehow were not consistent enough over time.
> 
> Could you clarify with an example ?

Just have a look at stkutil.h, there are plenty of examples.

e.g.

/*
 * TS 101.220, Section 7.2, Card Application Toolkit assigned templates,
 * These are the same as 3GPP 11.14 Sections 13.1 and 13.2
 */
enum stk_envelope_type {

or

/* TS 102.223 Section 9.4 */
enum stk_command_type {

Regards,
-Denis

      reply	other threads:[~2011-03-25 17:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 12:51 [PATCH 5/6] stkutil: Complete the TLV parsing/builder to support BIP commands Philippe Nunes
2011-03-23 21:26 ` Denis Kenzior
2011-03-24 11:56   ` Philippe Nunes
2011-03-24 14:32     ` Denis Kenzior
2011-03-25 16:51       ` Philippe Nunes
2011-03-25 17:15         ` Denis Kenzior [this message]

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=4D8CCDB3.6040206@gmail.com \
    --to=denkenz@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