MFC r297818: Update 25xx chips firmware from 7.03.00 to 8.03.00.

While the same update is also available for 24xx chips, it seems have
a problem with disabling virtual ports -- firmware handles the request,
but does not respong on it, causing timeout in driver.

MFC r291143: Update Qlogic 23XX firmware from 3.03.26 to 3.03.28

MFC r291132: Update firmware for QLogic 22xx from 2.02.06 to 2.02.08.

MFC r289755: Remove residual verbosity.

firmware_register() already reports errors.

MFC r291188: Rip off target mode support for parallel SCSI QLogic adapters.

Hacks to enable target mode there complicated code, while didn't really
work. And for outdated hardware fixing it is not really interesting.

Initiator mode tested with Qlogic 1080 adapter is still working fine.

MFC r289626: Update firmware images for Qlogic 24xx/25xx from 5.5.0 to 7.3.0.

This also removes separate "_multi" images, since this funcationality is
now in base, and there is simply no new images without it for years.

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Switch to using FC-Tape firmware.
Sponsered by: Spectralogic
MFC after: 1 week

Roll to the latest 2400/2500 firmware available from the public QLogic
website.

Sponsored by: Spectralogic
MFC after: 1 week

Update firmware to more recent versions.

MFC after: 3 months

Don't spam dmesg with "registered firmware ..." when module is compiled
into kernel, unless there is a verbose boot flag set. There is no real
need to have this information printed.

MFC after: 1 week

Add 8Gb card firmware. Update some 2Gb and 4Gb f/w sets.
Split 4Gb and 8Gb into pieces that can be either multi_id
capable or not.

Reviewed by: scottl, ken
Approved by: re

Make ispfw(4) play nice with individual firmware modules.

- Do not let individual KLD module unregister firmware image loaded by ispfw
or vice versa.
- Make 'kldunload ispfw' actually unregister all firmware images loaded by
ispfw, not just 'isp_1040'.
- Print which KLD module actually loaded the firmware image.
- Remove unused return value from do_load_fw() and do_unload_fw() and remove
duplicate sys/param.h while I am here.

The MODULE_NAME should "ispfw" unless overriden, not "isp".

Use 2K Login f/w.

Add QLogic 2400 (4Gb) firmware.

Convert isp(4) and ispfw(4) to use firmware(9) to manage firmware
loading for the QLogic cards.

Because isp(4) exists before the root is mounted, it's not really
possible for us to use the kernel's linker to load modules directly
from disk- that's really too bad.

However, the this is still a net win in in that the firmware has
been split up on a per chip (and in some cases, functionality)
basis, so the amount of stuff loaded *can* be substantially less
than the 1.5MB of firmware images that ispfw now manages. That is,
each specific f/w set is now also built as a module. For example,
QLogic 2322 f/w is built as isp_2322.ko and Initiator/Target 1080
firmware is built as isp_1080_it.ko.

For compatibility purposes (i.e., to perturb folks the least), we
also still build all of the firmware as one ispfw.ko module.

This allows us to let 'ispfw_LOAD' keep on working in existing
loader.conf files. If you now want to strip this down to just
the firmware for your h/w, you can then change loader.conf to
load the f/w you specifically want.

We also still allow for ispfw to be statically built (e.g., for
PAE and sparc64).

Future changes will look at f/w unloading and also role switching
that then uses the kernel linker to load different ips f/w sets.
MFC after: 2 months

Add 2322 firmware.

Update 2300 f/w. This will probably be the last
update here before we switch to the new f/w loading
framework.

Fix -Wunder and make the sbus code really compile only on sparc64.

Roll firmware to the latest version. There are a bunch of features
in alternate f/w versions that will be pursued at some points.

MFC after: 1 month

Remember to snag firmware for the DELL OEM (6312) card

MFC after: 2 days

Start each of the license/copyright comments with /*-, minor shuffle of lines

Do a pass over all modules in the kernel and make them return EOPNOTSUPP
for unknown events.

A number of modules return EINVAL in this instance, and I have left
those alone for now and instead taught MOD_QUIESCE to accept this
as "didn't do anything".

Add missing <sys/module.h> includes

Fix $FreeBSD$.

Reported by: Daniel O'Connor <doconnor@gsoft.com.au>

Update firmware sets for the 12160, 2200 and 2300 cards to the (more or
less) latest from QLogic.

Use __FBSDID().
Also some minor style cleanups.

Roll to latest level.

Know that a 10160 is the same as a 12160.

MFC after: 0 days

Get the most recent 2300 f/w that's on the QLogic intranet- fixes lots
of buglets and quite a few bugs.

MFC after: 1 day

Upgrade to latest QLogic f/w from their intranet site for 2100, 2200 and
2300 cards.

MFC after: 1 day

Add SBus firmware (compiled in only for sparc systems).

Remove __P.

Roll to latest production level firmware.

MFC after: 1 day

Roll firmware to latest offerings... Fixes a number of f/w related
bugs.

MFC after: 1 week

Update to latest 12160 f/w.

MFC after: 1 week

Add 2300/2312 (2Gbit) firmware.

update to latest and greatest f/w

roll to 2.01.26 level

remove MAINTAINER file

some copyright cleanups

remove unneeded includes
(obtained from phk@freebsd.org)

Roll back target mode f/w to 7.55- 7.65 hangs when presented with a
non-disconnecting command. Interestingly enough, of the other flavors
of the 7.65 f/w (the dual-id and multi-id flavor)- the dual-id doesn't
hang (they're also supposed to be the same except for supporting dual
or multi-id capture!), but other things are questionable as well.

A side effect of new 12160 f/w- there is only one set whether target
mode enabled or not now (like the FC cards).

roll new Qlogic 2200 firmware in place

roll new Qlogic 2100 firmware in place

roll new 12160.h firmware in place

Add in (separate files for different board's firmware) new files for ispfw
loadable module.