Andrey Jivsov wrote: > Looks like cyberjack_activate() fails on the first cyberjack_recv_t1. > > I would try to increase/decrease the value in ifd_msleep( 100 ) before > cyberjack_recv_t1 to see if this makes the difference. I will try to > reproduce it this week.
Yes. I wonder what I/O error means in libusb terms. > If you look at the source code of ifd/ifd-cyberjack.c, you are long way > along the path to make it work, once you are done with initialization. > Why not enhance the version in SVN, which already works, with more > reliable initialization sequence that you developed? Thank you. The problem is that FreeBSD kernel does everything that libusb provides (and even more) for you. I don't need to worry about almost anything, just write the code writing and reading from pipes. This is a kernel module source which successfully initializes (and does nothing more): http://akson.sgh.waw.pl/~saper/FreeBSD/smartcard/ucyberjack.c I don't have to use timeouts or sleeps to have this working. It is actually a very clean code with no quirks. I will try to have a look at SVN in a while as well. I have one questions related to cyberjack implementation: Do we need to rollout another t=1 implementation to deal with cyberjack? couldn't something existing like proto-t1.c be easily attached? How does cyberjack implement other protocols? Or should I just use T=1 to send reader-specific commands? How do I switch to, say, T=0? -- << Marcin Cieslak // [EMAIL PROTECTED] >> _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
