|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: [Muscle] pcscd (CCID) depends on /proc/bus/usb/???
From: Ludovic Rousseau (ludovic.rousseau
gmail.com)
Date: Thu Dec 07 2006 - 15:00:58 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2006/12/7, Todd Denniston <Todd.Denniston
ssa.crane.navy.mil>:
> have you looked at the inotify[1] infrastructure?
Not really. I was thinking about using inotify to avoid polling in the
pcscd/libpcsclite communication.
I don't know if inotify can be configured to check only USB devices
with InterfaceClass equal to 11 (CCID device) like it is possible with
udev with:
# generic CCID device
BUS=="usb", SYSFS{bInterfaceClass}=="0b", ACTION=="add",
RUN+="/usr/sbin/pcscd --hotplug"
> granted that may mean one more dependency that pcscd has, but at least it
> seems small now.
pcscd does not depends on udev. You can trigger a rescan in pcscd
using udev or inotify or any other mechanism that can call
"/usr/sbin/pcscd --hotplug" when a reader is plugged/unplugged.
The problem with udev is that the action happens too early. One
solution (used by OpenCT) is to sleep(1) in pcscd but I really don't
like this.
Regards,
--
Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
Muscle
lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]