Hi, I'm not a smart card driver expert, but if you do require communication between the kernel and the user space, then a device node plus file operations is a reasonable requirement :-) . The user space library will be a wrapper for the kernel module.
ccid commonly uses libusb, this is why it does not need any specific kernel module. the kernel interface is in this lib. Regards Sebastien On Wed, Dec 23, 2009 at 8:23 PM, Feng Ye <[email protected]> wrote: > Hello there, > > We are developing smart card driver for our SoC, which has cpu and smart > card interface. > The drivers on the muscle website are either for serial or usb external > readers, while ours are directly connected. > We would like to put the IFD handler on user space and smart card driver on > kernel space. We couldn't find a sample driver architected like this. > Looks like we need to define our own device (like /dev/smartcarad) and our > own IOCTL (for communicating between IFD handler and the smart cacrd > driver)? > > Thanks, > Feng > > > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.drizzle.com/mailman/listinfo/muscle > >
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
