-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add Broadcom 5880 Smartcard/UPEK Reader #4
base: master
Are you sure you want to change the base?
Conversation
I tested Contact Smart Card Reader 0a5c:5801 according http://natisbad.org/E4300/ and it works! (0a5c:5800 is very similar, according |
Please accept! |
Why do you use OpenCT instead of pcsc-lite and the CCID driver? Note that your reader is listed in the "Unsupported or partly supported CCID readers" list |
Yes, device works with pcsc. |
As you see in http://pcsclite.alioth.debian.org/ccid/unsupported.html#0x0A5C0x5801 its about older CCID release 1.3.12 It works with newer CCID releases as you see in http://pcsclite.alioth.debian.org/ccid/shouldwork.html#0x0A5C0x5800 The same device ID 0a5c:5800 and 0a5c:5801 is common for several devices, the hub may named e.g. "Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor" I.e. the same computer can have two devices – contacted and contactless – reader. But to make contactless reader working, your need to do trick in MS Windows, because only for Windows there is special program to change some device modes: dissable "CV-only" mode and enable CCID compatible mode. see also: |
I will ask again: Why do you use OpenCT instead of pcsc-lite and the CCID driver? What does not work if you remove OpenCT? |
i can confirm the BCM5880 reader works out of the box with CCID driver
|
Broadcom 5880 Smartcard/UPEK Reader 0a5c:5800 and 0a5c:5801
is supported by openct using ccid