src/sys/dev/mpt/mpt_debug.c, branch releng/12.2

sys/dev: further adoption of SPDX licensing ID tags.

2017-11-27T14:52:40+00:00

Mainly focus on files that use BSD 2-Clause license, however the tool I
was using misidentified many licenses so this was mostly a manual - error
prone - task.

The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.

Add PIM_EXTLUNS support to mpt(4).

2017-03-10T14:44:59+00:00

Target mode is still limited to 256 LUNs due to the way driver is written,
but initiator can now use full 8 byte LUN space.

MFC after:	2 weeks

After r241858, remove the remainder of FreeBSD ~4 support from mpt(4).

2012-10-22T10:42:59+00:00

MFC after:	1 week

- Staticize functions as appropriate and comment out unused ones.

2011-07-29T18:35:10+00:00

- Sprinkle some const where appropriate.
- Consistently use target_id_t for the target parameter of mpt_map_physdisk()
  and mpt_is_raid_volume().
- Fix some whitespace bugs.

Approved by:	re (kib)

Correct spelling.

2011-04-22T09:59:16+00:00

Submitted by:	brucec

MFP4: principally to reapply tagged command support to FC and SAS cards.

2006-12-07T22:02:28+00:00

Fix config page writes to not strip out the attributes when you

2006-07-12T07:48:50+00:00

actually go write the config page. This fixes the long standing
problem about updating NVRAM on Fibre Channel cards and seems
so far to not break SPI config page writes.

Put back role setting into mpt. That is, you can set a desired role
for mpt as a hint. On the next reboot, it'll pick that up and redo
the NVRAM settings appropriately and warn you that this won't take
effect until the next reboot. This saves people the step of having
to find a BIOS utilities disk to set target and/or initiator role
for the MPT cards.

Add acknowledgements to LSI-Logic for support

2006-05-29T20:34:28+00:00

Get most of the way back to having Integrated Mirroring work

2006-05-26T05:54:21+00:00

again- the addition of target mode support broke it massively.

Fix some of the previus changes 'better'.

2006-04-01T07:12:18+00:00

There's something strange going on with async events. They seem
to be be treated differently for different Fusion implementations.
Some will really tell you when it's okay to free the request that
started them.  Some won't. Very disconcerting.

This is particularily bad when the chip (FC in this case) tells you
in the reply that it's not a continuation reply, which means you
can free the request that its associated with. However, if you do
that, I've found that additional async event replies come back for
that message context after you freed it. Very Bad Things Happen.

Put in a reply register debounce. Warn about out of range context
indices. Use more MPILIB defines where possible. Replace bzero with
memset. Add tons more KASSERTS. Do a *lot* more request free list
auditting and serial number usages. Get rid of the warning about
the short IOC Facts Reply.  Go back to 16 bits of context index.

Do a lot more target state auditting as well. Make a tag out
of not only the ioindex but the request index as well and worry
less about keeping a full serial number.