| 30 |
- none known |
- none known |
| 31 |
|
|
| 32 |
|
|
| 33 |
|
Supported operating systems: |
| 34 |
|
============================ |
| 35 |
|
|
| 36 |
|
- GNU/Linux (libusb 0.1.7) |
| 37 |
|
- MacOS X/Darwin (libusb 0.1.8beta, CVS snapshot. See "Known problems") |
| 38 |
|
to libusb) |
| 39 |
|
|
| 40 |
|
|
| 41 |
|
Known problems: |
| 42 |
|
=============== |
| 43 |
|
|
| 44 |
|
MacOS X/Darwin |
| 45 |
|
readers enumeration |
| 46 |
|
|
| 47 |
|
You may have wrong reader identification if you two or more reader |
| 48 |
|
at the exact same time. |
| 49 |
|
pcscd and the CCID driver do not list connected readers in the same |
| 50 |
|
order. The driver has no way to know which reader has been |
| 51 |
|
detected as a new reader by pcscd. So if you plug two readers at |
| 52 |
|
the same time (for example if you start pcscd with two readers |
| 53 |
|
connected or if you plug a USB hub with two readers on the hub) |
| 54 |
|
you may have this (with two readers foo and bar): |
| 55 |
|
- pcscd scans the USB bus and finds a new CCID reader foo and calls |
| 56 |
|
the driver |
| 57 |
|
- the CCID driver scan the USB bus and finds a new reader bar |
| 58 |
|
- pcscd continues scanning the USB bus and finds the second reader |
| 59 |
|
bar and calls the driver |
| 60 |
|
- the CCID driver scan the USB bus and finds an unused reader foo. |
| 61 |
|
Now the reader foo will be called bar by pcscd and bar will be |
| 62 |
|
called foo. |
| 63 |
|
We don't have this under Linux or *BSD since the USB bus scanning |
| 64 |
|
method is the same for pcscd and the CCID driver. |
| 65 |
|
One solution would be to use IFDHCreateChannelByName() instead of |
| 66 |
|
IFDHCreateChannel() and specify the USB device to use. |
| 67 |
|
Another solution is to plug readers one after the other and not at |
| 68 |
|
the same time. |
| 69 |
|
|
| 70 |
|
hotplug |
| 71 |
|
|
| 72 |
|
Due to libusb work in progress the driver may crash on a reader |
| 73 |
|
insertion after a few insert/remove actions. |
| 74 |
|
So if your reader is always connected you should not have |
| 75 |
|
problems. |
| 76 |
|
A new version of libusb should fix this bug |
| 77 |
|
|
| 78 |
|
|
| 79 |
Licence: |
Licence: |
| 80 |
======== |
======== |
| 81 |
|
|
Parent Directory
| 
Revision Log
| 
Patch