1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
|
.\" $OpenBSD: mpt.4,v 1.3 2004/03/31 03:45:40 marco Exp $
.\"
.\" Copyright (c) 2003 Wasabi Systems, Inc.
.\" All rights reserved.
.\"
.\" Written by Jason R. Thorpe for Wasabi Systems, Inc.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed for the NetBSD Project by
.\" Wasabi Systems, Inc.
.\" 4. The name of Wasabi Systems, Inc. may not be used to endorse
.\" or promote products derived from this software without specific prior
.\" written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY WASABI SYSTEMS, INC. ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL WASABI SYSTEMS, INC
.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.Dd February 25, 2004
.Dt MPT 4
.Os
.Sh NAME
.Nm mpt
.Nd LSI Fusion-MPT SCSI and FibreChannel host adapter driver
.Sh SYNOPSIS
.Cd "mpt* at pci? dev ? function ?"
.Cd "scsibus* at mpt?"
.Sh DESCRIPTION
The
.Nm
driver provides support
for the LSI Logic Fusion-MPT family of
.Tn SCSI
and
.Tn Fibre Channel
controllers:
.Pp
.Bl -bullet -compact -offset indent
.It
53c1020
.Pq Single Ultra320 Tn SCSI
.It
53c1030
.Pq Dual Ultra320 Tn SCSI
.It
FC909
.Pq 1Gb/s Tn Fibre Channel
.It
FC909A
.Pq Dual 1Gb/s Tn Fibre Channel
.It
FC919
.Pq 2Gb/s Tn Fibre Channel
.It
FC929
.Pq Dual 2Gb/s Tn Fibre Channel
.It
Emulated in VMWare ESX Server 2
.El
.Pp
The LSI Logic SCSI and Fibre Channel controllers contain firmware that presents
a multiprotocol service layer based on the LSI Logic Fusion-MPT architecture.
The firmware isolates the host drivers from the hardware and controls the
device side of the message passing interface to the host device drivers.
The firmware manages all phases of an I/O request and optimizes the interrupt
management for the system.
For Fibre Channel, the firmware also manages all FC-2 through FC-4 services,
which minimizes the amount of Fibre Channel unique services required with the
host driver.
.Pp
The MPI (Message Passing Interface) defintion includes a register-level
transport mechanism and a messaging protocol.
A system doorbell and message queues define the MPI transport interface.
Inbound Message Frames (MF), allocated in host memory, indentify I/O operations
to be performed by the IO Controller (IOC).
These operations are queued on the Request Queue by the host driver.
Outbound Message Frames, also in host memory, track I/O operations as they
complete.
These frames are queued on the Reply Queue by the IOC.
A doorbell mechanism is provided for IOC configuration, reset management,
and IOC status.
.Sh SEE ALSO
.Xr cd 4 ,
.Xr ch 4 ,
.Xr intro 4 ,
.Xr pci 4 ,
.Xr scsi 4 ,
.Xr sd 4 ,
.Xr siop 4 ,
.Xr st 4 ,
.Xr uk 4
.Sh HISTORY
The
.Nm
driver first appeared in
.Ox 3.5 .
.Sh AUTHORS
The
.Om
driver was ported from
.Nx
by Milos Urbanek, Kenneth R. Westerback and Marco Peereboom.
.Sh BUGS
This driver does not function properly with MPT firmware levels higher than
1.03.00.
.Pp
The runtime MPT firmware is displayed under the REV heading for the 1020/1030
chips during POST.
Example:
.Bd -literal
HBA ID LUN VENDOR PRODUCT REV SYNC WIDE
--- -- --- -------- ---------------- -------- ----- ----
0 7 0 LSILogic 1020/1030[ 102] 1013D00 320.0 16
1 7 0 LSILogic 1020/1030[ 102] 1013D00 320.0 16
.Ed
.Pp
The version is 1013D00 which translates to 1.01.3D.00.
The last two digits are normally not used and it is written in decimal notation.
Thus making this example version 1.01.61.
|
