Use valid man(7) markup, document OpenBSD device names and explain the
kernel limitation affecting NVMe Security Send and Security Receive.

Index: docs/sedutil-cli.8
--- docs/sedutil-cli.8.orig
+++ docs/sedutil-cli.8
@@ -1,28 +1,29 @@
 .\" Manpage for sedutil-cli.
-.TH SEDUTIL\-CLI 8 "18 Feb 2016" "0.12" "sedutil-cli man page"
+.TH SEDUTIL\-CLI 8 "February 18, 2016" "1.49.13" "sedutil-cli man page"
 .SH NAME
 sedutil-cli \- util to manage TCG Opal 2.0 self encrypting drives
-
 .SH SYNOPSIS
 sedutil\-cli <\-v> <\-n> <action> <options> <device>
-
 .SH DESCRIPTION
 sedutil-cli is a utility to manage self encrypting drives that conform
 to the Trusted Computing Group (TCG) OPAL 2.0 SSC specification.
-
-In Linux libata.allow_tpm must be set to 1. Either via adding
-libata.allow_tpm=1 to the kernel flags at boot time or changing the
-contents of /sys/module/libata/parameters/allow_tpm to a from a
-"0" to a "1" on a running system.
-
+.PP
+On OpenBSD, use the raw whole-disk device, such as
+.I /dev/rsd0c
+or
+.IR /dev/rwd0c .
+Direct device access normally requires root privileges.
+.PP
+OpenBSD supports the required passthrough commands for ATA and SCSI/SAS/SAT
+devices. NVMe disks can be identified, but the kernel currently rejects
+the NVMe Security Send and Security Receive commands required to manage
+their Opal state.
 .SH OPTIONS
 .SS General Options
-.TP
 .IP "\-v (optional)"
 increase verbosity, one to five v's
 .IP "\-n (optional)"
 no password hashing. Passwords will be sent in clear text!
-
 .SS Actions
 .IP \-\-scan
 Scans the devices on the system identifying Opal compliant devices
@@ -45,13 +47,15 @@ Erase a Locking Range, 0 = GLobal 1..n  = LRn
 .IP "\-\-setupLockingRange <0...n> <RangeStart> <RangeLength> <password> <device>"
 Setup a new Locking Range, 0 = GLobal 1..n  = LRn
 .IP "\-\-initialSetup <SIDpassword> <device>"
-Setup the device for use with sedutil, <SIDpassword> is new SID and Admin1 password
+Setup the device for use with sedutil; <SIDpassword> is the new SID and
+Admin1 password.
 .IP "\-\-setSIDPassword <SIDpassword> <newSIDpassword> <device>"
 Change the SID password
 .IP "\-\-setAdmin1Pwd <Admin1password> <newAdmin1password> <device>"
 Change the Admin1 password
 .IP "\-\-setPassword <oldpassword, "" for MSID> <userid> <newpassword> <device>"
-Change the Enterprise password for userid, "EraseMaster" or "BandMaster<n>", 0 <= n <= 1023
+Change the Enterprise password for userid, "EraseMaster" or
+"BandMaster<n>", 0 <= n <= 1023.
 .IP "\-\-setLockingRange <0...n> <RW|RO|LK> <Admin1password> <device>"
 Set the status of a Locking Range, 0 = GLobal 1..n  = LRn
 .IP "\-\-enableLockingRange <0...n> <Admin1password> <device>"
@@ -70,27 +75,27 @@ set the device back to factory defaults.
 .IP "\-\-revertNoErase <Admin1password> <device>"
 deactivate the Locking SP without erasing the data on GLOBAL RANGE *ONLY*
 .IP "\-\---yesIreallywanttoERASEALLmydatausingthePSID <PSID> <device>"
-revert the device using the PSID. 
+revert the device using the PSID.
 .B *ERASING* *ALL* the data
 .IP "\-\-printDefaultPassword <device>"
 print MSID
-
 .SH EXAMPLES
 .EX
 sedutil-cli --scan
 .EE
 .EX
-sedutil-cli --query /dev/sdc
+sedutil-cli --query /dev/rsd0c
 .EE
 .EX
-sedutil-cli --yesIreallywanttoERASEALLmydatausingthePSID <PSIDALLCAPSNODASHED> /dev/sdc
+sedutil-cli --yesIreallywanttoERASEALLmydatausingthePSID <PSIDALLCAPSNODASHED> /dev/rsd0c
 .EE
 .EX
-sedutil-cli --initialSetup <newSIDpassword> /dev/sdc
+sedutil-cli --initialSetup <newSIDpassword> /dev/rsd0c
 .EE
-
 .SH BUGS
 Sleep (S3) is not supported.
-
 .SH AUTHOR
-The tool was developed by Bright Plaza Inc. <drivetrust@drivetrust.com>. This man page was written by Jan Luca Naumann <j.naumann@fu-berlin.de>.
+The tool was developed by Bright Plaza Inc.
+<drivetrust@drivetrust.com>.
+This man page was written by Jan Luca Naumann
+<j.naumann@fu-berlin.de>.
