RELNOTES for version 0.7.1 (12/18/00):

	 - The driver becomes more and more stable since the beta release
	   in march.

	 - Kernel 2.0 is still supported, but not tested any longer.

	 - Kernel 2.4 is supported form the point of compilation, but not
	   tested yet.

	 - The internal structure of the driver becomes much cleaner since
           unsing a pointer to the global structure rather than a board index
           in each function.

	 - The driver locks now the memory, if the user hasn't used mlock(2).
	   So you can start test_itifg in read mode WITHOUT being root.

	 - The SMP support is much cleaner, more robust and TESTED!

	 - I have cross-compiled the code for powerpc, alpha and ia64 systems,
           but this doesn't mean, that it also should run.

	 - The naming of the camera config files follows now the scheme:

	       vendor-model-feature-board.cam.

	 - The libconfig.a/config.h was renamed to libiticonfig.a/iticonfig.h
           to avoid naming clashes.

RELNOTES for version 0.7.0beta (03/27/00):

The main difference between this and all older device driver versions is,
that we do now a PAGEWISE transfer of the frame directly into the (for now
still mlock(2)'ed) user space. This means, you have to be root to run the
test_itifg program in an other than the -o mmap mode. The later mode
allocates an 'in kernel' buffer (< 60MB) and you can mmap it (no root
access needed).

The new transfer scheme has some consequences:

        + The Reserved Upper Memory is no longer needed, because you can
          alloc/dealloc your buffers while the system is running via
          mmap/malloc.

        - If the pagewise transfer is not done in hardware (PCDig), your
          system has SIGNIFICAT MORE interrupts to handle than before.
          So I strongly recommend to use a PPro or PII system!

Some driver interfaces has also changed:

        - any driver buffer control (GE_GET/SET_BMA/MEM) is now obsolete

        - the CR_SET_SNAP call is unified with the read(2) call.

But due to code maintenance problems there are some things, that are
no longer supported:

        - starting with this release, the old (rev. 0/1Q) IC-PCI boards
          are unsupported

        - the board trigger mode is now unsupported - I think the right
          way to trigger is to trigger the camera, not the board (any
          other suggestions welcome!)

Other things, that have changed:

        - the test_itifg is completely new and better structured - now it
          can also fork itself to grab from more than one board

        - starting with this release we have ONLY TWO special device files

Conclusion:
Many things have changed. Please try out your favorite ones and mail to
the list about any suggestions/problems...

RELNOTES for version 0.6.0b (05/02/00):

	- PCDig fpga download files are now included
	- some user contributed camera config files added
	- two new dialog based shell scripts to setup and maintain the
	  bma base and size values 'user friendly'
	- only minor code patches

RELNOTES for version 0.6.0a (12/03/99):

	- many bugfixes (see ChangeLog entries for v060pl)

	- proc-fs support to read out version, date, boards, modules

RELNOTES for version 0.6.0 (09/23/99):

	1. from the users point of view:
        --------------------------------

	- Support for the new PCDig (digital) board.
	  (not yet: automatic image conversion for multiple tapped cameras
                    support for the two on board serial ports)

	- Because now it's the first time, that we also support another
	  board beside the IC-PCI (the PCVision was only from the hardware
	  different), the name of the driver has changed from ICPCI to ITIFG.

	- Support for cameras with very with image sizes (bigger than the
	  on-board memory size). This feature was realized through an
	  'immediate transfer modus', which copies the image in 64k pieces
	  from the on-board to the 'upper main memory area'.
	  (tested with the Kodak MegaPlus 6.3i - 3072x2048 = 6Mb > 4Mb,
	   but also useful for e.g. 1280x1024x10bit on a 2Mb IC-PCI)

	- Conditioned by the last point, we have another change of spelling:
	  The former BMA (Bus Master)- Modus is now called UMB (Upper Memory
	  Buffer)- Modus.
	  (Please don't forget this, if you try an 'insmod itifg umb=disable'
	  or 'test_itifg -o umb')
	  This was needed to prepare Bus Master Transfer also directly to
	  the user space (only difference to 'Immediate Transfer' - 4k 'Pages'
	  instead of 64k 'Pieces'), not only to the Upper Main Memory Area.
	  (Successfully tested, but not delivered with this release)

	- Extended libconfig.a (conversion function for PCDig fpga-files) and
	  new utility program config_pcdig (board download of these files)

	- Completely revised installation, please see the INSTALLATION section
	  in itifg.4

	- New and comfortable boot time startup script. Now you can try
	  /etc/rc.d/init.d/itifg (start|stop|restart) to instert/remove the
	  module, build the device files and download the fpga-files to the
	  PCDig.

	2. from the programmers point of view:
        -------------------------------------
	
	- most functions, named icp_ have been renamed to iti_; the main
	  glabal structure is now iti.

	- in some functions are now constructs like

		switch (DEVICE_ID)
		  {
		    case ITI_ICPCI:
		      ...
		      break;
		    case ITI_PCDIG:
		      ...
		      break;
		  }

	- the other functions are selected via a virtual function switch
	  table:

	  old function call:

		cr_get_fcnt (board):

	  new function call:

		iti.vcr[board]->get_fcnt (board);

RELNOTES for version 0.5.1 (09/21/99):

	- Support for the AM-STD/COMP color acquisition module!
	  This work was done by
		Rolando Cantarutti <rcantarutti@ctios2.ctio.noao.edu>,
	  Special Thank's to him!
	  (To apply the patches you should now use `make [clr|rgb|cmp]-patch'
	   instead of the old general make patch)

	- Hardware decimation (2,4,8) in x and y direction (if you decimate
	  an CCIR interlaced image by 2, you read in only one field an can
	  achive 50fps).
	  You can test this with `test_icpci -z 2,4,8 ...'.
	
	- Support for the on-board io-ports - there will be a new device
          ic[0123]ioP. You can write to it (with strobe) an read from it
          in non-blocking or blocking (with strobe/interrupt) mode.
	  An example program (ioport_icpci) is included.

	Other new features are

	- Dynamic major device number assignment (don't forget to run the
	  new MAKEDEV.icpci after EVERY insmod)

	and the

	- Support for different irq's on multi-board installations.

	- A new ioctl to GET/RESET_STATISTICS (number of frames /
	  number of io-port events) is also introduced.

RELNOTES for version 0.5.0a (06/02/99):

	- the poll(2) interface is tested - due to this test_icpci has now
	  sightly different parameters ('-s signal|select|poll' determines
	  now the synchronisation mode)

	- a bug with displaying grey images in case of a timeout is fixed
	  (kernel 2.2 only)

	- the AMRGB module ist updated and should work now

	- other minor bugfixes
	
RELNOTES for version 0.5.0 (05/02/99):

	1. from the users point of view:
        --------------------------------

	- support for kernel 2.2

	- support for the special exsync counter at the AM-DIG
	  (ioctl + example program 'extime_icpci')

	- before you can 'make all', you have to run 'make config' -
	  this determines the system (linux-2.0/2.2) with 'uname -s/-r'
	  and saves the result in .system
 
	- icpciMain.h/icpciIoctl.h is outdated -> user programs have to
	  include icpciExt.h

	- the AM-CLR/AM-STD/RGB patches are revised by me and untested,
	  please wait for the next release or use 0.4.3c instead, which
	  has a new patch for the AM-CLR (thanks to Werner)
	
	- the poll(2) system-call should work, but I have tested it not
	  yet

	- the copy of 64k AM-DIG LUT's into/from the kernel space should
	  be fixed (special thanks to "A.J. Aranyosi" <aja@mit.edu>)

	- ENODEV is replaced by ENXIO

	- the kernel patchfiles reserve some memory by themselve, if you
	  don't specify anything (8Mb if < 128M, 16M if > 128M) (see manual)
  
	2. from the programmes point of view:
        -------------------------------------

	- now we have a complete os-indipendent layer - all system
	  dependencies are in osLx20/22.c and icpciOS.h

	- various global variables have been moved into the global icp
	  structure

	- some parts of the 'pci' subfield of icp are now in the 'map'
	  subfield; os-depending stuff is in the new 'osp' subfield

	- the card8/16/32/bool data types have been replaces by
	  u_char/short/long/int; PDEBUG/printk is now named ICP_PRINTF/
	  icp_printf

	- direct memory access to the board via pointer dereferencing
	  is avoided, icp_readb/w/l, icp_writeb/w/l, memcpy_from/toio
	  is used

	- the ChangeLogs are no longer in every file, old messages are
	  into ChangeLog.old, newer ones at the end of ChangeLog, which
	  is is generated by CVS

	- the initialization of the acquisition modules is done in two
	  steps (am??_startup and am??_init)

	- the time critical clearing of the on-board memory is now done
	  in several pieces with scheduling (mouse should no longer hang)

RELNOTES for version 0.4.3c (04/30/99):

	- this version INCLUDES the glibc-patches for version 0.4.3b

	- Werner has send me a new and TESTED AM-RGB patch-file for 0.4.3b,
	  this is included into this release

	- NO OTHER CHANGES IN COMPARISON TO 0.4.3b 


RELNOTES for version 0.4.3b (02/01/99):

	- to access the upper memory area (bus-master buffers) mmap
	  /dev/ic[0|1|2|3]idI instead of /dev/mem. This is nesseccary,
	  because mmap at /dev/mem DISABLES caching of these memory space.
	  Without caching we got only 6fps (PII/266 CCIR 768x572) compared
	  to approx. 22fps now. 
	  (special thanks to Lars Prieske (lars@planet.de))

	- bug in irq-handler patched (timeouts when snapping images from
	  two digital cameras at seperate boards)

	- the additional programs test_icpci_clr and test_icpci_rgb are
	  untested!

RELNOTES for version 0.4.3 (11/03/98):

	- full support for the PCVision (IC-PCI with on board AM-VS)
	  (including config files and ioctl's)

	- support for the AM-STD/RGB with a patch
	  (hard wired configuration and no ioctl's)


RELNOTES for version 0.4.2 (08/11/98):

	- the driver is now under GPL (v2.0)

	- the problems with different starting and cycling lines
	  at the AM-DIG are fixed

	- VERSION ioctl added (software version is returned)

	- now we can remap also UNALIGNED cr and icr register spaces
	  (useful for some Motherboards) 

	- some fixes to share irq's with other device drivers

	- the test program can detect timeouts also in signal mode

	- fixes at the CLR module for faster processors
