    **************************************************************************

    ALL OF THESE FILES ARE FOR HP INTERNAL USE ONLY AND ARE COMPANY CONFIDENTIAL

    **************************************************************************

    Included is some documentation and example code about Catseye.  The ERS
    you received with this tape contains some errors, especially about the
    RUG chip.  The 'ruguse' document should be used when in doubt.

    ruguse: Correct information on using RUG.

    appnote: General hints about using a Catseye display.

    btest.c: Program to access hardware registers on a Catseye board.

    btest.man: Description of the btest program.

    lib.c: Example (more or less debugged) graphics library to use
	   Catseye.
	   CAUTION: This library has not been fully tested and should
		    be used only as a guide for software development.

    lib.c.h1, lib.c.h2 : header files for lib.c

    lib.man: Description of commands in lib.c

    hrclens.c: example program using lib.c


The programs assume that two special device files exist for each Catseye
board in the system.  Only one Catseye may be in DIO I space, all other
boards must reside in DIO II space.  

	/dev/catseye
	/dev/cat_fb

where /dev/catseye is used to map in the control space, /dev/cat_fb is used to
map in the frame buffer space.  

The device files for placing catseye in DIO I space are as follows:
(card switch setting all closed except for switch 1)

	0 crw-rw-rw-	1 root	other	10 0x005601 Mar 20 12:52 /dev/catseye
	0 crw-rw-rw-	1 root	other	10 0x002020 Mar 20 12:52 /dev/cat_fb


The device files for placing catseye in DIO II space in the first space are as follows:
(card switch setting all closed except for switchs 8 and 3)

	0 crw-rw-rw-	1 root	other	10 0x010001 Mar 24 09:15 /dev/catseye
	0 crw-rw-rw-	1 root	other	10 0x012020 Mar 24 09:16 /dev/cat_fb


Since all of the above code and documentation are not true products, all
usual disclaimers apply.  Good luck.
					Desi Rhoden
