+based on Philips CL RC622, RC531 and RC632, adding support should be very
+straightforward. If you want to contract me for implementing a driver
+backend, don't hesitate to contact me.
+
+
+3. Building / Installing
+
+In the default configuration, librfid only includes the driver for the OpenPCD
+dumbreader firmware.
+
+If you want support for Omnikey Cardman 5121/5321, you have to choose the
+backend you want to use, either:
+
+3.1 (new) native CCID backend
+
+If you add the '--enable-ccid' option to the './configure' command, then the new
+native CCID driver (courtesy of Werner Koch) will be linked into the library.
+This requires a working libusb with development headers.
+
+In order to use the reader, you will need to set the permissions of the
+respective /proc/bus/usb or /sys/bus/usb files (or run the application as
+root, if you trust my code, which you shouldn't).
+
+If you run udev, just use the 'etc/udev/librfid.rules' udev rulefile, which should
+change the group of the usb device to 'users'.
+
+3.2 (old) OpenCT backend
+
+This backend has the advantage that it will allow you to use the contact-based
+part and the contactless part of the CM5121 simultaneously.
+
+Please note that while librfid in this configuration _uses_ OpenCT as a
+lower-layer transport interface, it doesn't actually provide a virtual reader
+interface to it, i.e. you can't use CT-API/OpenCT/PCSC API's to access RFID
+transponders.
+
+In order to use this backend, you need to use the
+'--enable-openct' option and - if it is not installed in a default
+location like /usr or /usr/local - set the environment variables
+PATH, LD_LIBRARY_PATH and PKG_CONFIG_PATH so all files are found.
+
+
+4. Testing
+
+In the 'utils' directory, you will get a 'librfid-tool' binary. It is very
+minimalist, and mainly an example on how to use the librfid API. For an ICAO
+compliant passport, you may try "--layer2 iso14443a --protocol tcl". For a
+mifare ultralight transponder, "--layer2 iso14443a --protocol
+mifare-ultralight" will give you a full dump of the transponder.
+
+The most basic command to get started is "librfid-tool --scan" to make it
+auto-detect the first available (and supported) transponder
+
+
+5. Help and Support
+
+If you run into any problems using librfid, the primary contact address is the
+mailinglist of librfid developers at librfid-devel@lists.gnumonks.org. Please
+note that while the development community is trying to provide the best level
+of support, response times might vary.