Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

New sentence, new line.

Browse Source
This commit is contained in:
wiz 2009-05-18 13:49:43 +00:00
parent 32a127402a
commit 84e3197bea
1 changed files with 39 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

72
share/man/man4/iop.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: iop.4,v 1.19 2008/04/30 13:10:54 martin Exp $
.\" $NetBSD: iop.4,v 1.20 2009/05/18 13:49:43 wiz Exp $
.\"
.\" Copyright (c) 2000, 2001, 2007 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -49,26 +49,29 @@ I/O processors conforming to the
specification, revision 1.5 and above.
.Pp
I2O is a specification that defines a software interface for communicating
with a number of device types. In its basic form, I2O provides the
following:
with a number of device types.
In its basic form, I2O provides the following:
.Pp
.Bl -bullet
.It
A vendor-neutral interface for communicating with an I/O processor (IOP)
and a number of types of peripherals. In order to achieve this,
hardware-specific device drivers run on the IOP, and hardware-neutral device
drivers run on the host.
and a number of types of peripherals.
In order to achieve this, hardware-specific device drivers run on
the IOP, and hardware-neutral device drivers run on the host.
.It
Reduced I/O overhead for the host. All communication between the host and
the IOP is performed using a high level protocol. The specification also
provides for batching of requests and replies between the host and IOP.
Reduced I/O overhead for the host.
All communication between the host and the IOP is performed using
a high level protocol.
The specification also provides for batching of requests and replies
between the host and IOP.
.It
An optional vendor-neutral configuration interface. Data from HTTP GET and
POST operations can be channeled to individual devices, and HTML pages
returned.
An optional vendor-neutral configuration interface.
Data from HTTP GET and POST operations can be channeled to individual
devices, and HTML pages returned.
.El
.Pp
Five types of devices are well defined by the specification. These are:
Five types of devices are well defined by the specification.
These are:
.Pp
.Bl -bullet -compact
.It
@ -99,9 +102,9 @@ and
are prerequisites and must therefore be included beforehand.
.Bl -tag -width OTTF
.It Dv IOPIOCPT (struct ioppt)
Submit a message to the IOP and return the reply. Note that the return
value of this ioctl is not affected by completion status as indicated by the
reply.
Submit a message to the IOP and return the reply.
Note that the return value of this ioctl is not affected by completion
status as indicated by the reply.
.Bd -literal
struct ioppt {
void *pt_msg; /* pointer to message buffer */
@ -120,20 +123,22 @@ struct ioppt_buf {
};
.Ed
.Pp
The minimum timeout value that may be specified is 1000ms. All other values
must not exceed the
The minimum timeout value that may be specified is 1000ms.
All other values must not exceed the
.Nm
driver's operational limits.
.Pp
The initiator context and transaction context fields in the message frame
will be filled by the
.Nm
driver. As such, this ioctl may not be used to send messages without a
driver.
As such, this ioctl may not be used to send messages without a
transaction context payload.
.It Dv IOPIOCGSTATUS (struct iovec)
Request the latest available status record from the IOP. This special-case
ioctl is provided as the I2O_EXEC_STATUS_GET message does not post replies,
and can therefore not be safely issued using the IOPIOCPT ioctl.
Request the latest available status record from the IOP.
This special-case ioctl is provided as the I2O_EXEC_STATUS_GET
message does not post replies, and can therefore not be safely
issued using the IOPIOCPT ioctl.
.El
.Pp
The following ioctls may block while attempting to acquire the
@ -143,22 +148,23 @@ driver's configuration lock, and may fail if the acquisition times out.
.It Dv IOPIOCGLCT (struct iovec)
Retrieve the
.Nm
driver's copy of the logical configuration table. This copy of the LCT
matches the current device configuration, but is not necessarily the latest
available version of the LCT.
driver's copy of the logical configuration table.
This copy of the LCT matches the current device configuration, but
is not necessarily the latest available version of the LCT.
.It Dv IOPIOCRECONFIG
Request that the
.Nm
driver scan all bus ports, retrieve the latest version of the LCT, and
attach or detach devices as necessary. Note that higher-level
reconfiguration tasks (such as logically re-scanning SCSI busses) will not
be performed by this ioctl.
attach or detach devices as necessary.
Note that higher-level reconfiguration tasks (such as logically
re-scanning SCSI busses) will not be performed by this ioctl.
.It Dv IOPIOCGTIDMAP (struct iovec)
Retrieve the TID to device map. This map indicates which targets are
configured, and what the corresponding device name for each is. Although at
any given point it contains the same number of entries as the LCT, the number
of entries should be determined using the iov_len field from the returned
iovec.
Retrieve the TID to device map.
This map indicates which targets are
configured, and what the corresponding device name for each is.
Although at any given point it contains the same number of entries
as the LCT, the number of entries should be determined using the
iov_len field from the returned iovec.
.Bd -literal
struct iop_tidmap {
u_short it_tid;