BRIEF GUIDE FOR INSTALLING IKON HARDCOPY BOARD AND DRIVER IN HP-UX VERSION 10.X PCI MACHINES Applies to Ikon Model 10117 Pci Hardcopy Interface 18 May, 1998 IKON Corporation 2617 Western Avenue Seattle, Washington 98121 phone: (206) 728-6465 fax: (206) 728-1633 e-mail: ikoncorp@worldnet.att.net www: http://www.launchsite.com/ikon/ Other files provided with this driver: ihcp_driver.c source code module for driver ihcp_reg.h definition file for board's registers ihcp_var.h definition file for driver soft-state structure ihcp_io.h ioctl definition file for driver and calling programs ihcp master file for ihcp driver ihcp_install script that installs standard driver ihcp_install_debug script that installs driver with debug prints enabled ihcp_makefile script that compiles standard driver (called by install script) ihcp_makefile_debug script that compiles debug driver (called by install debug script) ihcp_remove script that removes driver modules and re-installs previous unix ihcp_mknod script that makes device nodes for ihcp driver & boards filtertest.c simple program that adds cr to each unix source line for printing iktest0.c simple sample program that prints test message on ihcp0 This guide includes instructions for installing an IKON Model 10117 and driver in HP workstations with Pci I/O slots. INSTALLING: 1) Configure and install the board(s) in the appropriate Pci slot(s). All board configuration is done via software, with the exception of the interface type selection, which is done with an on-board jumper cable. Connect the cable between the I/O pin strip, and either the CENT pin strip (for Centronics compatible devices) or the V-DIFF pin strip (for Versatec, VPI, Xerox ColorgrafX compatible devices). A single driver can support multiple boards. 2) Create a directory called IKON that will be used as a base for install cleanup, test. It will contain the IKON provided files and the results of compile operations. Copy the IKON files to this directory. 3) If any changes are to be made to the driver source code, make them now. The source modules are: ihcp_reg.h Provides "internal" definitions used by all versions of the driver. ihcp_var.h Defines the soft-state structure used by the driver. ihcp_io.h Provides "external" ioctl command definitions used by all versions of the driver, and by the calling application. Also contains some user- modifiable definitions. ihcp_driver.c The source code module for the driver. 4) Become super-user. 5) Install the driver (ihcp_install) Type "./ihcp_install" The ihcp modules will be copied to the appropriate locations, the driver source compiled, and the kernel modules linked to make a new kernel (/stand/build/vmunix_test). The script will also back up the original /stand/vmunix as "/stand/vmunix.back", if the backup does not already exist, and will copy /stand/build/vmunix_test to "/stand/vmunix". 6) Reboot the system With the exceptin of one "ihcp" line for each board installed, during reboot the driver code is silent, unless the version with debug printing is loaded. 7) Make the Device Node (ihcp_mknod) run: "./ihcp_mknod The device file name(s) will be "/dev/ihcp", where "" is the instance number of each board. Instance numbers are somewhat unpredictable, depending on what 10117 boards (if any) have been previously installed, and in what slots. A single board, installed for the first time should have an instance number of "0". At this point, the device should be available for application programs. NOTE: Included on the distribution media is a file called iktest0.c. This sample program demonstrates the calling sequences required to issue ioctls to issue board commands and/or set driver parameters, to write to the device attached to the board, and to read back the board's registers. Compile it to run the test, if desired, but make sure the device number is correct first. DEINSTALLING: If it is desired to remove the ihcp driver and associated modules, as super user type "./ihcp_remove". This will remove ihcp modules and entries, and copy the previously saved unix to /stand/vmunix. If there is no saved unix (/stand/vmunix.back), a fresh unix will be created. NOTE: If it is desired to switch between the standard driver and the debug driver, it is not necessary to de-install first.