qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: alevy@redhat.com, qemu-stable@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ccid: Fix dwProtocols advertisement of T=0
Date: Fri, 27 Apr 2018 09:46:31 +0200	[thread overview]
Message-ID: <20180427074631.3l6f3hghcuni6lpd@sirius.home.kraxel.org> (raw)
In-Reply-To: <20180420183219.20722-1-jandryuk@gmail.com>

On Fri, Apr 20, 2018 at 02:32:19PM -0400, Jason Andryuk wrote:
> Commit d7d218ef02d87c637d20d64da8f575d434ff6f78 attempted to change
> dwProtocols to only advertise support for T=0 and not T=1.  The change
> was incorrect as it changed 0x00000003 to 0x00010000.
> 
> lsusb -v in a linux guest shows:
> "dwProtocols         65536  (Invalid values detected)", though the
> smart card could still be accessed.  Windows 7 does not detect inserted
> smart cards and logs the the following Error in the Event Logs:
> 
>     Source: Smart Card Service
>     Event ID: 610
>     Smart Card Reader 'QEMU QEMU USB CCID 0' rejected IOCTL SET_PROTOCOL:
>     Incorrect function. If this error persists, your smart card or reader
>     may not be functioning correctly
> 
>     Command Header: 03 00 00 00
> 
> Setting to 0x00000001 fixes the Windows issue.

Added to usb queue.

thanks,
  Gerd

      reply	other threads:[~2018-04-27  7:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 18:32 [Qemu-devel] [PATCH] ccid: Fix dwProtocols advertisement of T=0 Jason Andryuk
2018-04-27  7:46 ` Gerd Hoffmann [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=20180427074631.3l6f3hghcuni6lpd@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=alevy@redhat.com \
    --cc=jandryuk@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).