Add support for the HP Modular Smart Array 20 & 500 storage arrays.

Logical volumes on these devices show up as LUNs behind another
controller (also known as proxy controller).  In order to issue
firmware commands for a volume on a proxy controller, they must be
targeted at the address of the proxy controller it is attached to,
not the Host/PCI controller.

A proxy controller is defined as a device listed in the INQUIRY
PHYSICAL LUNS command who's L2 and L3 SCSI addresses are zero.  The
corresponding address returned defines which "bus" the controller
lives on and we use this to create a virtual CAM bus.

A logical volume's addresses first byte defines the logical drive
number.  The second byte defines the bus that it is attached to
which corresponds to the BUS of the proxy controller's found or the
Host/PCI controller.

Change event notification to be handled in its own kernel thread.
This is needed since some events may require the driver to sleep
on some operations and this cannot be done during interrupt context.
With this change, it is now possible to create and destroy logical
volumes from FreeBSD, but it requires a native application to
construct the proper firmware commands which is not publicly
available.

Special thanks to John Cagle @ HP for providing remote access to
all the hardware and beating on the storage engineers at HP to
answer my questions.

1 files changed, 4 insertions, 0 deletions

diff --git a/share/man/man4/ciss.4 b/share/man/man4/ciss.4
index 9bf7526..da53ffb 100644
--- a/share/man/man4/ciss.4
+++ b/share/man/man4/ciss.4
@@ -83,6 +83,10 @@ HP Smart Array 642
 HP Smart Array 6400
 .It
 HP Smart Array 6400 EM
+.It
+HP Modular Smart Array 20 (MSA20)
+.It
+HP Modular Smart Array 500 (MSA500)
 .El
 .Sh SEE ALSO
 .Xr cam 4 ,