A team in Ukraine built a custom Windows control for me, earlier in the year.
For any USB reader connecting via its IFD to the windows PC/SC provider, the
control receives PC/SC realtime events that respond to bus
insertion/removal/suspend (of the reader, not the card), using Microsoft's
then-latest CCID driver stack over window-standard USB controller drivers . It
was not an easy task to accomplish, apparently. I think this goal set should be
established, for pc/sc-lite equivalent .
> Date: Thu, 7 Dec 2006 23:52:10 +0100> From: [EMAIL PROTECTED]> To:
> [email protected]> Subject: Re: [Muscle] pcscd (CCID) depends on
> /proc/bus/usb/???> > with openct I'm using udev to detect new devices.> works
> fine so far. but the scripts in openct get> called twice, for /dev/bus/usb
> and /proc/bus/usb> so two ifdhandler processes are started. but that> is ok,
> only on of them can claim the interface to> the smart card reader, and the
> other one fails.> > maybe something like that could work for pcsc and ccid>
> too? If I can be of any help, please let me know.> > Regards, Andreas>
> _______________________________________________> Muscle mailing list>
> [email protected]> http://lists.drizzle.com/mailman/listinfo/muscle
_________________________________________________________________
Use Messenger to talk to your IM friends, even those on Yahoo!
http://ideas.live.com/programpage.aspx?versionId=7adb59de-a857-45ba-81cc-685ee3e858fe
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
