+can-0.7.1 latest driver version version published
+ by Arnaud Westenberg
+
+can-0.7.1-tm5 the enhanced version with better support of
+ SJA1000 PeliCAN mode and CAN Ethernet proxy
+ contributed by Tomasz Motylewski <T.Motylewski@bfad.de>
+
+can-0.7.1-pi1 the import and usage of previous version for
+(Dec 2002) OCERA group purposes
+
+can-0.7.1-pi3.4 enhanced version with select support and rewritten
+(Mar 2003) make system for Linux kernels (2.2.x,2.4.x,2.5.x),
+ interrupts service cleanup and partial redesign
+ and DEVFS support
+
+lincan-0.2-pre heavily rewritten infrastructure of the driver based
+(Aug 2003) on atomic slot management of queues
+
+lincan-0.2 version tested on many bords and 2.2, 2.4, 2.6 Linux
+(Mar 2004) and RT-Linux enabled 2.4 Linux kernel
+
+lincan-0.2.8 possible SMP and HT deadlock fixed, driver can take
+(Jul 2004) advantage of CMPXCHG instruction if present on CPU,
+ added support for CPC-PCI and PCAN-PCI cards,
+ messages timestamping implemented
+ partially implemented support for Bosch C_CAN module,
+ requires more work and real hardware
+
+lincan-0.3 Changed SJA1000 chip IRQ handling. Enhanced VME
+(Nov 2004) and EMS CPC-PCI support and many other changes.
+
+lincan-0.3.1 Small improvements, RTR read moved into separate IOCTL,
+(Jul 2005) initial support for some boards contributed by users
+
+lincan-0.3.2 Improvements in SJA1000 error handling and reporting,
+(Feb 2006) i82527 support fixes, simple UDEV support,
+ updates for kernels up to 2.6.15 and fully preemptive
+ kernel compatibility. Support for MX1_DIS1 extension
+ board for PiMX1 ARM based BCC.
+
+lincan-0.3.3 Some more fixes of SJA1000 buss-of recovery,
+(May 2006) i82527 IRQ stuck problem fixed (reported by Terence Soh),
+ tested up to 2.6.17 (rc4). Minimal chip info in /proc/can.
+ Support for NSI CAN PCI contributed by Eric Pennamen.
+
+lincan-0.3.4 Some more fixes of SJA1000 buss-of recovery,
+(March 2009) Many enhancements and fixes. Tested up to 2.6.28 Linux kernel.
+
+lincan-0.3.5 Make system updates to build under latest Linux kernels,
+(October 2011) LinCAN core builds and tested with 2.6.35 and 3.0 Linux kernels.
+
+The actual version of driver have been latest tested it with
+ - KVASER pcican-q on 2.6 and 3.0 Linux kernel
+ - EMS CPC-PCI cards ("ems_cpcpci")
+ - virtual board tested on all systems as wel
+It takes more time to test driver with more cards.
+Infrastructure and support for more than 20 boards with more
+variants is prepared in the sources.
+
+
+SOURCES AND URLs
+================
+
+The actual driver version, development sources and mailing list
+can be found on OrtCAN project pages
+
+ http://ortcan.sourceforge.net/
+
+Please send comments, bug-fixes and enhancements directly to
+Pavel Pisa <pisa@cmp.felk.cvut.cz> or to OrtCAN discussion
+forums <http://sourceforge.net/projects/ortcan/forums>
+and or mailinglist found on OrtCAN project page.
+
+The original LinCAN driver component page at OCERA web site
+(not updated to the new version yet)
+
+ http://www.ocera.org/download/components/WP7/lincan-0.3.1.html
+
+List of related communication components
+
+ http://www.ocera.org/download/components/WP7/index.html
+
+Driver documentation can be found at
+
+ http://cmp.felk.cvut.cz/~pisa/can/doc/lincandoc-0.3.pdf
+
+The anouncements of new version are published at FreshMeat page
+
+ http://freshmeat.net/projects/lincan/
+
+
+COMPILATION of LinCAN releases
+==============================
+
+Just type 'make' at the command line and driver module should compile
+without errors for current running kernel.
+
+More detailed information can be found in driver documentation at
+ http://ortcan.sourceforge.net/lincan/
+Local maintainer site holds some usesfull information as well
+ http://cmp.felk.cvut.cz/~pisa/can/
+ http://cmp.felk.cvut.cz/~pisa/can/lincandoc-X.Y.pdf
+
+The LinCAN releases use OMK make system, which requires
+recent GNU make program version 3.81beta1 and above.
+Makefiles can be switched to old ones by script
+
+ sh ./switch-omk2std
+ make
+
+
+COMPILATION from OrtCAN project GIT repository tree
+===================================================
+
+There are more options to build LinCAN driver.
+The first one is to use stand-alone driver module build.
+The other option is to build LinCAN driver as part of the
+whole OrtCAN tree.
+
+The latest version of stand-alone LinCAN sources can be
+obtained from GIT repository and build by next commands
+
+ git clone git://git.code.sf.net/p/ortcan/lincan
+ cd lincan
+ ./build-lincan.sh
+
+The other option is to build LinCAN driver as part of the whole
+OrtCAN tree
+
+ git clone git://git.code.sf.net/p/ortcan/ortcan-top
+ cd ortcan/
+ git submodule update --init
+ make default-config
+ make
+
+COMPILATION options
+===================
+
+The options are defined in "config.omk" file for OMK based builds.
+File is looked for at directory where are build top directory,
+files "Makefile.rules" and "config.omk-default"
+located. To select card which is not enabled by default
+add line of next format to the "config.omk" file
+
+ CONFIG_OC_LINCAN_CARD_tscan1=y
+
+The cross-compilation and build against non-default kernel
+can be selected in "config.omk" file as well
+
+ LINUX_DIR=/usr/src/linux-2.6-mpc5200-build
+ CC=powerpc-linux-gnu-gcc
+ CXX=powerpc-linux-gnu-g++
+ AR=powerpc-linux-gnu-ar
+ LD=powerpc-linux-gnu-ld
+
+
+INSTALLATION
+============
+Type 'make install' for standard make system compilation.
+The driver should be copied into actual kernel version
+modules directory "/lib/modules/x.y.z/kernel/drivers/char".
+
+OMK system requires manual copy of files from "_compiled" tree
+to its final destinations.
+
+Create file "lincan.rules" with contents listed below in or linked
+into "/etc/udev/rules.d" directory to enable automatic device nodes
+creation for UDEV based system
+
+ # LinCAN driver
+ SUBSYSTEM=="can",GROUP="users",MODE="0660"
+
+The driver automatic loding can be requested by addition of "lincan"
+line into "/etc/modules" od Debian based systems.
+
+The target hardware/board specific options should be added into
+"/etc/modprobe.conf" file or file with similar functionality for your
+distribution. The options are discusses in the next paragraph.