mdoc: reorder sections consistently
This commit is contained in:
parent
1c9f17fc8b
commit
75c697f88d
@ -150,6 +150,9 @@ facility is a non-standard extension, which appeared in
|
||||
the GNU implementation and was adopted in
|
||||
.Fx 9
|
||||
for compatibility's sake.
|
||||
.Sh AUTHORS
|
||||
This manual page was written by
|
||||
.An Gabor Kovesdan Aq gabor@FreeBSD.org .
|
||||
.Sh BUGS
|
||||
Transliteration is enabled in this implementation by default, so it
|
||||
is impossible by design to turn it off.
|
||||
@ -157,6 +160,3 @@ Accordingly, trying to turn it off will always fail and \-1 will be
|
||||
returned.
|
||||
Getting the transliteration state will always succeed and indicate
|
||||
that it is turned on, though.
|
||||
.Sh AUTHORS
|
||||
This manual page was written by
|
||||
.An Gabor Kovesdan Aq gabor@FreeBSD.org .
|
||||
|
@ -142,9 +142,6 @@ The
|
||||
.Nm
|
||||
driver first appeared in
|
||||
.Fx 8.1 .
|
||||
.Sh CAVEATS
|
||||
Some LP PHY devices have DMA operation problems that in that case try to
|
||||
use PIO mode.
|
||||
.Sh AUTHORS
|
||||
.An -nosplit
|
||||
The
|
||||
@ -155,3 +152,6 @@ driver was written by
|
||||
.\".Sh BUGS
|
||||
.\"Some card based on the BCM4306 and BCM4309 chips do not work properly
|
||||
.\"on channel 1, 2 and 3.
|
||||
.Sh CAVEATS
|
||||
Some LP PHY devices have DMA operation problems that in that case try to
|
||||
use PIO mode.
|
||||
|
@ -227,6 +227,20 @@ If
|
||||
is non-zero, this tunable limits the maximum delay in which a transmit
|
||||
interrupt is generated.
|
||||
.El
|
||||
.Sh FILES
|
||||
.Bl -tag -width /dev/led/em*
|
||||
.It Pa /dev/led/em*
|
||||
identification LED device nodes
|
||||
.El
|
||||
.Sh EXAMPLES
|
||||
Make the identification LED of em0 blink:
|
||||
.Pp
|
||||
.Dl "echo f2 > /dev/led/em0"
|
||||
.Pp
|
||||
Turn the identification LED of em0 off again:
|
||||
.Pp
|
||||
.Dl "echo 0 > /dev/led/em0"
|
||||
.Pp
|
||||
.Sh DIAGNOSTICS
|
||||
.Bl -diag
|
||||
.It "em%d: Unable to allocate bus resource: memory"
|
||||
@ -246,20 +260,6 @@ If an issue is identified with the released source code on the supported kernel
|
||||
with a supported adapter, email the specific information related to the
|
||||
issue to
|
||||
.Aq freebsdnic@mailbox.intel.com .
|
||||
.Sh FILES
|
||||
.Bl -tag -width /dev/led/em*
|
||||
.It Pa /dev/led/em*
|
||||
identification LED device nodes
|
||||
.El
|
||||
.Sh EXAMPLES
|
||||
Make the identification LED of em0 blink:
|
||||
.Pp
|
||||
.Dl "echo f2 > /dev/led/em0"
|
||||
.Pp
|
||||
Turn the identification LED of em0 off again:
|
||||
.Pp
|
||||
.Dl "echo 0 > /dev/led/em0"
|
||||
.Pp
|
||||
.Sh SEE ALSO
|
||||
.Xr altq 4 ,
|
||||
.Xr arp 4 ,
|
||||
|
@ -161,6 +161,20 @@ The minimum is 80, and the maximum is 4096.
|
||||
If set to 1, enable Adaptive Interrupt Moderation.
|
||||
The default is to enable Adaptive Interrupt Moderation.
|
||||
.El
|
||||
.Sh FILES
|
||||
.Bl -tag -width /dev/led/igb*
|
||||
.It Pa /dev/led/igb*
|
||||
identification LED device nodes
|
||||
.El
|
||||
.Sh EXAMPLES
|
||||
Make the identification LED of igb0 blink:
|
||||
.Pp
|
||||
.Dl "echo f2 > /dev/led/igb0"
|
||||
.Pp
|
||||
Turn the identification LED of igb0 off again:
|
||||
.Pp
|
||||
.Dl "echo 0 > /dev/led/igb0"
|
||||
.Pp
|
||||
.Sh DIAGNOSTICS
|
||||
.Bl -diag
|
||||
.It "igb%d: Unable to allocate bus resource: memory"
|
||||
@ -180,20 +194,6 @@ If an issue is identified with the released source code on the supported kernel
|
||||
with a supported adapter, email the specific information related to the
|
||||
issue to
|
||||
.Aq freebsdnic@mailbox.intel.com .
|
||||
.Sh FILES
|
||||
.Bl -tag -width /dev/led/igb*
|
||||
.It Pa /dev/led/igb*
|
||||
identification LED device nodes
|
||||
.El
|
||||
.Sh EXAMPLES
|
||||
Make the identification LED of igb0 blink:
|
||||
.Pp
|
||||
.Dl "echo f2 > /dev/led/igb0"
|
||||
.Pp
|
||||
Turn the identification LED of igb0 off again:
|
||||
.Pp
|
||||
.Dl "echo 0 > /dev/led/igb0"
|
||||
.Pp
|
||||
.Sh SEE ALSO
|
||||
.Xr altq 4 ,
|
||||
.Xr arp 4 ,
|
||||
|
@ -143,6 +143,19 @@ Enable prints for controller events.
|
||||
.Xr sa 4 ,
|
||||
.Xr scsi 4 ,
|
||||
.Xr targ 4
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
driver first appeared in
|
||||
.Fx 9.0 .
|
||||
.Sh AUTHORS
|
||||
.An -nosplit
|
||||
The
|
||||
.Nm
|
||||
driver was originally written by
|
||||
.An Scott Long Aq scottl@FreeBSD.org .
|
||||
This man page was written by
|
||||
.An Ken Merry Aq ken@FreeBSD.org .
|
||||
.Sh BUGS
|
||||
This driver is still in development, it has only been tested on the amd64
|
||||
architecture and has some known shortcomings:
|
||||
@ -158,16 +171,3 @@ times, without user intervention.
|
||||
.It
|
||||
The error recovery code isn't complete.
|
||||
.El
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
driver first appeared in
|
||||
.Fx 9.0 .
|
||||
.Sh AUTHORS
|
||||
.An -nosplit
|
||||
The
|
||||
.Nm
|
||||
driver was originally written by
|
||||
.An Scott Long Aq scottl@FreeBSD.org .
|
||||
This man page was written by
|
||||
.An Ken Merry Aq ken@FreeBSD.org .
|
||||
|
@ -57,11 +57,6 @@ To get mouse working in
|
||||
.Xr X 7 ,
|
||||
one needs to install
|
||||
.Pa ports/x11-drivers/xf86-input-egalax .
|
||||
.Sh BUGS
|
||||
.Nm
|
||||
can't act like
|
||||
.Xr sysmouse 4 ,
|
||||
since the latter does not support absolute motion events.
|
||||
.Sh FILES
|
||||
.Nm
|
||||
creates a blocking pseudo\-device file,
|
||||
@ -77,3 +72,8 @@ The
|
||||
.Nm
|
||||
driver was written by
|
||||
.An Gleb Smirnoff Aq glebius@FreeBSD.org
|
||||
.Sh BUGS
|
||||
.Nm
|
||||
can't act like
|
||||
.Xr sysmouse 4 ,
|
||||
since the latter does not support absolute motion events.
|
||||
|
@ -80,9 +80,6 @@ ST Lab U-400 four-port serial USB adapter
|
||||
.Xr tty 4 ,
|
||||
.Xr ucom 4 ,
|
||||
.Xr usb 4
|
||||
.Sh BUGS
|
||||
This driver doesn't support access to any fine tunes of
|
||||
chip, like RS522/RS485 mode, non-standard baudrates, etc.
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
@ -95,3 +92,6 @@ The
|
||||
driver was written by
|
||||
.An Lev Serebryakov
|
||||
.Aq lev@FreeBSD.org .
|
||||
.Sh BUGS
|
||||
This driver doesn't support access to any fine tunes of
|
||||
chip, like RS522/RS485 mode, non-standard baudrates, etc.
|
||||
|
@ -67,6 +67,15 @@ It is the caller's responsibility to enforce any such requirements.
|
||||
The
|
||||
.Fn bus_adjust_resource
|
||||
method returns zero on success or an error code on failure.
|
||||
.Sh EXAMPLES
|
||||
Grow an existing memory resource by 4096 bytes.
|
||||
.Bd -literal
|
||||
struct resource *res;
|
||||
int error;
|
||||
|
||||
error = bus_adjust_resource(dev, SYS_RES_MEMORY, res,
|
||||
rman_get_start(res), rman_get_end(res) + 0x1000);
|
||||
.Ed
|
||||
.Sh ERRORS
|
||||
.Fn bus_adjust_resource
|
||||
will fail if:
|
||||
@ -85,15 +94,6 @@ The new address range does not overlap with the existing address range of
|
||||
.It Bq Er EBUSY
|
||||
The new address range conflicts with another allocated resource.
|
||||
.El
|
||||
.Sh EXAMPLES
|
||||
Grow an existing memory resource by 4096 bytes.
|
||||
.Bd -literal
|
||||
struct resource *res;
|
||||
int error;
|
||||
|
||||
error = bus_adjust_resource(dev, SYS_RES_MEMORY, res,
|
||||
rman_get_start(res), rman_get_end(res) + 0x1000);
|
||||
.Ed
|
||||
.Sh SEE ALSO
|
||||
.Xr bus_alloc_resource 9 ,
|
||||
.Xr bus_release_resource 9 ,
|
||||
|
@ -33,3 +33,4 @@
|
||||
.\" .Sh HISTORY
|
||||
.\" .Sh AUTHORS
|
||||
.\" .Sh BUGS
|
||||
.\" .Sh SECURITY CONSIDERATIONS
|
||||
|
@ -185,22 +185,6 @@ function switches terminal emulation to
|
||||
which is used by versions of
|
||||
.Fx
|
||||
prior to 9.0.
|
||||
.Sh SECURITY CONSIDERATIONS
|
||||
The
|
||||
.Fn tf_respond
|
||||
callback is used to respond to device status requests commands generated
|
||||
by an application.
|
||||
In the past, there have been various security issues, where a malicious
|
||||
application sends a device status request before termination, causing
|
||||
the generated response to be interpreted by applications such as
|
||||
.Xr sh 1 .
|
||||
.Pp
|
||||
.Nm
|
||||
only implements a small subset of responses which are unlikely to cause
|
||||
any harm.
|
||||
Still, it is advised to leave
|
||||
.Fn tf_respond
|
||||
unimplemented.
|
||||
.Sh SEE ALSO
|
||||
.Xr ncurses 3 ,
|
||||
.Xr termcap 3 ,
|
||||
@ -218,3 +202,19 @@ the
|
||||
library appeared in userspace.
|
||||
.Sh AUTHORS
|
||||
.An Ed Schouten Aq ed@FreeBSD.org
|
||||
.Sh SECURITY CONSIDERATIONS
|
||||
The
|
||||
.Fn tf_respond
|
||||
callback is used to respond to device status requests commands generated
|
||||
by an application.
|
||||
In the past, there have been various security issues, where a malicious
|
||||
application sends a device status request before termination, causing
|
||||
the generated response to be interpreted by applications such as
|
||||
.Xr sh 1 .
|
||||
.Pp
|
||||
.Nm
|
||||
only implements a small subset of responses which are unlikely to cause
|
||||
any harm.
|
||||
Still, it is advised to leave
|
||||
.Fn tf_respond
|
||||
unimplemented.
|
||||
|
@ -130,6 +130,16 @@ The
|
||||
.Nm
|
||||
utility is expected to conform to
|
||||
.St -p1003.1-2004 .
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
utility appeared in
|
||||
.Fx 9.0 .
|
||||
.Sh AUTHORS
|
||||
The
|
||||
.Nm
|
||||
utility and this manual page was written by
|
||||
.An Stanislav Sedov Aq stas@FreeBSD.org .
|
||||
.Sh BUGS
|
||||
Since
|
||||
.Nm
|
||||
@ -141,13 +151,3 @@ interface the report will be limited to filesystems the
|
||||
.Nm
|
||||
utility knows about (currently only cd9660, devfs, nfs, ntfs, nwfs, udf,
|
||||
ufs and zfs).
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
utility appeared in
|
||||
.Fx 9.0 .
|
||||
.Sh AUTHORS
|
||||
The
|
||||
.Nm
|
||||
utility and this manual page was written by
|
||||
.An Stanislav Sedov Aq stas@FreeBSD.org .
|
||||
|
Loading…
Reference in New Issue
Block a user