diff options
| author | Jason Andryuk <jandryuk@gmail.com> | 2018-04-20 14:32:19 -0400 |
|---|---|---|
| committer | Gerd Hoffmann <kraxel@redhat.com> | 2018-04-27 10:28:20 +0200 |
| commit | 0ee86bb6c5beb6498488850104f7557c376d0bef (patch) | |
| tree | b0991b927adea23feb0c8ee340887d733acb60d1 /hw/usb/host-libusb.c | |
| parent | b8846a4d6352b2a1d2012f8b3b9115640524aeda (diff) | |
| download | qemu-0ee86bb6c5beb6498488850104f7557c376d0bef.zip qemu-0ee86bb6c5beb6498488850104f7557c376d0bef.tar.gz qemu-0ee86bb6c5beb6498488850104f7557c376d0bef.tar.bz2 | |
ccid: Fix dwProtocols advertisement of T=0
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.
Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
Message-id: 20180420183219.20722-1-jandryuk@gmail.com
Cc: qemu-stable@nongnu.org
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'hw/usb/host-libusb.c')
0 files changed, 0 insertions, 0 deletions