#
#	ihcp.conf	x86 version
#
#	Hardware configuration file for IKON PCI hardcopy
#	interface driver.
#
#	This file contains driver configuration defaults, and forces the interrupt priority
#	to a value that keeps the scheduler happy.
#
#	Several driver default paramaters can be set by modifying this file and re-loading the driver.
#	This avoids having to re-compile the driver when it is necessary to change defaults.
#
#
#
#	START OF USER-CONFIGURABLE DEFAULTS
#
#	The handshake speed of the plotter interface is set by the vers_speed_def or cent_speed_def
#	property for versatec and centronics configurations, respectively.
#	Permissible values for either are 0,1,2, or 3.  0 gives the fastest speed.
#	See the board manual for details.
#
vers_speed_def=1;
cent_speed_def=1;
#
#	The default versatec print/plot mode is determined by mode_def.  0=print, 1=plot.
#	This mode can be (and usually is) overridden by the application calling the driver.
#
mode_def=1;
#
#	There are two software timeout clocks used by the driver: a dma timer, and a wait-for-ready timer.
#	The defaults for these timers are set by dma_time_def, and rdy_time_def, in SECONDS.
#
dma_time_def=1800;
rdy_time_def=1800;
#
#
#	The x86 version of this driver uses host-based dma chaining, which forms
#	scatter-gather lists in host memory.  sg_list_length controls the size of
#	the scatter-gather list, and therefore the amount of host memory used for
#	lists, and the maximum size of a dma transfer.
#
#	Each list entry (one per 4K buffer page) requires 16 bytes of host memory.
#	A 64 link chaining list consumes 1024 bytes of host memory, and allows a
#	maximum of 256K bytes per dma buffer.
#
sg_list_length=64;
#
#	END OF USER-CONFIGURABLE DEFAULTS
#
#
#
#	We force the interrupt priority of the
#	driver to level 9 to get it below the level of the
#	scheduler - the board's eeprom was reporting a class code that
#	caused the OBP to set the board's priority to the same level
#	as the scheduler, which required using a high-level
#	interrupt handler.
#
#	That should have been OK, but when two boards were running at the 
#	same time, LBOLT was getting confused and confusing the software timer.
#	It is not clear who was causing the problem.
#
#	We can solve the problem by changing our eeprom to give a class code
#	of 0x07, which currently gives us a priority of 1, but that seems
#	like too low a priority.
#
#	For now, we will force a relatively high priority, but below
#	the scheduler priority of 10.
#
#	DO NOT MODIFY THIS PROPERTY!!!!!
#
interrupt-priorities=9;