Use consistent terminology in the usage message, the man page

synopsis, and the man page description ("selector" vs. "sel" and
"addr" vs. "reg").

Fix the usage message and man page synopsis to show that the "value"
argument is not optional.
This commit is contained in:
John Polstra 2002-09-17 18:10:39 +00:00
parent f1495caf2d
commit 3915eeb59d
2 changed files with 10 additions and 10 deletions
usr.sbin/pciconf

@ -34,11 +34,11 @@
.Nm
.Fl l Op Fl v
.Nm
.Fl a Ar sel
.Fl a Ar selector
.Nm
.Fl r Oo Fl b | h Oc Ar sel addr Ns Op : Ns Ar addr
.Fl r Oo Fl b | h Oc Ar selector addr Ns Op : Ns Ar addr2
.Nm
.Fl w Oo Fl b | h Oc Ar sel addr Op Ar value
.Fl w Oo Fl b | h Oc Ar selector addr value
.Sh DESCRIPTION
The
.Nm
@ -138,19 +138,19 @@ non-zero indicates that it does not.
The
.Fl r
option reads a configuration space register at byte offset
.Ar reg
.Ar addr
of device
.Ar selector
and prints out its value in hexadecimal.
The optional second
.Ar reg2
The optional second address
.Ar addr2
specifies a range to read.
The
.Fl w
option writes the
.Ar value
into a configuration space register at byte offset
.Ar reg
.Ar addr
of device
.Ar selector .
For both operations, the flags

@ -80,9 +80,9 @@ usage()
{
fprintf(stderr, "%s\n%s\n%s\n%s\n",
"usage: pciconf -l [-v]",
" pciconf -a sel",
" pciconf -r [-b | -h] sel addr[:addr]",
" pciconf -w [-b | -h] sel addr [value]");
" pciconf -a selector",
" pciconf -r [-b | -h] selector addr[:addr2]",
" pciconf -w [-b | -h] selector addr value");
exit (1);
}