10-29-2008
Good Luck
You're not likely to find an implementation of a driver for quite some time...It's a standard, but not an open standard. You can't get a legal copy of it if you're a competitor to existing AIA members, and some of them have libraries; a driver would need to come from a vendor or would require reverse engineering.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Does anyone know the /etc/system entries to hard code the GigE interface too 1000 full duplex? (1 Reply)
Discussion started by: 98_1LE
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am trying to install Gandalf, a computer vision and numerical library (http://gandalf-library.sourceforge.net/). I am using Cygwin on a Windows machine and have tried everything to get this to build, but to no avail.
Gcc, make, and libtool are all included in my Cygwin install. I... (1 Reply)
Discussion started by: justinh
1 Replies
3. UNIX for Dummies Questions & Answers
Someone check my code and tell me why there's no output?
I've been coding for 10 hours and I can't tell.
I've stripped every command, and broken it down to just an echo.
for FILENAME in `cat ${TMP_PATH}fxsol_ls.txt`
do
echo $FILENAME
done (6 Replies)
Discussion started by: yongho
6 Replies
4. UNIX for Dummies Questions & Answers
is there any system call in linux which maps to taskSpawn ( ) in VxWorks RTOS (1 Reply)
Discussion started by: Agnello
1 Replies
5. Solaris
I've been researching minimizeing Solaris 8 and found that on the web page http://www.sun.com/bigadmin/content/packagelist/s8u7PkgList/p2.html the package SUNWglmr
is listed as "rasctrl environment monitoring driver for i2c, (Root) (32-bit)" while in the document "Solaris 8 minimize-updt1.pdf"... (1 Reply)
Discussion started by: roygoodwin
1 Replies
6. UNIX for Dummies Questions & Answers
Help, suspect hacked via serial or electric! any ideas on error "Pid:1, comm:swapper Tainted:G W 2.6.35-22 generic #33 -unbutu device = "(null)" or unknown-blocklist(8.1) please append a correct "root"boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd. Thanks... (3 Replies)
Discussion started by: kryclear
3 Replies
7. Hardware
In general terms what are the differences platform driver,codec driver and Machine driver? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
CMX(4) BSD Kernel Interfaces Manual CMX(4)
NAME
cmx -- Omnikey CardMan 4040 smartcard reader device driver
SYNOPSIS
device cmx
DESCRIPTION
The cmx driver provides support for the PCCARD based Omnikey CardMan 4040 smartcard reader. The driver provides a character device special
file based Chip/Smart Card Interface Devices (CCID) interface. The driver implements what the vendor calls the Synchronous API onto the
smartcard reader device.
Reading and writing is synchronous, meaning that a call to write(2) directly corresponds to a complete CCID command sent to the device, while
the following read(2) will return the complete answer from the reader. There is no support for partial reads or writes. There is no upper
limit on CCID request or response sizes, but the complete CCID request must be sent to the driver in write(2) and the complete CCID response
must fit into the buffer supplied to read(2).
Non-blocking I/O, select(2) and poll(2) are supported and work as expected. An open file descriptor will always be ready for writing, but
only ready for reading if the device indicates that it has data available.
FILES
/dev/cmxn Character device special file.
/usr/ports/security/openct OpenCT, a userspace smartcard daemon containing a CCID driver which directly supports cmx devices.
COMPATIBILITY
Userland smartcard code written for the vendor's Linux drivers should work with the cmx driver without modification.
SEE ALSO
pccard(4)
HISTORY
The cmx driver first appeared in FreeBSD 7.1.
AUTHORS
The cmx driver was written by Daniel Roethlisberger <daniel@roe.ch>, originally based on the Linux driver v1.1.0 by Omnikey GmbH
www.omnikey.com. Early testing and bug fixes by Marcin Cieslak <saper@system.pl>.
BUGS
The way the cmx driver talks to the CardMan 4040 is a bit rough. Due to the complete lack of hardware documentation other than vendor driv-
ers for other operating systems, the gory details of the device's I/O registers are not understood very well. There may be error conditions
which can only be solved by physically reinserting the reader.
BSD
July 7, 2007 BSD