d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

mdoc(7) police: removed hard sentence breaks.

Browse Source
This commit is contained in:
Ruslan Ermilov 2001-09-04 09:47:40 +00:00
parent c146250ee2
commit 92c355d758
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
share/man/man4/isp.4
View File

@ -56,12 +56,13 @@ Fibre Channel support uses FCP SCSI profile for
and utilizes Class 3 and Class 2 connections (Qlogic 2100 is Class
3 only, minor patches to the Qlogic 2200 to force Class 2 mode).
Support is available for Public and Private loops, and for
point-to-point connections (Qlogic 2200 only). The newer
2-Gigabit cards (2300, 2312) are also supported.
point-to-point connections (Qlogic 2200 only).
The newer 2-Gigabit cards (2300, 2312) are also supported.
Command tagging is
supported for all (in fact,
.Tn FibreChannel
requires tagging). Fabric support is enabled by default (but may
requires tagging).
Fabric support is enabled by default (but may
be contingent upon the correct firmware being loaded).
.Sh FIRMWARE
Firmware is now available if the
@ -131,7 +132,8 @@ option.
The following options are switchable by setting values in the loader
configuration file (see the
.Xr loader 8
manual page). They are:
manual page).
They are:
.Pp
.Bl -tag -width "isp_no_fwload" -compact
.It isp_disable
@ -169,7 +171,8 @@ The driver currently ignores some NVRAM settings.
The driver currently doesn't do error recovery for timed out commands
very gracefully.
.Pp
Target mode support isn't completely debugged yet. It works reasonably
Target mode support isn't completely debugged yet.
It works reasonably
well for Fibre Channel, somewhat well for Qlogic 1040 cards, but
doesn't yet work for the other cards (due to last minute unnanounced
changes in firmware interfaces).
@ -177,7 +180,8 @@ changes in firmware interfaces).
Sometimes, when booting, the driver gets stuck waiting for the
Fibre Channel f/w to tell it that the loop port database is ready,
or waiting for a good loop to be seen (this does not yet support
booting without being connected to a fibre channel device). To
booting without being connected to a fibre channel device).
To
unwedge the system, unplug and replug the fibre channel connection,
or otherwise cause a LIP (Loop Initialization Primitive sequence)-
this will kick the f/w into getting unstuck.