| 55 |
to libusb) |
to libusb) |
| 56 |
|
|
| 57 |
|
|
| 58 |
|
Debug informations: |
| 59 |
|
=================== |
| 60 |
|
|
| 61 |
|
The driver uses the debug function provided by pcscd. So if pcscd sends |
| 62 |
|
its debug to stdout (pcscd --foreground) then the CCID will also send |
| 63 |
|
its debug to stdout. If pcscd sends its debug to syslog (by default) |
| 64 |
|
then the CCID will also send its debug to syslog. |
| 65 |
|
|
| 66 |
|
You can change the debug level using the Info.plist configuraion file. |
| 67 |
|
The Info.plist is installed, by default, in |
| 68 |
|
/usr/local/pcsc/drivers/ifd-ccid.bundle/Contents/Info.plist |
| 69 |
|
|
| 70 |
|
The debug level is set in the ifdLogLevel field. It is a binary OR |
| 71 |
|
combinaison of 4 different levels. |
| 72 |
|
- 1: critical: important error messages |
| 73 |
|
- 2: info: informative messages like what reader was detected |
| 74 |
|
- 4: periodic: periodic info when pcscd test if a card is present (every |
| 75 |
|
1/10 of a second) |
| 76 |
|
- 8: comm: a dump of all the bytes exchanged between the host and the |
| 77 |
|
reader |
| 78 |
|
|
| 79 |
|
By default the debug level is set to 3 (1 + 2) and correspond to the |
| 80 |
|
critical and info levels. |
| 81 |
|
|
| 82 |
|
You have to restart the driver so it read the configuration file again |
| 83 |
|
and use the new debug level value. To restart the driver you just need |
| 84 |
|
to unplug all your CCID readers so the the driver is unloaded and then |
| 85 |
|
replug your readers. You can also restart pcscd. |
| 86 |
|
|
| 87 |
|
|
| 88 |
Known problems: |
Known problems: |
| 89 |
=============== |
=============== |
| 90 |
|
|
Parent Directory
| 
Revision Log
| 
Patch