From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] Return SIM file access conditions from read_file_info.
Date: Mon, 27 Jul 2009 18:13:09 -0500 [thread overview]
Message-ID: <200907271813.10545.denkenz@gmail.com> (raw)
In-Reply-To: <1248106299-5861-1-git-send-email-andrew.zaborowski@intel.com>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
Hi,
I've pushed this patch with some modifications afterward. From reading the
spec myself, I noticed that our interpretations are a 'bit' different.
According to TS 11.11 9.3:
- Read is in byte 9, upper 4 bits
- Update is in byte 9, lower 4 bits
- Increate is in byte 10, upper 4 bits
- Rehabilitate is in byte 11, upper 4 bits
- Invalidate is in byte 11, lower 4 bits
I've reworked the code according to the above spec.
Yet in your implementation they were in bytes 10-12 with lower & upper
swapped. E.g. Read in byte 10, lower 4 bits.
Can you confirm that my interpretation is correct, or am I missing something?
Regards,
-Denis
next prev parent reply other threads:[~2009-07-27 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 16:11 [PATCH] Return SIM file access conditions from read_file_info Andrzej Zaborowski
2009-07-27 23:13 ` Denis Kenzior [this message]
2009-07-27 23:24 ` Andrzej Zaborowski
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=200907271813.10545.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.