src/sys/dev/isp/isp_ioctl.h, branch release/5.3.0_cvs

This commit was manufactured by cvs2svn to create tag

2004-11-04T19:12:42+00:00

'RELENG_5_3_0_RELEASE'.

This commit was manufactured to restore the state of the 5.3-RELEASE image.

Reverse role defines for initiator and target mode to better match the

2004-02-07T03:43:27+00:00

class 3 service parameters we'd get.

Steal 8 bits out of the portid u_int32_t for role information (port ids
are 24 bits anyway).

MFC after:	1 week

Add firmware major, minor and micro revsions to the ISP_FC_GETHINFO ioctl

2004-01-23T23:22:11+00:00

structure.

fix broken _IOR usage

2003-11-14T05:13:00+00:00

Add get/set param ioctls.

2002-07-08T17:34:56+00:00

MFC after:	1 week

Add ISP_FC_GETHINFO ioctl.

2002-06-16T04:59:30+00:00

MFC after:	1 week

Reorder some of the ioctls and add a few new ones.

2002-02-21T23:30:05+00:00

MFC after:	1 day

More for f/w crash dumps (bug fixing and adding ioctl entry points

2002-02-18T00:00:34+00:00

and hints to enable for specific units)

MFC after:	1 week

Support for f/w crash dumps (2200 && 23XX).

2002-02-17T06:38:22+00:00

If you want QLogic to look at a potential f/w problem for FC cards, you really
have to provide them info in the format they expect. This involves dumping
a lot of hardware registers (> 300 16 bit registers) and a lot of SRAM
(> 128KB minimum). Thus all of this code is #ifdef protected which will
become an option so that the memory allocation of where to dump the crash
image is pretty expensive. It's worth it if you have a reproducible problem
because they have some tools that can tell them, given the f/w version,
the precise state of everything.

MFC after:	1 week

+ A variety of 23XX changes:

2002-02-04T21:04:25+00:00

	disable MWI on 2300

	based on function code, set an 'isp_port' for the 2312- it's a
	separate instance, but the NVRAM is shared, and the second port's
	NVRAM is at offset 256.

+ Enable RIO operation for LVD SCSI cards. This makes a *big* difference
as even under reasonable load we get batched completions of about 30
commands at a time on, say, an ISP1080.

+ Do 'continuation' mailbox commands- this allows us to specify a work
area within the softc and 'continue' repeated mailbox commands. This is
more or less on an ad hoc basis and is currently only used for firmware
loading (which f/w now loads substantially faster becuase the calling
thread is only woken when all the f/w words are loaded- not for each
one of the 40000 f/w words that gets loaded).

+ If we're about to return from isp_intr with a 'bogus interrupt' indication,
and we're not a 23XX card, check to see whether the semaphore register is
currently *2* (not *1* as it should be) and whether there's an async completion
sitting in outgoing mailbox0. This seems to capture cases of lost fast posting
and RIO interrupts that the 12160 && 1080 have been known to pump out under
extreme load (extreme, as in > 250 active commands).

+ FC_SCRATCH_ACQUIRE/FC_SCRATCH_RELEASE macros.

+ Endian correct swizzle/unswizzle of an ATIO2 that has a WWPN in it.

MFC after:	1 week