svn commit: r231937 - head/share/man/man4
Christian Brueffer
brueffer at FreeBSD.org
Mon Feb 20 13:22:01 UTC 2012
Author: brueffer
Date: Mon Feb 20 13:22:00 2012
New Revision: 231937
URL: http://svn.freebsd.org/changeset/base/231937
Log:
More improvements, the biggest one using list environments for enumerations.
Modified:
head/share/man/man4/oce.4
Modified: head/share/man/man4/oce.4
==============================================================================
--- head/share/man/man4/oce.4 Mon Feb 20 11:27:37 2012 (r231936)
+++ head/share/man/man4/oce.4 Mon Feb 20 13:22:00 2012 (r231937)
@@ -58,7 +58,7 @@ module at boot time, place the following
if_oce_load="YES"
.Ed
.Sh DESCRIPTION
-Emulex one connect adapters come in various skews and with
+Emulex OneConnect adapters come in various skews and with
different combinations of NIC, FCoE and iSCSI functions.
The
.Nm
@@ -69,47 +69,63 @@ The
driver supports VLAN Hardware offload, TCP checksum offload,
TCP segmentation offload (TSO), Large receive offload (LRO),
Bonding, Jumbo frames (from 1500 - 9000), Multiple TX queues,
-Receive-Side Scaling(RSS) and MSI-X interrupts.
+Receive-Side Scaling (RSS) and MSI-X interrupts.
.Sh HARDWARE
The
.Nm
-driver supports the following Emulex network adapters:
+driver supports the following network adapters:
.Pp
.Bl -bullet -compact
.It
-BladeEngine 2
+Emulex BladeEngine 2
.It
-BladeEngine 3
+Emulex BladeEngine 3
.It
-Lancer
+Emulex Lancer
.El
.Sh UPDATING FIRMWARE
Adapter firmware updates are persistent.
.Pp
Firmware can be updated by following the steps below:
-.Bd -literal -compact
- 1) Copy the below code to a Makefile
- ".KMOD=elxflash
- FIRMWS=imagename.ufi:elxflash
- .include <bsd.kmod.mk>"
- 2) Replace imagename in above with UFI file name.
- 3) Copy Makefile and UFI to a directory
- 4) Execute make & copy generated elxflash.ko to /lib/modules
- 5) sysctl dev.oce.<if_id>.fw_upgrade=elxflash
- 6) Reboot the machine.
+.Bl -enum
+.It
+Copy the below code to a Makefile:
.Pp
-In case of issues with supplied UFI, flashing fails with one
-of the below errors.
- 1) "Invalid BE3 firmware image"
- 2) "Invalid Cookie. Firmware image corrupted ?"
- 3) "cmd to write to flash rom failed."
+.Bd -literal -offset indent
+\&.KMOD=elxflash
+FIRMWS=imagename.ufi:elxflash
+\&.include <bsd.kmod.mk>
.Ed
+.It
+Replace imagename in above with UFI file name
+.It
+Copy Makefile and UFI file to a directory
+.It
+Execute make & copy generated elxflash.ko to
+.Pa /lib/modules
+.It
+sysctl dev.oce.<if_id>.fw_upgrade=elxflash
+.It
+Reboot the machine
+.El
+.Pp
+In case of issues with supplied UFI, flashing fails with one
+of the following errors.
+.Pp
+.Bl -enum -compact
+.It
+.Qq Invalid BE3 firmware image
+.It
+.Qq "Invalid Cookie. Firmware image corrupted ?"
+.It
+.Qq cmd to write to flash rom failed.
+.El
.Sh SUPPORT
For general information and support,
go to the Emulex website at:
-.Fa http://www.Emulex.com/
+.Pa http://www.Emulex.com/
or E-Mail at
-.Fa freebsd-drivers at emulex.com.
+.Pa freebsd-drivers at emulex.com .
.Sh SEE ALSO
.Xr ifconfig 8
.Sh AUTHORS
@@ -117,4 +133,4 @@ or E-Mail at
The
.Nm
driver was written by
-.An freebsd-drivers at emulex.com.
+.An freebsd-drivers at emulex.com .
More information about the svn-src-all
mailing list