Technical data

isp(7D) Devices SunOS 5.5
FILES /kernel/drv/isp ELF Kernel Module
/kernel/drv/isp.conf Configuration file
SEE ALSO prtconf(1M), driver.conf(4), scsi_abort(9F), scsi_hba_attach(9F), scsi_ifgetcap(9F),
scsi_reset(9F), scsi_transport(9F), scsi_device(9S), scsi_extended_sense(9S),
scsi_inquiry(9S), scsi_pkt(9S)
Writing Device Drivers
ANSI Small Computer System Interface-2 (SCSI-2)
ISP1000 Firmware Interface Specification, QLogic Corp.
ISP1000 Technical Manual, QLogic Corp.
DIAGNOSTICS The messages described below are some that may appear on the system console, as well
as being logged.
This first set of messages may be displayed while the isp driver is first trying to attach.
All of these messages mean that the isp driver was unable to attach. These messages are
preceded by "isp%d", where "%d" is the instance number of the isp controller.
Device in slave-only slot, unused
The SBus device has beenplaced in a slave-only slot and will not be accessible;
move to non-slave-only SBus slot.
Device is using a hilevel intr, unused
The device was configured with a interrupt level that cannot be used with this
isp driver, check the SBus device.
Failed to alloc soft state
Driver was unable to allocate space for the internal state structure. Driver did
not attach to device, SCSI devices will be inaccessible.
Bad soft state
Driver requested an invalid internal state structure. Driver did not attach to dev-
ice, SCSI devices will be inaccessible.
Unable to map registers;
Driver was unable to map device registers; check for bad hardware. Driver did
not attach to device, SCSI devices will be inaccessible.
Cannot add intr
Driver was not able to add the interrupt routine to the kernel. Driver did not
attach to device, SCSI devices will be inaccessible.
Unable to attach
Driver was unable to attach to the hardware for some reason that may be
printed. Driver did not attach to device, SCSI devices will be inaccessible.
This next set of messages can be displayed at any time, they will be printed with the full
device pathname followed by the shorter form described above.
Firmware should be < 0x%x bytes
Firmware size exceeded allocated space; will not download firmware. This could
7D-166 modified 30 Aug 1995