1.\" $OpenBSD: mpii.4,v 1.8 2010/10/01 12:27:36 mikeb Exp $ 2.\" 3.\" Copyright (c) 2010 Marco Peereboom <marco@openbsd.org> 4.\" Copyright (c) 2009 David Gwynne <dlg@openbsd.org> 5.\" 6.\" Permission to use, copy, modify, and distribute this software for any 7.\" purpose with or without fee is hereby granted, provided that the above 8.\" copyright notice and this permission notice appear in all copies. 9.\" 10.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES 11.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF 12.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR 13.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES 14.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN 15.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF 16.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 17.\" 18.Dd $Mdocdate: October 1 2010 $ 19.Dt MPII 4 20.Os 21.Sh NAME 22.Nm mpii 23.Nd LSI Logic Fusion-MPT Message Passing Interface II 24.Sh SYNOPSIS 25.Cd "mpii* at pci?" 26.Cd "scsibus* at mpii?" 27.Sh DESCRIPTION 28The 29.Nm 30driver provides support for storage controllers using the 31LSI Logic Fusion-MPT Message Passing Interface II 32family of chipsets: 33.Pp 34.Bl -dash -offset indent -compact 35.It 36LSISAS2004, 37LSISAS2008 38.El 39.Pp 40These chipsets can be found on the following controllers: 41.Pp 42.Bl -dash -offset indent -compact 43.It 44Dell PERC H200 45.It 46LSI SAS 9200-8e, SAS 9211-4i, SAS 9211-8i 47.El 48.Pp 49Some models of these controllers have varying degrees of support for RAID 0 50and RAID 1. 51.Sh SEE ALSO 52.Xr bio 4 , 53.Xr intro 4 , 54.Xr pci 4 , 55.Xr scsi 4 , 56.Xr bioctl 8 , 57.Xr sensorsd 8 , 58.Xr sysctl 8 59.Sh HISTORY 60The 61.Nm 62driver first appeared in 63.Ox 4.7 . 64.Sh AUTHORS 65.An -nosplit 66The 67.Nm 68driver was written by 69.An James Giannoules 70and 71.An Mike Belopuhov . 72.Sh BUGS 73The chips supported by 74.Nm 75do not use a SCSI-like identifier. 76Instead they use an opaque ID and leave discovery order up to the operating 77system. 78The code to handle this is currently not implemented and therefore it is not a 79good idea to run this driver on a multi-boot machine or with more than 1 drive. 80