From: Jeremy White <jwhite@codeweavers.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Retrieve the correct TD byte when checking an ATR.
Date: Mon, 19 Jan 2015 10:24:59 -0600 [thread overview]
Message-ID: <54BD2FDB.5050109@codeweavers.com> (raw)
In-Reply-To: <CAJ+F1CJs+Fu7N4VJTjbXz21fMTtMwTJFdH=7g0uuJGHAs+qVPg@mail.gmail.com>
>> The '40' should have been the second TD; instead
>> the FF is used, incorrectly.
>
> The second TD? There is only one here, T0 = 0x95 & 0xf0 >> 4 = b1001
Yes, sorry, I should not have capitalized TD in my comment. The code
uses the variable 'td' to hold the upper 4 bits of T0, and then, if
present, the upper 4 bits of TD1. So what is read imprecisely is the
upper 4 bits of TD1.
I don't know qemu patch protocol; that seems like a very minor detail in
the comment; does it justify a resubmit?
>
>>
>> Signed-off-by: Jeremy White <jwhite@codeweavers.com>
>> ---
>> hw/usb/ccid-card-passthru.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/hw/usb/ccid-card-passthru.c b/hw/usb/ccid-card-passthru.c
>> index 10f1d30..2ae3b81 100644
>> --- a/hw/usb/ccid-card-passthru.c
>> +++ b/hw/usb/ccid-card-passthru.c
>> @@ -168,8 +168,8 @@ static int check_atr(PassthruState *card, uint8_t *data, int len)
>> opt_bytes++;
>> }
>> if (td & 0x8) {
>> - opt_bytes++;
>> td = data[opt_bytes + 2] >> 4;
>> + opt_bytes++;
>> }
>> }
>> if (len < 2 + historical_length + opt_bytes) {
>> --
>> 1.7.10.4
>>
>>
>
> That looks correct, opt_bytes before incrementing points to the current TD.
>
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>
prev parent reply other threads:[~2015-01-19 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 14:57 [Qemu-devel] [PATCH] Retrieve the correct TD byte when checking an ATR Jeremy White
2015-01-19 16:11 ` Marc-André Lureau
2015-01-19 16:24 ` Jeremy White [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=54BD2FDB.5050109@codeweavers.com \
--to=jwhite@codeweavers.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.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.