From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 7/8] Add AT driver for STK atom.
Date: Tue, 20 Apr 2010 15:55:33 -0500 [thread overview]
Message-ID: <201004201555.33596.denkenz@gmail.com> (raw)
In-Reply-To: <l2tfb249edb1004201348re351d92bre2347973abd7d9c3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
Hi Andrew,
> > So I re-read that part of the spec, and I can see why we might want it.
> > However, this quote seemed rather interesting: "Le set to '00' indicates
> > that the terminal expects to receive at most the maximum number of bytes,
> > i.e. 256, in the response ADPU. The UICC may return any number of bytes
> > in the range 1 to 256."
> >
> > Shouldn't that 'FF' be changed to '00'? Also, you might want to include
> > the relevant passage or Spec/Section reference in this code so we don't
> > wonder where it came from in the future.
>
> Attached patch adds a comment and changes the FF to 00. I guess it is
> largely theoretical right now. The issue again with "any number of
> bytes in the range 1 to 256" is that this prohibits an empty response,
> which we want to allow too :) Maybe this should be a parameter of
> driver->envelope()
"The maximum number of bytes expected in the data part of the response APDU is
presented in the parameter Le, which is optional. This means that if the
terminal does not expect any data in the response APDU Le is absent from the
command"
The question really becomes, do we actually want a response and know what to
do with it?
Regards,
-Denis
next prev parent reply other threads:[~2010-04-20 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 6:50 [PATCH 7/8] Add AT driver for STK atom Andrzej Zaborowski
2010-04-15 21:48 ` Denis Kenzior
2010-04-20 19:33 ` Andrzej Zaborowski
2010-04-20 20:21 ` Denis Kenzior
2010-04-20 20:48 ` Andrzej Zaborowski
2010-04-20 20:55 ` Denis Kenzior [this message]
2010-04-20 21:03 ` andrzej zaborowski
2010-04-20 21:32 ` 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=201004201555.33596.denkenz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.