cmx(4) [debian man page]
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 Synchronious API onto the smartcard reader device. Reading and writing is synchronious, 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. COMPATIBILITY
Userland smartcard code written for the vendor's Linux drivers should work with the cmx driver without modification. 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. 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
Check Out this Related Man Page
cmx(8) System Manager's Manual cmx(8) Name cmx - generic communication exerciser Syntax /usr/field/cmx [ -h ] [ -ofile ] [ -tn ] -l line-1 ... Description The exerciser will write, read, and validate random data and packet lengths on a given communications line. The line under test must have a loopback connector attached to the distribution panel or the cable and the line must be disabled in the file and a non-modem line. That is, the flag must be set to off. The exerciser runs until or kill -15 pid is sent to the process. A logfile is made in for you to examine and then remove. If there are errors listed in the logfile, make sure that you check the file, because that is where the driver and kernel error messages are saved. You must specify the -l flag followed by the lines to test. The line-n arguments identify the lines to be tested. A maximum of 32 lines can be tested at any one time. The line-n arguments are specified as names taken from the directory without the letters ``tty''. For example, if the directory lists tty03, the line argument is 03. The DEVICES section lists the devices that can be tested. Restrictions If there is a need to run a system exerciser over an NFS link or on a diskless system there are some restrictions. For exercisers that need to write into a file system, such as the target file system must be writable by root. Also the directory, in which any of the exer- cisers are executed, must be writable by root because temporary files are written into the current directory. These latter restrictions are sometimes difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of the restrictions may be overcome by copying the exerciser to another directory and then executing it. Options -h Prints help message about this command. -ofile Save output diagnostics in file. -tn Run time in minutes (n). The default is to run until a or kill -15 pid is sent to the process. Restrictions Pseudo devices (those whose first character after tty is p, q, r, s, t, u) cannot be tested. Neither can lta devices with major #39. Devices Use the command on to find out which tty line corresponds to a device line number. Examples The following example runs the exerciser for 60 minutes on lines 00, 13, 22, and 32. % /usr/field/cmx -t60 -l 00 13 22 32 The following example runs the exerciser on lines 11, 42, 45, and 76 in the background until interrupted by a or kill -15 pid. % /usr/field/cmx -l 11 42 45 76 & See Also Guide to System Exercisers cmx(8)