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
Check Out this Related Man Page
cmx(8) System Manager's Manual cmx(8)NAME
cmx - Generic communication exerciser
SYNOPSIS
/usr/field/cmx [-b [minbaud]-[maxbaud]] [-h] [-ofile] [-tn] -l line-n...
OPTIONS
Use this option to specify the minimum, maximum, or range of baud rates to test. Prints help messages about the cmx command. Test all the
listed tty lines, where n equals the lines to test according to the special device file entries in the /dev directory, such as 00, 12, or
42-53 Saves output diagnostics in file. Specifies the run time in minutes (n). The default is to run until a [CTRL-C] or a kill -15 pid
is sent to the process.
DESCRIPTION
The cmx exerciser writes, reads, and validates random data and packet lengths on a specified communications line. The line being tested
must have a loopback connector attached to the distribution panel, or the cable and the line must be disabled in the /etc/inittab file and
a non-modem line; the CLOCAL option must be set to on.
The exerciser runs until a [CTRL-C] or a kill -15 pid is sent to the process.
A logfile for you to examine and then remove is created in the current working directory; errors can be listed in the logfile.
You must specify the -l option 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 /dev directory without the letters "tty." For
example, if the /dev directory lists tty03, the line-n argument is 03.
The Devices section lists the devices that can be tested.
RESTRICTIONS
If you want to run a system exerciser over an NFS link or on a diskless system, there are some restrictions. For exercisers such as fsx(8)
that need to write into a file system, the target file system must be writable by root. Also, the directory from which an exerciser is exe-
cuted must be writable by root because temporary files are written into the directory. These restrictions can be difficult to adhere to
because NFS file systems are often mounted in a way that prevents root from writing into them. Some of the restrictions may be adhered to
by copying the exerciser into another directory and then executing it.
Pseudo devices (devices whose first character after tty is any alphabetic character, other than lowercase d) cannot be tested. Also lat
devices with major #5 cannot be tested.
DEVICES
Use the file command on /dev/tty* to find out which tty line corresponds to a device line number.
EXAMPLES
The following example runs the cmx 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 cmx exerciser on lines 11, 42, 45, and 76 in the background until interrupted by a [CTRL-C] or a kill -15 pid: %
/usr/field/cmx -l 11 42 45 76 & The following example runs the cmx exerciser on line 11, specifying a range of baud rates to test. %
/usr/field/cmx -b9600-38400 -l 11
SEE ALSO
Commands: diskx(8), fsx(8), memx(8), shmx(8), tapex(8)cmx(8)