From 3174c2c63e5cd6a839c04d16f78cb09d64a98a3e Mon Sep 17 00:00:00 2001
From: Sascha Wildner <saw@online.de>
Date: Sun, 7 Aug 2016 18:21:00 +0200
Subject: [PATCH 8/8] i386 removal, part 56/x: Remove old i386 specific manual
 pages.

Shuffle a number of them to share/man/man4 because they didn't seem to
be i386 specific for one reason or another.
---
 share/man/man4/Makefile                |   5 +
 share/man/man4/{man4.i386 => }/digi.4  |   2 +-
 share/man/man4/{man4.i386 => }/io.4    |   5 +-
 share/man/man4/man4.i386/Makefile      |  38 ----
 share/man/man4/man4.i386/ar.4          | 123 -------------
 share/man/man4/man4.i386/cs.4          | 107 ------------
 share/man/man4/man4.i386/cy.4          | 204 ----------------------
 share/man/man4/man4.i386/ed.4          | 161 -----------------
 share/man/man4/man4.i386/ep.4          |  92 ----------
 share/man/man4/man4.i386/ex.4          |  72 --------
 share/man/man4/man4.i386/fe.4          | 309 ---------------------------------
 share/man/man4/man4.i386/glxsb.4       |  97 -----------
 share/man/man4/man4.i386/linux.4       | 124 -------------
 share/man/man4/man4.i386/longrun.4     |  67 -------
 share/man/man4/man4.i386/npx.4         |  95 ----------
 share/man/man4/man4.i386/perfmon.4     | 204 ----------------------
 share/man/man4/man4.i386/pnp.4         | 195 ---------------------
 share/man/man4/man4.i386/pnpbios.4     |  89 ----------
 share/man/man4/man4.i386/pst.4         |  65 -------
 share/man/man4/man4.i386/sbni.4        |  74 --------
 share/man/man4/man4.i386/spic.4        |  60 -------
 share/man/man4/man4.i386/sr.4          | 141 ---------------
 share/man/man4/man4.i386/stl.4         |  86 ---------
 share/man/man4/man4.i386/vx.4          | 108 ------------
 share/man/man4/{man4.i386 => }/tx.4    |   3 +-
 share/man/man4/{man4.i386 => }/viapm.4 |   6 +-
 sys/config/LINT64                      |   4 +-
 27 files changed, 13 insertions(+), 2523 deletions(-)
 rename share/man/man4/{man4.i386 => }/digi.4 (99%)
 rename share/man/man4/{man4.i386 => }/io.4 (93%)
 delete mode 100644 share/man/man4/man4.i386/Makefile
 delete mode 100644 share/man/man4/man4.i386/ar.4
 delete mode 100644 share/man/man4/man4.i386/cs.4
 delete mode 100644 share/man/man4/man4.i386/cy.4
 delete mode 100644 share/man/man4/man4.i386/ed.4
 delete mode 100644 share/man/man4/man4.i386/ep.4
 delete mode 100644 share/man/man4/man4.i386/ex.4
 delete mode 100644 share/man/man4/man4.i386/fe.4
 delete mode 100644 share/man/man4/man4.i386/glxsb.4
 delete mode 100644 share/man/man4/man4.i386/linux.4
 delete mode 100644 share/man/man4/man4.i386/longrun.4
 delete mode 100644 share/man/man4/man4.i386/npx.4
 delete mode 100644 share/man/man4/man4.i386/perfmon.4
 delete mode 100644 share/man/man4/man4.i386/pnp.4
 delete mode 100644 share/man/man4/man4.i386/pnpbios.4
 delete mode 100644 share/man/man4/man4.i386/pst.4
 delete mode 100644 share/man/man4/man4.i386/sbni.4
 delete mode 100644 share/man/man4/man4.i386/spic.4
 delete mode 100644 share/man/man4/man4.i386/sr.4
 delete mode 100644 share/man/man4/man4.i386/stl.4
 delete mode 100644 share/man/man4/man4.i386/vx.4
 rename share/man/man4/{man4.i386 => }/tx.4 (96%)
 rename share/man/man4/{man4.i386 => }/viapm.4 (94%)

diff --git a/share/man/man4/Makefile b/share/man/man4/Makefile
index 338a850..da84ed8 100644
--- a/share/man/man4/Makefile
+++ b/share/man/man4/Makefile
@@ -79,6 +79,7 @@ MAN=	aac.4 \
 	ddb.4 \
 	de.4 \
 	devctl.4 \
+	digi.4 \
 	disc.4 \
 	divert.4 \
 	dm.4 \
@@ -131,6 +132,7 @@ MAN=	aac.4 \
 	inet6.4 \
 	intpm.4 \
 	intro.4 \
+	io.4 \
 	ip.4 \
 	ip6.4 \
 	ipfirewall.4 \
@@ -336,6 +338,7 @@ MAN=	aac.4 \
 	twa.4 \
 	twe.4 \
 	tws.4 \
+	tx.4 \
 	txp.4 \
 	uark.4 \
 	ubsa.4 \
@@ -382,6 +385,7 @@ MAN=	aac.4 \
 	uvscom.4 \
 	vga.4 \
 	vge.4 \
+	viapm.4 \
 	vinum.4 \
 	virtio.4 \
 	virtio_blk.4 \
@@ -541,6 +545,7 @@ MLINKS+=tap.4 if_tap.4
 MLINKS+=ti.4 if_ti.4
 MLINKS+=tl.4 if_tl.4
 MLINKS+=tun.4 if_tun.4
+MLINKS+=tx.4 if_tx.4
 MLINKS+=txp.4 if_txp.4
 MLINKS+=udav.4 if_udav.4
 MLINKS+=upmap.4 kpmap.4
diff --git a/share/man/man4/man4.i386/digi.4 b/share/man/man4/digi.4
similarity index 99%
rename from share/man/man4/man4.i386/digi.4
rename to share/man/man4/digi.4
index 636384d..fad61ce 100644
--- a/share/man/man4/man4.i386/digi.4
+++ b/share/man/man4/digi.4
@@ -34,7 +34,7 @@
 .\" $FreeBSD: src/share/man/man4/man4.i386/dgb.4,v 1.13.2.6 2001/08/17 13:08:45 ru Exp $
 .\"
 .Dd August 6, 2009
-.Dt DIGI 4 i386
+.Dt DIGI 4
 .Os
 .Sh NAME
 .Nm digi
diff --git a/share/man/man4/man4.i386/io.4 b/share/man/man4/io.4
similarity index 93%
rename from share/man/man4/man4.i386/io.4
rename to share/man/man4/io.4
index c3bf2b6..2cc4f08 100644
--- a/share/man/man4/man4.i386/io.4
+++ b/share/man/man4/io.4
@@ -26,10 +26,9 @@
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
 .\" $FreeBSD: src/share/man/man4/man4.i386/io.4,v 1.6.2.4 2001/09/22 19:58:01 iedowse Exp $
-.\" $DragonFly: src/share/man/man4/man4.i386/io.4,v 1.2 2003/06/17 04:36:59 dillon Exp $
 .\"
 .Dd January 1, 1996
-.Dt IO 4 i386
+.Dt IO 4
 .Os
 .Sh NAME
 .Nm io
@@ -57,8 +56,6 @@ the kernel enforces that only the super-user may open this device.
 .It Pa /dev/io
 .El
 .Sh SEE ALSO
-.Xr i386_get_ioperm 2 ,
-.Xr i386_set_ioperm 2 ,
 .Xr mem 4
 .Sh HISTORY
 The
diff --git a/share/man/man4/man4.i386/Makefile b/share/man/man4/man4.i386/Makefile
deleted file mode 100644
index 379f475..0000000
--- a/share/man/man4/man4.i386/Makefile
+++ /dev/null
@@ -1,38 +0,0 @@
-# $FreeBSD: src/share/man/man4/man4.i386/Makefile,v 1.122.2.12 2003/04/15 17:23:32 fjoe Exp $
-
-MAN=	ar.4 \
-	cs.4 \
-	cy.4 \
-	digi.4 \
-	ed.4 \
-	ep.4 \
-	ex.4 \
-	fe.4 \
-	glxsb.4 \
-	io.4 \
-	linux.4 \
-	longrun.4 \
-	npx.4 \
-	perfmon.4 \
-	pnp.4 \
-	pnpbios.4 \
-	pst.4 \
-	sbni.4 \
-	spic.4 \
-	sr.4 \
-	stl.4 \
-	tx.4 \
-	viapm.4 \
-	vx.4
-
-MLINKS+=ar.4 if_ar.4
-MLINKS+=ed.4 if_ed.4
-MLINKS+=ep.4 if_ep.4
-MLINKS+=sbni.4 if_sbni.4
-MLINKS+=sr.4 if_sr.4
-MLINKS+=tx.4 if_tx.4
-MLINKS+=vx.4 if_vx.4
-
-MANSUBDIR=/i386
-
-.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.i386/ar.4 b/share/man/man4/man4.i386/ar.4
deleted file mode 100644
index efea056..0000000
--- a/share/man/man4/man4.i386/ar.4
+++ /dev/null
@@ -1,123 +0,0 @@
-.\"
-.\" Copyright (c) 1995, 1999 John Hay.  All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\" 3. Neither the name of the author nor the names of any co-contributors
-.\"    may be used to endorse or promote products derived from this software
-.\"    without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY John Hay ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL John Hay BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/ar.4,v 1.17.2.4 2001/08/17 13:08:45 ru Exp $
-.\"
-.Dd November 19, 1995
-.Dt AR 4 i386
-.Os
-.Sh NAME
-.Nm ar
-.Nd synchronous Digi/Arnet device driver
-.Sh SYNOPSIS
-.Cd "device ar"
-.Pp
-.Cd "pseudo-device sppp"
-.Sh DESCRIPTION
-The
-.Nm
-driver supports the Digi/Arnet SYNC/570i PCI cards that is based on the
-HD64570 chip.
-Both the 2 and 4 port cards are supported and auto detected.
-.Pp
-The standard
-.Dx
-sppp code is used for the link level layer.
-The
-default protocol used is PPP.
-The Cisco HDLC protocol can be used by
-adding
-.Ar link2
-to
-.Xr ifconfig 8 .
-.Pp
-Alternately, the driver can be compiled to support
-.Xr netgraph 4
-(see below).
-.Sh NUMBERING
-Only one line for each card is needed in the kernel configuration file.
-The first card's ports will be installed from ar0. The numbering of the
-next card will continue where the first stopped, eg. if the first card
-is a two port card it will use ar0 and ar1. The next card will then
-start at ar2.
-.Pp
-The card only supports IRQ 3, 5, 7, 10, 11, 12 and 15.
-.Pp
-The iomem area is a 16Kb block and must start at a 16Kb boundary.
-.Sh NETGRAPH SUPPORT
-If the kernel is compiled with
-.Cd "options NETGRAPH"
-then the sppp and Cisco HDLC modes are disabled (and the sppp driver
-is unneeded), and this driver functions as a
-.Xr netgraph 4
-node with a single hook named
-.Dv rawdata .
-Connecting to this hook enables the transmission of raw HDLC frames.
-The node will have the same name as the device with ``sync_''
-prepended, e.g.,
-.Dv sync_ar0 .
-.Sh FILES
-.Bl -tag -width /sys/platform/pc32/isa/ic/hd64570.h -compact
-.It Pa /sys/dev/netif/ar/if_ar.c
-.It Pa /sys/dev/netif/ar/if_ar.h
-.It Pa /sys/dev/netif/ar/if_ar_pci.c
-.It Pa /sys/dev/netif/ar/if_arregs.h
-.It Pa /sys/platform/pc32/isa/ic/hd64570.h
-.El
-.Sh DIAGNOSTICS
-.Bl -diag
-.It "ar%d: Warning illegal interrupt %d."
-The card cannot use the specified interrupt.
-Choose a different one.
-.El
-.Sh SEE ALSO
-.Xr netgraph 4 ,
-.Xr netintro 4 ,
-.Xr sr 4 ,
-.Xr ifconfig 8
-.Sh HISTORY
-The
-.Nm
-device driver first appeared in
-.Fx 2.2 .
-.Sh AUTHORS
-.An -nosplit
-The
-.Nm
-device driver was written by
-.An John Hay Aq Mt jhay@FreeBSD.org .
-Netgraph support was added by
-.An Julian Elischer Aq Mt julian@FreeBSD.org .
-.Sh BUGS
-At the moment only the V.35 and X.21 interfaces are tested.
-The others
-may need tweaks to the clock selection code.
-.Pp
-The code can probably stand some optimizing.
-.Pp
-Please report bugs to
-.Aq Mt jhay@FreeBSD.org .
diff --git a/share/man/man4/man4.i386/cs.4 b/share/man/man4/man4.i386/cs.4
deleted file mode 100644
index 8d616d9..0000000
--- a/share/man/man4/man4.i386/cs.4
+++ /dev/null
@@ -1,107 +0,0 @@
-.\"
-.\" Copyright (c) 1998 Michael Smith
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/cs.4,v 1.6.2.5 2001/08/17 13:08:45 ru Exp $
-.\"
-.Dd July 20, 1998
-.Dt CS 4 i386
-.Os
-.Sh NAME
-.Nm cs
-.Nd Crystal Semiconductor CS8900 and CS8920 ethernet device driver
-.Sh SYNOPSIS
-.Cd "device cs"
-.Sh DESCRIPTION
-The
-.Nm
-driver provides support for ethernet adapters based on the
-.Tn Crystal Semiconductor CS8900
-and
-.Tn CS8920
-NICs.  These devices are used on the
-.Tn IBM EtherJet PCMCIA
-adapters and in many embedded applications where the high integration, small
-size and low cost of the CS89x0 family compensate for their drawbacks.
-.Pp
-The
-.Nm
-driver will obtain configuration parameters from the card.
-Parameters specified in the configuration entry will be
-used if present; the card may be soft-configured so these may be any valid
-value.
-The driver will detect the
-.Tn IBM EtherJet
-adapters automatically.
-.Pp
-Memory-mapped and DMA operation are not supported at this time.
-.Sh DIAGNOSTICS
-.Bl -diag
-.It "cs%d: full/half duplex negotiation timeout"
-The attempt to negotiate duplex settings with the hub timed out.  This may
-indicate a cabling problem or a faulty or incompatible hub.
-.It "cs%d: failed to enable <media>"
-The CS89x0 failed to select the nominated media, either because it is not
-present or not operating correctly.
-.It "cs%d: No EEPROM, assuming defaults"
-The CS89x0 does not have an EEPROM, or the EEPROM is hopelessly damaged.  Operation
-will only be successful if the configuration entry lists suitable values for
-the adapter.
-.It "cs%d: Invalid irq"
-The IRQ specified in the configuration entry is not valid for the adapter.
-.It "cs%d: Could not allocate memory for NIC"
-There is a critical memory shortage.  The adapter will not function.
-.It "cs%d: Adapter has no media"
-The adapter is not configured for a specific media type.
-The media type will have
-to be manually set.
-.It "This is a %s, but LDN %d is disabled"
-The PnP probe code found a recognised adapter, but the adapter is disabled.
-.It "failed to read pnp parms"
-A PnP adapter was found, but configuration parameters for it could not be read.
-.It "failed to pnp card parametars"
-The parameters obtained via PnP were not accepted by the driver.  The adapter
-may not function.
-.El
-.Sh CAVEATS
-The CS89x0 family of adapters have a very small RAM buffer (4K).  This may
-cause problems with extremely high network loads or bursty network traffic.
-In particular, NFS operations should be limited to 1k read/write transactions
-in order to avoid overruns.
-.Sh SEE ALSO
-.Xr arp 4 ,
-.Xr ifmedia 4 ,
-.Xr netintro 4 ,
-.Xr ng_ether 4 ,
-.Xr ifconfig 8
-.Sh AUTHORS
-.An -nosplit
-The
-.Nm
-device driver was written by
-.An Maxim Bolotin
-and
-.An Oleg Sharoiko .
-This manpage was written by
-.An Michael Smith .
diff --git a/share/man/man4/man4.i386/cy.4 b/share/man/man4/man4.i386/cy.4
deleted file mode 100644
index c0e8ab6..0000000
--- a/share/man/man4/man4.i386/cy.4
+++ /dev/null
@@ -1,204 +0,0 @@
-.\" Copyright (c) 1990, 1991 The Regents of the University of California.
-.\" All rights reserved.
-.\"
-.\" This code is derived from software contributed to Berkeley by
-.\" the Systems Programming Group of the University of Utah Computer
-.\" Science Department.
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\" 3. Neither the name of the University nor the names of its contributors
-.\"    may be used to endorse or promote products derived from this software
-.\"    without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\"     from: @(#)dca.4	5.2 (Berkeley) 3/27/91
-.\"	from: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp
-.\"	from: sio.4,v 1.16 1995/06/26 06:05:30 bde Exp $
-.\" $FreeBSD: src/share/man/man4/man4.i386/cy.4,v 1.13.2.2 2001/08/17 13:08:45 ru Exp $
-.\"
-.Dd June 14, 1999
-.Dt CY 4 i386
-.Os
-.Sh NAME
-.Nm cy
-.Nd Cyclades Cyclom-Y serial driver
-.Sh SYNOPSIS
-.Cd "device cy"
-.Pp
-Minor numbering:
-.Bd -literal
-0b\fIMMMMMMMMMMMMMMMMxxxxxxxxOLIMMMMM\fR
-                          call\fBO\fRut
-                           \fBL\fRock
-                            \fBI\fRnitial
-  \fBMMMMMMMMMMMMMMMM           MMMMMM\fRinor
-.Ed
-.Sh DESCRIPTION
-The
-.Nm
-driver provides support for Cirrus Logic CD1400-based
-.Tn EIA
-.Tn RS-232C
-.Pf ( Tn CCITT
-.Tn V.24 )
-communications interfaces (ports) on Cyclades Cyclom-Y boards.
-Each CD1400 provides 4 ports.
-Cyclom-Y boards with various numbers of CD1400's are available.
-This driver supports up to 8 CD1400's (32 ports) per board.
-.Pp
-Input and output for each line may set independently
-to the following speeds:
-50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600,
-19200, 38400, 57600, or 115200 bps.
-Other speeds of up to 150000 are supported by the termios interface
-but not by the sgttyb compatibility interface.
-The CD1400 is not fast enough to handle speeds above 115200 bps
-effectively.
-It can transmit on a single line at slightly more than 115200 bps,
-but when 4 lines are active in both directions its limit is about
-90000 bps on each line.
-.\" XXX the following should be true for all serial drivers and
-.\" should not be repeated in the man pages for all serial drivers.
-.\" It was copied from sio.4.  The only change was s/sio/cy/g.
-.Pp
-Serial ports controlled by the
-.Nm
-driver can be used for both `callin' and `callout'.
-For each port there is a callin device and a callout device.
-The minor number of the callout device is 128 higher
-than that of the corresponding callin port.
-The callin device is general purpose.
-Processes opening it normally wait for carrier
-and for the callout device to become inactive.
-The callout device is used to steal the port from
-processes waiting for carrier on the callin device.
-Processes opening it do not wait for carrier
-and put any processes waiting for carrier on the callin device into
-a deeper sleep so that they do not conflict with the callout session.
-The callout device is abused for handling programs that are supposed
-to work on general ports and need to open the port without waiting
-but are too stupid to do so.
-.Pp
-The
-.Nm
-driver also supports an initial-state and a lock-state control
-device for each of the callin and the callout "data" devices.
-The minor number of the initial-state device is 32 higher
-than that of the corresponding data device.
-The minor number of the lock-state device is 64 higher
-than that of the corresponding data device.
-The termios settings of a data device are copied
-from those of the corresponding initial-state device
-on first opens and are not inherited from previous opens.
-Use
-.Xr stty 1
-in the normal way on the initial-state devices to program
-initial termios states suitable for your setup.
-.Pp
-The lock termios state acts as flags to disable changing
-the termios state.  E.g., to lock a flag variable such as
-CRTSCTS, use
-.Em "stty crtscts"
-on the lock-state device.  Speeds and special characters
-may be locked by setting the corresponding value in the lock-state
-device to any nonzero value.
-.Pp
-Correct programs talking to correctly wired external devices
-work with almost arbitrary initial states and almost no locking,
-but other setups may benefit from changing some of the default
-initial state and locking the state.
-In particular, the initial states for non (POSIX) standard flags
-should be set to suit the devices attached and may need to be
-locked to prevent buggy programs from changing them.
-E.g., CRTSCTS should be locked on for devices that support
-RTS/CTS handshaking at all times and off for devices that don't
-support it at all.  CLOCAL should be locked on for devices
-that don't support carrier.  HUPCL may be locked off if you don't
-want to hang up for some reason.  In general, very bad things happen
-if something is locked to the wrong state, and things should not
-be locked for devices that support more than one setting.  The
-CLOCAL flag on callin ports should be locked off for logins
-to avoid certain security holes, but this needs to be done by
-getty if the callin port is used for anything else.
-.Sh FILES
-.\" XXX more cloning: s/d/c/g and add a ? for the card number.
-.Bl -tag -width /dev/ttyic?? -compact
-.It Pa /dev/ttyc??
-for callin ports
-.It Pa /dev/ttyic??
-.It Pa /dev/ttylc??
-corresponding callin initial-state and lock-state devices
-.Pp
-.\" XXX more cloning: s/a/c/g.  No consistency :-(.
-.It Pa /dev/cuac??
-for callout ports
-.It Pa /dev/cuaic??
-.It Pa /dev/cualc??
-corresponding callout initial-state and lock-state devices
-.El
-.Pp
-.Bl -tag -width /etc/rc.d/serial -compact
-.It Pa /etc/rc.d/serial
-examples of setting the initial-state and lock-state devices
-.El
-.Pp
-The first question mark in these device names is short for the
-card number
-(a decimal number between 0 and 65535 inclusive).
-The second question mark is short for the port number
-(a letter in the range [0-9a-v]).
-.Sh DIAGNOSTICS
-.Bl -diag
-.\" XXX back to s/sio/cy/g.
-.It cy%d: silo overflow.
-Problem in the interrupt handler.
-.El
-.Bl -diag
-.It cy%d: interrupt-level buffer overflow.
-Problem in the bottom half of the driver.
-.El
-.Bl -diag
-.It cy%d: tty-level buffer overflow.
-Problem in the application.
-Input has arrived faster than the given module could process it
-and some has been lost.
-.El
-.\" .Bl -diag
-.\" .It sio%d: reduced fifo trigger level to %d.
-.\" Attempting to avoid further silo overflows.
-.\" .El
-.Sh SEE ALSO
-.Xr stty 1 ,
-.Xr termios 4 ,
-.Xr tty 4 ,
-.Xr comcontrol 8 ,
-.Xr pstat 8
-.Sh HISTORY
-The
-.Nm
-driver is derived from the
-.Nm sio
-driver and the
-.Nx
-.Nm
-driver and is
-.Ud
-.Sh BUGS
-Serial consoles are not implemented.
diff --git a/share/man/man4/man4.i386/ed.4 b/share/man/man4/man4.i386/ed.4
deleted file mode 100644
index 9635763..0000000
--- a/share/man/man4/man4.i386/ed.4
+++ /dev/null
@@ -1,161 +0,0 @@
-.\"
-.\" Copyright (c) 1994, David Greenman
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\"    must display the following acknowledgement:
-.\"	This product includes software developed by David Greenman.
-.\" 4. The name of the author may not be used to endorse or promote products
-.\"    derived from this software without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/ed.4,v 1.19.2.10 2003/02/17 21:20:39 trhodes Exp $
-.\"
-.Dd October 28, 1995
-.Dt ED 4 i386
-.Os
-.Sh NAME
-.Nm ed
-.Nd NE-2000 and WD-80x3 ethernet device driver
-.Sh SYNOPSIS
-.Cd "device miibus"
-.Cd "device ed"
-.Sh DESCRIPTION
-The
-.Nm
-driver provides support for 8 and 16bit ethernet cards that are based on
-the National Semiconductor DS8390 and similar NICs manufactured by other companies.
-.Pp
-It supports all 80x3 series ethernet cards manufactured by Western Digital and SMC,
-the SMC Ultra, the 3Com 3c503, the Novell NE1000/NE2000 and compatible cards,
-the HP PC Lan+ and the Digital Equipment EtherWorks DE305 card.
-PCI and PC Card devices are supported.
-.Pp
-The
-.Nm
-driver uses a unique multi-buffering mechanism to achieve high transmit performance.
-.Pp
-In addition to the standard port and IRQ specifications, the
-.Nm
-driver also supports a number of
-.Cd flags
-which can force 8/16bit mode, enable/disable multi-buffering, and select the default
-interface type (AUI/BNC, and for cards with twisted pair, AUI/10BaseT).
-.Pp
-When using a 3c503 card, the AUI connection may be selected by specifying the
-.Cm link2
-option to
-.Xr ifconfig 8
-(BNC is the default).
-.Sh DIAGNOSTICS
-.Bl -diag
-.It "ed%d: kernel configured irq %d doesn't match board configured irq %d."
-The IRQ number that was specified in the kernel config file (and then compiled
-into the kernel) differs from the IRQ that has been set on the interface card.
-.It "ed%d: failed to clear shared memory at %x - check configuration."
-When the card was probed at system boot time, the
-.Nm
-driver found that it could not clear the card's shared memory.
-This is most commonly
-caused by a BIOS extension ROM being configured in the same address space as the
-ethernet card's shared memory.
-Either find the offending card and change its BIOS
-ROM to be at an address that doesn't conflict, or change the
-.Cd iomem
-option in the kernel config file so that the card's shared memory is mapped at a
-non-conflicting address.
-.It "ed%d: Invalid irq configuration (%d) must be 2-5 for 3c503."
-The IRQ number that was specified in the kernel config file is not valid for
-the 3Com 3c503 card.
-The 3c503 can only be assigned to IRQs 2 through 5.
-.It "ed%d: Cannot find start of RAM."
-.It "ed%d: Cannot find any RAM, start : %d, x = %d."
-The probe of a Gateway card was unsuccessful in configuring the card's packet memory.
-This likely indicates that the card was improperly recognized as a Gateway or that
-the card is defective.
-.It "ed: packets buffered, but transmitter idle."
-Indicates a logic problem in the driver.
-Should never happen.
-.It "ed%d: device timeout"
-Indicates that an expected transmitter interrupt didn't occur.
-This condition could also be caused if the kernel is configured for a
-different IRQ channel than the one the card is actually using.
-If that is the case, you will have to either reconfigure the card
-using a DOS utility or set the jumpers on the card appropriately.
-.It "ed%d: NIC memory corrupt - invalid packet length %d."
-Indicates that a packet was received with a packet length that was either larger than
-the maximum size or smaller than the minimum size allowed by the IEEE 802.3 standard.
-.It "ed%d: remote transmit DMA failed to complete."
-This indicates that a programmed I/O transfer to an NE1000 or NE2000 style card
-has failed to properly complete.
-.El
-.Sh SEE ALSO
-.Xr arp 4 ,
-.Xr ifmedia 4 ,
-.Xr miibus 4 ,
-.Xr netintro 4 ,
-.Xr ng_ether 4 ,
-.Xr ifconfig 8
-.Sh HISTORY
-The
-.Nm
-device driver first appeared in
-.Fx 1.0 .
-.Sh AUTHORS
-The
-.Nm
-device driver and this manual page were written by
-.An David Greenman .
-.Sh CAVEATS
-Early revision DS8390 chips have problems.
-They lock up whenever the receive
-ring-buffer overflows.
-They occasionally switch the byte order
-of the length field in the packet ring header (several different causes
-of this related to an off-by-one byte alignment) - resulting in
-.Qq Li "NIC memory corrupt - invalid packet length"
-messages.
-The card is reset
-whenever these problems occur, but otherwise there is no problem with
-recovering from these conditions.
-.Pp
-The NIC memory access to 3Com and Novell cards is much slower than it is on
-WD/SMC cards; it's less than 1MB/second on 8bit boards and less than 2MB/second
-on the 16bit cards.
-This can lead to ring-buffer overruns resulting in
-dropped packets during heavy network traffic.
-.Pp
-16bit Compex cards identify themselves as being 8bit.
-While these cards will
-work in 8bit mode, much higher performance can be achieved by specifying
-.Cd "flags 0x04"
-(force 16bit mode) in your kernel config file.
-In addition, you should also specify
-.Cd "iosiz 16384"
-to take advantage of the extra 8K of shared memory that 16bit mode provides.
-.Sh BUGS
-The
-.Nm
-driver is a bit too aggressive about resetting the card whenever any bad
-packets are received.
-As a result, it may throw out some good packets which
-have been received but not yet transferred from the card to main memory.
diff --git a/share/man/man4/man4.i386/ep.4 b/share/man/man4/man4.i386/ep.4
deleted file mode 100644
index 2ae1c0e..0000000
--- a/share/man/man4/man4.i386/ep.4
+++ /dev/null
@@ -1,92 +0,0 @@
-.\"
-.\" Copyright (c) 1994 Herb Peyerl
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\"    must display the following acknowledgement:
-.\"      This product includes software developed by Herb Peyerl
-.\" 3. The name of the author may not be used to endorse or promote products
-.\"    derived from this software without specific prior written permission
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
-.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
-.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
-.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
-.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
-.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/ep.4,v 1.16.2.6 2001/08/17 13:08:45 ru Exp $
-.\"
-.Dd February 4, 1993
-.Dt EP 4 i386
-.Os
-.Sh NAME
-.Nm ep
-.Nd Ethernet driver for 3Com Etherlink III (3c5x9)
-.Sh SYNOPSIS
-.Cd "device ep"
-.Sh DESCRIPTION
-The
-.Nm
-device driver supports various PCMCIA cards including the 3c589.
-Various models of these cards come with a different assortment of
-connectors:
-.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
-.It AUI/DIX
-Standard 15 pin connector, also known as 10base5 (thick-net)
-.It 10Base2
-BNC, also known as thin-net
-.It 10BaseT
-UTP, also known as twisted pair
-.El
-.Pp
-The default port to use is the port that has been selected with the
-setup utility.
-To override this, use the following media options with
-.Xr ifconfig 8
-or in your
-.Pa /etc/rc.conf
-file.
-.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
-.It 10base5/AUI
-Use the AUI port.
-.It 10base2/BNC
-Use the BNC port.
-.It 10baseT/UTP
-Use the UTP port.
-.El
-.Pp
-If there are multiple cards in the computer, they are searched for
-in the following order: bus, slot, then ethernet address.
-.Sh DIAGNOSTICS
-.Bl -diag
-.It ep0: reset (status: %x)
-The driver has encountered a FIFO underrun or overrun.
-The driver will reset the card and the packet will be lost.
-This is not fatal.
-.It ep0: eeprom failed to come ready
-The eeprom failed to come ready.
-This probably means the card is wedged.
-.El
-.Sh SEE ALSO
-.Xr ed 4 ,
-.Xr ifmedia 4 ,
-.Xr intro 4 ,
-.Xr ng_ether 4 ,
-.Xr vx 4 ,
-.Xr ifconfig 8
-.Sh STANDARDS
-are great.
-There's so many to choose from.
diff --git a/share/man/man4/man4.i386/ex.4 b/share/man/man4/man4.i386/ex.4
deleted file mode 100644
index d7dc3f6..0000000
--- a/share/man/man4/man4.i386/ex.4
+++ /dev/null
@@ -1,72 +0,0 @@
-.\"
-.\" Copyright (c) 1997 David E. O'Brien
-.\"
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR
-.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
-.\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT,
-.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
-.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
-.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/ex.4,v 1.9.2.6 2001/08/17 13:08:45 ru Exp $
-.\"
-.Dd January 19, 1997
-.Dt EX 4 i386
-.Os
-.Sh NAME
-.Nm ex
-.Nd "Ethernet device driver for the Intel EtherExpress Pro/10 and Pro/10+"
-.Sh SYNOPSIS
-.Cd "device ex"
-.Sh DESCRIPTION
-The
-.Nm
-driver provides support for the 16-bit PCI Intel EtherExpress Pro/10
-and Pro/10+ Ethernet cards based on the Intel i82595 chip.
-.Sh DIAGNOSTICS
-.Bl -diag
-.It "ex%d: Intel EtherExpress Pro/10, address XX:XX:XX:XX:XX:XX, connector %s"
-The device probe found an installed card, and was able to correctly install
-the device driver.
-.It "ex%d: WARNING: board's EEPROM is configured for IRQ %d, using %d"
-The device probe detected that the board is configured for a different
-interrupt than the one specified in the kernel configuration file.
-.It "ex%d: invalid IRQ."
-The device probe detected an invalid IRQ setting.
-.El
-.Sh SEE ALSO
-.Xr arp 4 ,
-.Xr ifmedia 4 ,
-.Xr netintro 4 ,
-.Xr ng_ether 4 ,
-.Xr ifconfig 8
-.Sh HISTORY
-The
-.Nm
-device driver first appeared in
-.Fx 2.2 .
-.Sh AUTHORS
-.An -nosplit
-The
-.Nm
-device driver was written by
-.An Javier Mart\('in Rueda .
-This manual page was written by
-.An David E. O'Brien .
-.Sh BUGS
-Currently the driver does not support multicast.
diff --git a/share/man/man4/man4.i386/fe.4 b/share/man/man4/man4.i386/fe.4
deleted file mode 100644
index 739ae7c0..0000000
--- a/share/man/man4/man4.i386/fe.4
+++ /dev/null
@@ -1,309 +0,0 @@
-.\" All Rights Reserved, Copyright (C) Fujitsu Limited 1995
-.\"
-.\" This document may be used, modified, copied, distributed, and sold, in
-.\" both source and printed form provided that the above copyright, these
-.\" terms and the following disclaimer are retained.  The name of the author
-.\" and/or the contributor may not be used to endorse or promote products
-.\" derived from this software without specific prior written permission.
-.\"
-.\" THIS DOCUMENT IS PROVIDED BY THE AUTHOR AND THE CONTRIBUTOR ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR THE CONTRIBUTOR BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" Contributed by M. Sekiguchi <seki@sysrap.cs.fujitsu.co.jp>.
-.\" for fe driver.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/fe.4,v 1.14.2.8 2001/10/10 11:43:53 murray Exp $
-.Dd March 3, 1996
-.Dt FE 4 i386
-.Os
-.Sh NAME
-.Nm fe
-.Nd Fujitsu MB86960A/MB86965A based Ethernet adapters
-.Sh SYNOPSIS
-.Cd "device fe0 at isa? port 0x300 irq ?"
-.Sh DESCRIPTION
-The
-.Nm
-is a network device driver
-for Ethernet adapters based on Fujitsu MB86960A, MB86965A,
-or other compatible chips.
-.Pp
-The driver provides automatic I/O port address configuration and
-automatic IRQ configuration,
-when used with suitable adapter hardware.
-.Pp
-The driver works with program I/O data transfer technique.
-It gives a fair performance.
-Shared memory is never used, even if the adapter has one.
-.Pp
-It currently works with Fujitsu FMV-180 series for ISA,
-Allied-Telesis AT1700 series and RE2000 series for ISA,
-and Fujitsu MBH10302 PC card.
-.Ss Parameters
-On the kernel configuration file, two parameters,
-.Ar port
-and
-.Ar irq ,
-must be specified to reflect adapter hardware settings.
-Another parameter
-.Ar flags
-can be specified to provide additional configuration as an option.
-Other parameters of the device statement
-must appear as described on the synopsis.
-.Pp
-The
-.Ar port
-parameter specifies a base I/O port address of the adapter.
-It must match with the hardware setting of the adapter.
-The
-.Ar port
-may be a left unspecified as
-.Dq Li \&? .
-In that case, the driver tries to detect the hardware setting
-of the I/O address automatically.
-This feature may not work with some adapter hardware.
-.Pp
-The
-.Ar irq
-parameter specifies an IRQ number used by the adapter.
-It must match the hardware setting of the adapter.
-.Ar Irq
-may be left unspecified as
-.Dq Li \&? ;
-in that case, the driver tries to detect
-the hardware setting of the IRQ automatically.
-This feature may not work on some adapters.
-.Pp
-The
-.Ar flags
-is a numeric value which consists of a combination of various device settings.
-The following flags are defined in the current version.
-To specify two or more settings for a device,
-use a numeric sum of each flag value.
-Flag bits not specified below are reserved and must be set to 0.
-Actually, each bit is either just ignored by the driver,
-or tested and used to control undocumented features of the driver.
-Consult the source program for undocumented features.
-.Bl -tag -width 8n
-.It Li 0x007F
-These flag bits are used
-to initialize DLCR6 register of MB86960A/MB86965A chip,
-when the
-.Li 0x0080
-bit of the
-.Ar flags
-is set.
-See below for more about DLCR6 override feature.
-The
-.Li 0x007F
-flag bits must be 0 unless the
-.Li 0x0080
-bit is set,
-to maintain the compatibility with future versions of the driver.
-.It Li 0x0080
-This flag overrides the default setting to the DLCR6 register
-of MB86960A/MB86965A chip by a user supplied value,
-which is taken from the lower 7 bits of the flag value.
-This is a troubleshooting flag and should not be used
-without understanding of the adapter hardware.
-Consult the Fujitsu manual for more information
-on DLCR6 settings.
-.El
-.Sh OPTIONS
-The
-.Nm
-driver has some private options,
-which can be specified with an
-.Dq option
-statement in the kernel configuration file.
-The following lists the private options.
-The driver also accepts some other undocumented options,
-all of whose names start with a fixed prefix
-.Dv "FE_" .
-Consult the source program for undocumented options.
-.Bl -tag -width "FE_"
-.It Dv "FE_DEBUG=" Ns Ar level
-This option takes a numeric value
-.Ar level
-which controls the debugging level for the device and/or the driver.
-Setting the
-.Dv "FE_DEBUG"
-option to a value which is not listed here
-may cause undocumented behavior.
-The default setting of this option is 1.
-.Bl -bullet
-.It
-Setting
-.Dv "FE_DEBUG=0"
-makes most of debugging codes,
-including sanity check,
-be excluded from the object code of the driver.
-It generates fastest and smallest object code.
-Some emergency messages are logged even under this setting, though.
-.It
-Setting
-.Dv "FE_DEBUG=1"
-makes minimum debugging codes be included,
-setting the amount of logged messages minimum.
-Only fatal error messages are logged under this setting.
-.It
-Setting
-.Dv "FE_DEBUG=2"
-makes standard debugging codes be included,
-setting the amount of logged messages middle.
-Messages on lair events and/or questionable conditions
-are logged under this setting.
-.It
-Setting
-.Dv "FE_DEBUG=3"
-makes all debugging codes be included,
-and set the amount of legged messages maximum.
-Redundant messages such as those reporting usual actions
-or dumping register values
-are logged under this setting.
-.El
-.El
-.Sh FEATURES SPECIFIC TO HARDWARE MODELS
-The
-.Nm
-driver has some features and limitations
-which depend on adapter hardware models.
-The following is a summary of such dependency.
-.Ss Fujitsu FMV-180 series adapters
-Both automatic IRQ detection and automatic I/O port address detection
-is available with these adapters.
-.Pp
-Automatic I/O port address detection feature of
-.Nm
-works mostly fine for FMV-180 series.
-It works even if there are two or more FMV-180s in a system.
-However, some combination of other adapters may confuse the driver.
-It is recommended not to use
-.Em "port ?"
-when you experience some difficulties with hardware probe.
-.Pp
-Automatic IRQ detection feature of
-.Nm
-works reliably for FMV-180 series.
-It is recommended to use
-.Em "irq ?"
-always for FMV-180.
-The hardware setting of IRQ is read
-from the configuration EEPROM on the adapter,
-even when the kernel config file specifies an IRQ value.
-The driver will generate a warning message,
-if the IRQ setting specified in the kernel config file
-does not match one stored in EEPROM.
-Then, it will use the value specified in the config file.
-(This behavior has been changed from the previous releases.)
-.Ss Allied-Telesis AT1700 series and RE2000 series adapters
-Automatic I/O port address detection
-is available with Allied-Telesis AT1700 series and RE2000 series,
-while it is less reliable than FMV-180 series.
-Using the feature with Allied-Telesis adapters
-is not recommended.
-.Pp
-Automatic IRQ detection is also available with some limitation.
-The
-.Nm
-driver
-tries to get IRQ setting from the configuration EEPROM on the board,
-if
-.Dq irq ?\&
-is specified in the configuration file.
-Unfortunately,
-AT1700 series and RE2000 series seems to have two types of models;
-One type allows IRQ selection from 3/4/5/9,
-while the other from 10/11/12/15.
-Identification of the models are not well known.
-Hence, automatic IRQ detection with Allied-Telesis adapters
-may not be reliable.
-Specify an exact IRQ number if any troubles are encountered.
-.Pp
-Differences between AT1700 series and RE2000 series
-or minor models in those series are not recognized.
-.Ss Fujitsu MBH10302 PC card
-The
-.Nm
-driver supports Fujitsu MBH10302 and compatible PC cards.
-It requires the PC card (PCMCIA) support package.
-.Sh SEE ALSO
-.Xr netstat 1 ,
-.Xr ed 4 ,
-.Xr ifmedia 4 ,
-.Xr netintro 4 ,
-.Xr ng_ether 4 ,
-.Xr ifconfig 8
-.Sh HISTORY
-The
-.Nm
-driver appeared in
-.Fx 2.0.5 .
-.Sh AUTHORS, COPYRIGHT AND DISCLAIMER
-The
-.Nm
-driver was originally written and contributed by
-.An M. Sekiguchi Aq Mt seki@sysrap.cs.fujitsu.co.jp ,
-following the
-.Xr ed 4
-driver written by
-.An David Greenman .
-PC card support in
-.Nm
-is written by
-.An Hidetoshi Kimura Aq Mt h-kimura@tokyo.se.fujitsu.co.jp .
-This manual page was written by
-.An M. Sekiguchi .
-.Pp
-.Em "All Rights Reserved, Copyright (C) Fujitsu Limited 1995"
-.Pp
-This document and the associated software may be used, modified,
-copied, distributed, and sold, in both source and binary form provided
-that the above copyright, these terms and the following disclaimer are
-retained.  The name of the author and/or the contributor may not be
-used to endorse or promote products derived from this document and the
-associated software without specific prior written permission.
-.Pp
-THIS DOCUMENT AND THE ASSOCIATED SOFTWARE IS PROVIDED BY THE AUTHOR
-AND THE CONTRIBUTOR
-.Dq AS IS
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR THE
-CONTRIBUTOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
-EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
-PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
-PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-DOCUMENT AND THE ASSOCIATED SOFTWARE, EVEN IF ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
-.Sh BUGS
-Following are major known bugs:
-.Pp
-Statistics on the number of collisions maintained by the
-.Nm
-driver is not accurate;
-the
-.Fl i
-option of
-.Xr netstat 1
-shows slightly less value than true number of collisions.
-.Pp
-More mbuf clusters are used than expected.
-The packet receive routine has an intended violation
-against the mbuf cluster allocation policy.
-The unnecessarily allocated clusters are freed within short lifetime,
-and it will not affect long term kernel memory usage.
-.Pp
-Although XNS and IPX supports are included in the driver,
-they are never be tested and must have a lot of bugs.
diff --git a/share/man/man4/man4.i386/glxsb.4 b/share/man/man4/man4.i386/glxsb.4
deleted file mode 100644
index 2a1422d..0000000
--- a/share/man/man4/man4.i386/glxsb.4
+++ /dev/null
@@ -1,97 +0,0 @@
-.\" $OpenBSD: glxsb.4,v 1.5 2007/05/31 19:19:54 jmc Exp $
-.\"
-.\"Copyright (c) 2006 Tom Cosgrove <tom@openbsd.org>
-.\"
-.\"Permission to use, copy, modify, and distribute this software for any
-.\"purpose with or without fee is hereby granted, provided that the above
-.\"copyright notice and this permission notice appear in all copies.
-.\"
-.\"THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
-.\"WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
-.\"MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
-.\"ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
-.\"WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
-.\"ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
-.\"OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/glxsb.4,v 1.4 2009/04/23 08:37:56 brueffer Exp $
-.\"
-.Dd October 6, 2009
-.Dt GLXSB 4 i386
-.Os
-.Sh NAME
-.Nm glxsb
-.Nd Geode LX Security Block crypto accelerator
-.Sh SYNOPSIS
-To compile this driver into the kernel,
-place the following lines in your
-kernel configuration file:
-.Bd -ragged -offset indent
-.Cd "device crypto"
-.Cd "device glxsb"
-.Ed
-.Pp
-Alternatively, to load the driver as a
-module at boot time, place the following line in
-.Xr loader.conf 5 :
-.Bd -literal -offset indent
-glxsb_load="YES"
-.Ed
-.Sh DESCRIPTION
-The
-.Nm
-driver supports the security block of the Geode LX series processors.
-The Geode LX is a member of the AMD Geode family
-of integrated x86 system chips.
-.Pp
-Driven by periodic checks for available data from the generator,
-.Nm
-supplies entropy to the
-.Xr random 4
-driver for common usage.
-.Pp
-.Nm
-also supports acceleration of AES-128-CBC operations for
-.Xr crypto 4 .
-It also registers itself to accelerate other HMAC algorithms, although
-there is no hardware acceleration for those algorithms.
-This is only needed so
-.Nm
-can work with
-.Xr ipsec 4 .
-.Sh CAVEAT
-The
-.Xr crypto 9
-framework will fail to open the crypto session on the device if the AES
-key's length is != 128 bits.
-This prevents the use of the
-.Nm
-device driver with AES keys of length != 128 bits.
-.Sh SEE ALSO
-.Xr crypto 4 ,
-.Xr intro 4 ,
-.Xr ipsec 4 ,
-.Xr pci 4 ,
-.Xr random 4 ,
-.Xr crypto 9
-.Sh HISTORY
-The
-.Nm
-device driver first appeared in
-.Ox 4.1 .
-The
-.Nm
-device driver was imported into
-.Fx 7.1 .
-.Sh AUTHORS
-.An -nosplit
-The
-.Nm
-device driver was written for
-.Ox
-by
-.An Tom Cosgrove .
-It was ported to
-.Fx
-by
-.An Patrick Lamaiziere Aq Mt patfbsd@davenulle.org .
diff --git a/share/man/man4/man4.i386/linux.4 b/share/man/man4/man4.i386/linux.4
deleted file mode 100644
index 9c76f4c..0000000
--- a/share/man/man4/man4.i386/linux.4
+++ /dev/null
@@ -1,124 +0,0 @@
-.\" Copyright (c) 2000 Sheldon Hearn
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $DragonFly: src/share/man/man4/man4.i386/linux.4,v 1.2 2007/07/14 21:48:15 swildner Exp $
-.\" $FreeBSD: src/share/man/man4/man4.i386/linux.4,v 1.6 2002/12/12 17:25:57 ru Exp $
-.Dd September 17, 2003
-.Dt LINUX 4 i386
-.Os
-.Sh NAME
-.Nm linux
-.Nd Linux ABI support
-.Sh SYNOPSIS
-To link Linux ABI support into the kernel:
-.Cd "options COMPAT_LINUX"
-.Pp
-To load the Linux ABI support kernel module:
-.Dl kldload linux
-.Sh DESCRIPTION
-The
-.Nm
-module provides limited
-Linux ABI (Application Binary Interface) compatibility
-for userland applications.
-The module provides the following significant facilities:
-.Bl -bullet
-.It
-An image activator for correctly branded
-.Xr elf 5
-executable images
-.It
-Special signal handling for activated images
-.It
-Linux to native system call translation
-.El
-.Pp
-It is important to note that the Linux ABI support
-is not provided through an emulator, instead,
-a true (albeit limited) ABI implementation is provided.
-.Pp
-The following
-.Xr sysctl 8
-tunable variables are available:
-.Bl -tag -width ".Va compat.linux.oss_version"
-.It Va compat.linux.osname
-Linux kernel operating system name.
-.It Va compat.linux.osrelease
-Linux kernel operating system release.
-.It Va compat.linux.oss_version
-Linux Open Sound System version.
-.El
-.Pp
-The
-.Nm
-module can be linked into the kernel statically with the
-.Dv COMPAT_LINUX
-kernel configuration option
-or loaded as required.
-The following command will load the module
-if it is neither linked into the kernel
-nor already loaded as a module:
-.Bd -literal -offset indent
-if ! kldstat -v | grep -E 'linux(aout|elf)' > /dev/null; then
-	kldload linux > /dev/null 2>&1
-fi
-.Ed
-.Pp
-Note that dynamically linked Linux executables
-will require a suitable environment in
-.Pa /compat/linux .
-Specifically, the Linux run-time linker's hints files
-should be correctly initialized.
-For this reason, it is common to execute the following commands
-to prepare the system to correctly run Linux executables:
-.Bd -literal -offset indent
-if [ -x /compat/linux/sbin/ldconfig ]; then
-	/compat/linux/sbin/ldconfig
-fi
-.Ed
-.Pp
-For information on loading the
-.Nm
-kernel loadable module automatically on system startup,
-see
-.Xr rc.conf 5 .
-This information applies
-regardless of whether the
-.Nm
-module is statically linked into the kernel
-or loaded as a module.
-.Sh FILES
-.Bl -tag -width /compat/linux/proc -compact
-.It Pa /compat/linux
-minimal Linux run-time environment
-.It Pa /compat/linux/proc
-limited Linux process file system
-.El
-.Sh SEE ALSO
-.Xr brandelf 1 ,
-.Xr elf 5 ,
-.Xr linprocfs 5
-.Sh HISTORY
-Linux ABI support first appeared in
-.Fx 2.1 .
diff --git a/share/man/man4/man4.i386/longrun.4 b/share/man/man4/man4.i386/longrun.4
deleted file mode 100644
index 9324667..0000000
--- a/share/man/man4/man4.i386/longrun.4
+++ /dev/null
@@ -1,67 +0,0 @@
-.\" Copyright (c) 2001 Tamotsu HATTORI <athlete@kta.att.ne.jp>
-.\" Copyright (c) 2001 Mitsuru IWASAKI <iwasaki@FreeBSD.org>
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/longrun.4,v 1.7 2005/01/21 08:36:39 ru Exp $
-.Dd June 30, 2001
-.Dt LONGRUN 4 i386
-.Os
-.Sh NAME
-.Nm longrun
-.Nd Transmeta(TM) Crusoe(TM) LongRun(TM) support
-.Sh SYNOPSIS
-LongRun support is a collection of power saving modes for the
-Transmeta Crusoe chips, similar in scope to Intel's SpeedStep.
-The following
-.Xr sysctl 8
-MIBs control the different CPU modes:
-.Bl -column ".Va hw.crusoe.percentage" ".Vt integer" "Changeable"
-.It Sy "Name	Type	Changeable	Description"
-.It Va hw.crusoe.longrun Ta Vt integer Ta yes Ta "LongRun mode:"
-.It Ta Ta Ta "0: minimum frequency mode"
-.It Ta Ta Ta "1: power-saving mode"
-.It Ta Ta Ta "2: performance mode"
-.It Ta Ta Ta "3: maximum frequency mode"
-.It Va hw.crusoe.frequency Ta Vt integer Ta no Ta "Current frequency (MHz)."
-.It Va hw.crusoe.voltage Ta Vt integer Ta no Ta "Current voltage (mV)."
-.It Va hw.crusoe.percentage Ta Vt integer Ta no Ta "Processing performance (%)."
-.El
-.Sh EXAMPLES
-Print the current status:
-.Pp
-.Dl "% sysctl hw.crusoe"
-.Pp
-To set LongRun mode to performance oriented variable frequency mode
-(less power savings):
-.Pp
-.Dl "# sysctl hw.crusoe.longrun=2"
-.Sh HISTORY
-The Transmeta(TM) Crusoe(TM) LongRun(TM) support first appeared in
-.Fx 4.4 .
-.Sh AUTHORS
-.An -nosplit
-LongRun support and this manual page were written by
-.An Tamotsu HATTORI Aq Mt athlete@kta.att.ne.jp
-and
-.An Mitsuru IWASAKI Aq Mt iwasaki@FreeBSD.org .
diff --git a/share/man/man4/man4.i386/npx.4 b/share/man/man4/man4.i386/npx.4
deleted file mode 100644
index f9da0a1..0000000
--- a/share/man/man4/man4.i386/npx.4
+++ /dev/null
@@ -1,95 +0,0 @@
-.\"
-.\" Copyright (c) 1993 Christopher G. Demetriou
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\"    must display the following acknowledgement:
-.\"      This product includes software developed by Christopher G. Demetriou.
-.\" 3. The name of the author may not be used to endorse or promote products
-.\"    derived from this software without specific prior written permission
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
-.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
-.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
-.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
-.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
-.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-.\"
-.\"	from: npx.4,v 1.1 1993/08/06 10:58:03 cgd Exp
-.\" $FreeBSD: src/share/man/man4/man4.i386/npx.4,v 1.9.2.3 2001/08/17 13:08:46 ru Exp $
-.\" $DragonFly: src/share/man/man4/man4.i386/npx.4,v 1.3 2007/12/25 12:40:32 swildner Exp $
-.\"
-.Dd August 28, 1993
-.Dt NPX 4 i386
-.Os
-.Sh NAME
-.Nm npx
-.Nd Numeric Processing Extension coprocessor and emulator
-.Sh SYNOPSIS
-.Cd "device npx0 at nexus? port IO_NPX flags 0x0 irq 13"
-.Pp
-For hosts without a FPU coprocessor add:
-.Cd "options MATH_EMULATE"
-.Sh DESCRIPTION
-The
-.Nm
-driver enables the use of the system's Numeric Processing Extension
-coprocessor, if one is present.
-Numeric processing extensions are present in systems with
-.Sy 486DX
-CPUs and in systems with
-.Sy 487SX
-coprocessors.
-The
-.Nm
-driver is required for proper system functioning regardless
-of whether or not a NPX is present.
-.Pp
-If there is no NPX present in the system, the
-.Dv MATH_EMULATE
-option must be defined in the kernel configuration file.
-It will provide support for the instructions normally executed by the NPX.
-If there is no NPX in the system and the kernel is not built with math
-emulation, the system will not boot.
-.Pp
-The
-.Sy GENERIC
-kernel configuration uses the
-.Dv MATH_EMULATE
-option.
-.Pp
-For a description of the possible "flags" values see the LINT kernel
-configuration file.
-.Sh CAVEATS
-The emulator is much slower than the NPX coprocessor.
-This will result in poor floating-point math performance
-if the emulator must be used.
-.Pp
-The emulator does not support the whole set of npx instructions.
-It is sufficient for booting and configuring a system, but it cannot
-support a system with normal workload unless care is taken to compile
-the whole system (including third-party packages) with compiler
-options that avoid the use of the non-emulated instructions.
-.Sh BUGS
-There are lots of them, especially on old cheap motherboards.
-In particular, some motherboards do not have the interrupt lines from
-the NPX to the CPU wired properly.
-If this is the case, the emulator must be used if consistent system
-operation is desired.
-.Pp
-When using the
-.Dv MATH_EMULATE
-option, transcendental function instructions are not implemented.
-Emulation of other instructions is suspect.
diff --git a/share/man/man4/man4.i386/perfmon.4 b/share/man/man4/man4.i386/perfmon.4
deleted file mode 100644
index 5663fc5..0000000
--- a/share/man/man4/man4.i386/perfmon.4
+++ /dev/null
@@ -1,204 +0,0 @@
-.\"
-.\" Copyright 1996 Massachusetts Institute of Technology
-.\"
-.\" Permission to use, copy, modify, and distribute this software and
-.\" its documentation for any purpose and without fee is hereby
-.\" granted, provided that both the above copyright notice and this
-.\" permission notice appear in all copies, that both the above
-.\" copyright notice and this permission notice appear in all
-.\" supporting documentation, and that the name of M.I.T. not be used
-.\" in advertising or publicity pertaining to distribution of the
-.\" software without specific, written prior permission.  M.I.T. makes
-.\" no representations about the suitability of this software for any
-.\" purpose.  It is provided "as is" without express or implied
-.\" warranty.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY M.I.T. ``AS IS''.  M.I.T. DISCLAIMS
-.\" ALL EXPRESS OR IMPLIED WARRANTIES WITH REGARD TO THIS SOFTWARE,
-.\" INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT
-.\" SHALL M.I.T. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-.\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-.\" LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
-.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
-.\" ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
-.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/perfmon.4,v 1.8.2.5 2001/08/17 13:08:46 ru Exp $
-.\" $DragonFly: src/share/man/man4/man4.i386/perfmon.4,v 1.4 2007/11/04 19:04:42 swildner Exp $
-.Dd March 26, 1996
-.Dt PERFMON 4 i386
-.Os
-.Sh NAME
-.Nm perfmon
-.Nd CPU performance-monitoring interface
-.Sh SYNOPSIS
-.Cd cpu I586_CPU
-.Cd cpu I686_CPU
-.Cd options PERFMON
-.Sh DESCRIPTION
-The
-.Nm
-driver provides access to the internal performance-monitoring
-capabilities of the
-.Tn Intel
-.Tn Pentium
-and
-.Tn "Pentium Pro"
-CPUs.  These processors implement two internal counters which can be
-configured to measure a variety of events for either count or duration
-(in CPU cycles), as well as a cycle counter which counts clock cycles.
-The
-.Nm
-driver provides a device-style interface to these capabilities.
-.Pp
-All access to the performance-monitoring counters is performed through
-the special device file
-.Dq Pa /dev/perfmon .
-This device supports a number of
-.Xr ioctl 2
-requests, defined in
-.In machine/perfmon.h
-along with the definitions of the various counters for both
-.Tn Pentium
-and
-.Tn "Pentium Pro"
-processors.
-.Pp
-.Sy NOTA BENE :
-The set of available events differs from processor to processor.  It
-is the responsibility of the programmer to ensure that the event
-numbers used are the correct ones for the CPU type being measured.
-.Pp
-The following
-.Xr ioctl 2
-requests are defined:
-.Bl -tag -width ".Dv PMIOTSTAMP"
-.It Dv PMIOSETUP
-.Pq Li "struct pmc"
-Set up a counter with parameters and flags defined in the structure.
-The following fields are defined in
-.Li struct pmc :
-.Bl -tag -width "u_char pmc_eventx"
-.It Li "int pmc_num"
-the number of the counter in question; must be less than
-.Dv NPMC
-(currently 2).
-.It Li "u_char pmc_event"
-the particular event number to be monitored, as defined in
-.In machine/perfmon.h .
-.It Li "u_char pmc_unit"
-the unit mask value, specific to the event type (see the
-.Tn Intel
-documentation).
-.It Li "u_char pmc_flags"
-flags modifying the operation of the counter (see below).
-.It Li "u_char pmc_mask"
-the counter mask value; essentially, this is a threshold used to
-restrict the count to events lasting more (or less) than the specified
-number of clocks.
-.El
-.Pp
-The following
-.Li pmc_flags
-values are defined:
-.Bl -tag -compact -width PMCF_USRxx
-.It Dv PMCF_USR
-count events in user mode
-.It Dv PMCF_OS
-count events in kernel mode
-.It Dv PMCF_E
-count number of events rather than their duration
-.It Dv PMCF_INV
-invert the sense of the counter mask comparison
-.El
-.It Dv PMIOGET
-.Pq Li "struct pmc"
-returns the current configuration of the specified counter.
-.It Dv PMIOSTART
-.It Dv PMIOSTOP
-.Pq Li int
-starts (stops) the specified counter.  Due to hardware deficiencies,
-counters must be started and stopped in numerical order.  (That is to
-say, counter 0 can never be stopped without first stopping counter 1.)
-The driver will
-.Em not
-enforce this restriction (since it may not be present in future CPUs).
-.It Dv PMIORESET
-.Pq Li int
-reset the specified counter to zero.  The counter should be stopped
-with
-.Dv PMIOSTOP
-before it is reset.  All counters are automatically reset by
-.Dv PMIOSETUP .
-.It Dv PMIOREAD
-.Pq Li "struct pmc_data"
-get the current value of the counter.  The
-.Li pmc_data
-structure defines two fields:
-.Pp
-.Bl -tag -compact -width "quad_t pmcd_value"
-.It Li "int pmcd_num"
-the number of the counter to read
-.It Li "quad_t pmcd_value"
-the resulting value as a 64-bit signed integer
-.El
-.Pp
-In the future, it may be possible to use the
-.Li RDPMC
-instruction on
-.Tn "Pentium Pro"
-processors to read the counters directly.
-.It Dv PMIOTSTAMP
-.Pq Li "struct pmc_tstamp"
-read the time stamp counter.  The
-.Li pmc_tstamp
-structure defines two fields:
-.Pp
-.Bl -tag -compact -width "quad_t pmct_value"
-.It Li "int pmct_rate"
-the approximate rate of the counter, in MHz
-.It Li "quad_t pmct_value"
-the current value of the counter as a 64-bit integer
-.El
-.Pp
-It is important to note that the counter rate, as provided in the
-.Li pmct_rate
-field, is often incorrect because of calibration difficulties and
-non-integral clock rates.  This field should be considered more of a
-hint or sanity-check than an actual representation of the rate of
-clock ticks.
-.El
-.Sh FILES
-.Bl -tag -compact -width "/usr/include/machine/perfmon.h"
-.It Pa /dev/perfmon
-character device interface to counters
-.It In machine/perfmon.h
-include file with definitions of structures and event types
-.It Pa /usr/share/examples/perfmon
-sample source code demonstrating use of all the
-.Fn ioctl
-commands
-.El
-.Sh SEE ALSO
-.Xr ioctl 2
-.Rs
-.%A Intel Corporation
-.%B Pentium Pro Family Developer's Manual
-.%D January 1996
-.%V vol. 3
-.%O Operating System Writer's Manual
-.Re
-.Sh HISTORY
-The
-.Nm
-device first appeared in
-.Fx 2.2 .
-.Sh AUTHORS
-The
-.Nm
-driver was written by
-.An Garrett A. Wollman ,
-MIT Laboratory for Computer Science.
diff --git a/share/man/man4/man4.i386/pnp.4 b/share/man/man4/man4.i386/pnp.4
deleted file mode 100644
index d45e9f5..0000000
--- a/share/man/man4/man4.i386/pnp.4
+++ /dev/null
@@ -1,195 +0,0 @@
-.\" pnp(4) - manual page for PnP device support
-.\"
-.\"
-.\" Copyright (c) 1997 Luigi Rizzo
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\"    must display the following acknowledgements:
-.\"	This product includes software developed by Luigi Rizzo.
-.\" 4. The name of the author may not be used to endorse or promote products
-.\"    derived from this software without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
-.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
-.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
-.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
-.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
-.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/pnp.4,v 1.5.2.7 2001/09/25 23:40:30 yokota Exp $
-.\"
-.Dd September 7, 1997
-.Dt PNP 4 i386
-.Os
-.Sh NAME
-.Nm pnp
-.Nd support for PnP devices
-.Sh SYNOPSIS
-.Cd controller pnp0
-.Sh DESCRIPTION
-Support for PnP devices in
-.Dx
-allows the user to override the
-configuration of PnP cards, and device drivers to fetch/modify
-parameters in the card's configuration space.
-.Pp
-The manual override mechanism requires the kernel to be compiled with
-.Cd options USERCONFIG .
-In this case, the kernel keeps a table of fixed size (20 entries as a
-default) where configuration data are held for PnP devices.
-Each
-PnP card can contain several independent devices (5 or 6 is not
-unusual).
-.Pp
-By booting the kernel with the
-.Dq Fl c
-flag, commands are available to
-modify the configuration of PnP cards.
-Commands start with the
-sequence:
-.Dl pnp CSN LDN
-where CSN and LDN are the Card Select Number and Logical Device Number
-associated to the device.
-Following this sequence any combination of
-the following commands can be used:
-.Bl -tag -width "mmmmmmmmmm"
-.It Dv irqN line
-Sets the irq line for interrupt 0 or 1 on the card.
-Line=0 means the line
-is unused.
-.It Dv drqN n
-Sets the drq channel used for DMA 0 or 1 on the card.
-Channel=4 means
-the channel is unused.
-.It Dv portN address
-Sets the base address for the N-th port's range (N=0..7). address=0
-means that the port is not used.
-.It Dv memN address
-Sets the base address for the N-th memory's range (N=0..3). address=0
-means that the memory range is not used.
-.It Dv bios
-Makes the PnP device use the configuration set by the BIOS.
-This
-is the default, and is generally ok if your BIOS has PnP support.
-If BIOS is used, then other parameters are ignored except "flags".
-.It Dv os
-Makes the PnP device to use the configuration specified in this entry.
-.It Dv enable
-Enables the PnP device.
-.It Dv disable
-Disables the PnP device.
-.It Dv delete
-Frees the entry used for the device, so that it can be used for
-another device with a different CSN/LDN pair.
-.It Dv flags
-Sets the value of a 32-bit flags entry which is passed to the device
-driver.
-This can be used to set special operation modes (e.g. SB vs. WSS
-emulation on some sound cards, etc.).
-.El
-.Pp
-The current content of the table can be printed using the
-.Ic ls
-command in userconfig.
-In addition to modifications done by the user,
-the table contains an entry for
-all logical devices accessed by a PnP device driver.
-.Pp
-Modifications to
-the table will be saved to the boot image on the filesystem by the
-.Xr kget 8
-command.
-.Sh DEVICE DRIVER SUPPORT FOR PnP
-PnP devices are automatically recognized and configured by the kernel.
-A PnP device is identified by the following data structure:
-.Bd -literal
-struct pnp_device {
-	char	*pd_name;
-	char	*(*pd_probe ) (u_long csn, u_long vendor_id);
-	void	(*pd_attach ) (u_long csn, u_long vend_id, char * name,
-		    struct isa_device *dev);
-	u_long	*pd_count;
-	u_int	*imask;
-	struct	isa_device dev;
-};
-.Ed
-.Pp
-The probe routine must check that the vendor_id passed is a
-recognized one, that any necessary devices on the card are enabled,
-and returns a NULL value in case of failure or a non-NULL value
-(generally a pointer to the device name) upon success.  In the probe
-routine, the function
-.Fn read_pnp_parms
-can be used to check that the logical devices are enabled.
-.Pp
-The attach routine should do all the necessary initialization, enable
-the PnP card to ISA accesses, fetch the configuration, and call the ISA
-driver for the device.
-.\".Pp
-.\"The following routines and data structures can be used:
-.\".Bl -tag -width "xxxxxxxxxx"
-.\".It Dv struct pnp_cinfo
-.\"This data structure (defined in
-.\".Pa /sys/boot/common/isapnp.h )
-.\"contains all
-.\"information related to a PnP logical device.
-.\".It Fn read_pnp_parms "struct pnp_cinfo *d" "int ldn"
-.\"This function returns the configuration of the requested
-.\"logical device.
-.\"It is not possible to specify a CSN since this function
-.\"is only meant to be used during probe and attach routines
-.\".It Fn write_pnp_parms "struct pnp_cinfo *d" "int ldn"
-.\"This function sets the parameters of the requested logical device.
-.\"At
-.\"the same time, it updates the entry in the kernel override table.
-.\"Device drivers in general should
-.\".Em not
-.\"modify the configuration of a device, since either the BIOS or the user
-.\"(through userconfig) should know better what to do.
-.\"In particular,
-.\"device driver
-.\".Em should not enable
-.\"a logical device which has
-.\"been found disabled,
-.\"since this would defeat the override mechanism in userconfig.
-.\"Device
-.\"drivers may disable a logical device, or a port range, etc, but should
-.\"do so only that particular device or parameter is known to cause
-.\"troubles.
-.\".It Fn enable_pnp_card void
-.\"This function
-.\".Em must
-.\"be used in the attach routine
-.\".Em only ,
-.\"before accessing the card's ISA ports/memory address ranges.
-.\".El
-.Sh SEE ALSO
-.Xr pnpbios 4 ,
-.Xr kget 8
-.Sh HISTORY
-The
-.Nm
-driver first appeared in
-.Fx 2.2.5 .
-.Sh AUTHORS
-.An -nosplit
-PnP support was written by
-.An Luigi Rizzo ,
-based on initial work done by
-.An Sujal Patel .
-.Sh BUGS
-There is no support for visual configuration of PnP devices.
-It would be nice to have commands in userconfig to fetch the
-configuration of PnP devices.
diff --git a/share/man/man4/man4.i386/pnpbios.4 b/share/man/man4/man4.i386/pnpbios.4
deleted file mode 100644
index f13722e..0000000
--- a/share/man/man4/man4.i386/pnpbios.4
+++ /dev/null
@@ -1,89 +0,0 @@
-.\"
-.\" Copyright (c) 2001
-.\" Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer as
-.\"    the first lines of this file unmodified.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
-.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
-.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
-.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
-.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
-.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/pnpbios.4,v 1.3 2005/07/15 17:35:26 hrs Exp $
-.\" $DragonFly: src/share/man/man4/man4.i386/pnpbios.4,v 1.2 2008/06/22 21:26:09 swildner Exp $
-.\"
-.Dd June 22, 2008
-.Dt PNPBIOS 4 i386
-.Os
-.Sh NAME
-.Nm pnpbios
-.Nd support for embedded devices on the motherboard
-.Sh SYNOPSIS
-.Cd device pnpbios
-.Sh DESCRIPTION
-The
-.Nm
-driver enumerates embedded ISA devices on the motherboard whose BIOS
-supports
-.Dq "Plug and Play BIOS Specification" .
-It assigns ISA bus resources (interrupt line, DMA channel, I/O ports,
-and memory region) to each device and activates it.
-.Pp
-If it cannot assign necessary resources to a device without
-causing conflict with other devices in the system,
-the device will not be activated and will be unavailable
-to programs.
-.Sh CAVEATS
-There is no explicit way to disable individual embedded devices.
-The
-.Nm
-driver will find all devices reported by the
-.Dq "Plug and Play (PnP)"
-BIOS and try to activate them all.
-.Pp
-There is no way to explicitly assign particular resource to a device.
-The resource assignment is fully automatic and there is
-no provision for manual override.
-.Sh SEE ALSO
-.Xr pnp 4
-.Sh STANDARDS
-.Rs
-.%A Compaq
-.%A Phoenix
-.%A Intel
-.%T "Plug and Play BIOS Specification Version 1.0A"
-.%D May 5, 1994
-.Re
-.Pp
-.Rs
-.%A Compaq
-.%A Phoenix
-.%A Intel
-.%T "Plug and Play BIOS CLARIFICATION Paper for Plug and Play BIOS Specification Version 1.0A"
-.%D October 6, 1994
-.Re
-.Sh HISTORY
-The
-.Nm
-driver first appeared in
-.Fx 4.0 .
-.Sh AUTHORS
-The
-.Nm
-driver was written by
-.An Mike Smith .
diff --git a/share/man/man4/man4.i386/pst.4 b/share/man/man4/man4.i386/pst.4
deleted file mode 100644
index b7aa51a..0000000
--- a/share/man/man4/man4.i386/pst.4
+++ /dev/null
@@ -1,65 +0,0 @@
-.\"
-.\" Copyright (c) 2001,2002 Søren Schmidt
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/pst.4,v 1.1.2.1 2002/09/28 11:19:07 sos Exp $
-.\"
-.Dd December 10, 2014
-.Dt PST 4 i386
-.Os
-.Sh NAME
-.Nm pst
-.Nd Device driver for Promise Supertrak SX6000
-.Sh SYNOPSIS
-Include this line in the kernel config file:
-.Cd device pst
-.Sh DESCRIPTION
-This driver is for the Promise Supertrak SX6000 ATA hardware RAID controller.
-It supports (in hardware) RAID levels 0, 1, 0+1, 3, 5 and JBOD on up to
-6 ATA disk drives, including automatic rebuild and hotswap, and supports
-signalling disk status on LED's on Promise Superswap disk enclosures.
-The Supertrak lines of controllers does not support non-disk devices.
-.Sh FILES
-.Bl -tag -width ".Pa /dev/pstX" -compact
-.It Pa /dev/pstX
-.Nm
-device nodes
-.El
-.Sh NOTES
-The
-.Nm
-driver does not support manipulating the RAID from the OS, RAID's need
-to be setup from the onboard BIOS. However hot swap, hot spare, and
-automatic rebuilds are supported without reboot.
-.Sh HISTORY
-The
-.Nm
-driver first appeared in
-.Fx 4.7 .
-.Sh AUTHORS
-.An -nosplit
-The
-.Nm
-driver and man page were written by
-.An S\(/oren Schmidt Aq Mt sos@FreeBSD.org .
diff --git a/share/man/man4/man4.i386/sbni.4 b/share/man/man4/man4.i386/sbni.4
deleted file mode 100644
index 6e6208c..0000000
--- a/share/man/man4/man4.i386/sbni.4
+++ /dev/null
@@ -1,74 +0,0 @@
-.\" Written by Denis I. Timofeev, 2002.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/sbni.4,v 1.1.2.1 2003/04/15 17:23:32 fjoe Exp $
-.\"
-.Dd January 8, 2002
-.Dt SBNI 4 i386
-.Os
-.Sh NAME
-.Nm sbni
-.Nd Granch SBNI12 leased line modem driver
-.Sh SYNOPSIS
-.Cd "device sbni"
-.Sh DESCRIPTION
-The
-.Nm
-driver provides support for leased line modems of following models:
-.Pp
-.Bl -tag -compact -width ".Pa SBNI12-10, SBNI12D-10, PCI"
-.It Pa SBNI12-05, SBNI12D-05, PCI
-.It Pa SBNI12-10, SBNI12D-10, PCI
-.El
-.Pp
-and a kit for data link over a voice band
-SBNI12-11, SBNI12D-11, PCI.
-.Sh FILES
-The sources for the driver reside in:
-.Pp
-.Bl -tag -compact -width ".Pa /sys/dev/netif/sbni/if_sbnireg.h"
-.It Pa /sys/dev/netif/sbni/if_sbni.c
-.It Pa /sys/dev/netif/sbni/if_sbnireg.h
-.It Pa /sys/dev/netif/sbni/if_sbnivar.h
-.El
-.Sh SEE ALSO
-.Xr arp 4 ,
-.Xr netintro 4 ,
-.Xr ifconfig 8
-.Sh HISTORY
-The
-.Nm
-device driver first appeared in
-.Fx 4.6 .
-.Sh AUTHORS
-The
-.Nm
-device driver for
-.Fx
-4.x was written by Denis I. Timofeev, partially
-based on David Greenman's
-.Nm ed
-driver. Earlier versions (available on ftp.granch.com) were written by
-Alexey V. Zverev.
-.Pp
-SBNI12 hardware was designed by Alexey V. Chirkov.
diff --git a/share/man/man4/man4.i386/spic.4 b/share/man/man4/man4.i386/spic.4
deleted file mode 100644
index e609da4..0000000
--- a/share/man/man4/man4.i386/spic.4
+++ /dev/null
@@ -1,60 +0,0 @@
-.\"
-.\" Copyright (c) 2002 Will Andrews
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/spic.4,v 1.1.2.1 2002/05/20 18:55:34 will Exp $
-.\"
-.Dd May 20, 2002
-.Dt SPIC 4 i386
-.Os
-.Sh NAME
-.Nm spic
-.Nd Sony Programmable I/O Controller device driver
-.Sh SYNOPSIS
-.Cd "device spic"
-.Sh DESCRIPTION
-The
-.Nm
-driver allows using
-.Xr moused 8
-to drive the Sony Vaio Jogdial device found on several Sony Vaio models.
-It works by mapping the forward, backwards, up, and down inputs to
-.Dq l ,
-.Dq r ,
-.Dq u ,
-.Dq d ,
-respectively.
-From that a program reading the Jogdial can decide what to do.
-Some actions might include scrolling, mimicking mouse buttons, launching
-applications, or other useful things.
-.Sh SEE ALSO
-.Xr moused 8
-.Sh HISTORY
-The
-.Nm
-device driver first appeared in
-.Fx 4.6 .
-.Sh AUTHORS
-.An Nick Sayer Aq Mt nsayer@FreeBSD.org
-.An Will Andrews Aq Mt will@FreeBSD.org
diff --git a/share/man/man4/man4.i386/sr.4 b/share/man/man4/man4.i386/sr.4
deleted file mode 100644
index bd0395f..0000000
--- a/share/man/man4/man4.i386/sr.4
+++ /dev/null
@@ -1,141 +0,0 @@
-.\"
-.\" Copyright (c) 1996 John Hay.  All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\"    must display the following acknowledgement:
-.\"        This product includes software developed by John Hay.
-.\" 4. Neither the name of the author nor the names of any co-contributors
-.\"    may be used to endorse or promote products derived from this software
-.\"    without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY John Hay ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL John Hay BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/sr.4,v 1.15.2.4 2001/08/17 13:08:46 ru Exp $
-.\"
-.Dd July 4, 1996
-.Dt SR 4 i386
-.Os
-.Sh NAME
-.Nm sr
-.Nd synchronous RISCom/N2 / WANic 400/405 device driver
-.Sh SYNOPSIS
-.Cd "device sr"
-.Pp
-.Cd "pseudo-device sppp"
-.Sh DESCRIPTION
-The
-.Nm
-driver supports the WANic 400/405 PCI cards
-that are based on the HD64570 chip.
-.Pp
-The standard
-.Dx
-sppp code is used for the link level layer.
-The
-default protocol used is PPP.
-The Cisco HDLC protocol can be used by
-adding
-.Em link2
-to
-.Xr ifconfig 8 .
-.Pp
-Alternately, the driver can be compiled to support
-.Xr netgraph 4
-(see below).
-.Pp
-The
-.Em flags
-field is optional.
-If it isn't specified, the driver will
-assume the following:
-.Bl -hang -offset indent
-.It "The card has 2 ports."
-.It "The clock for the serial ports is external and the transmitter uses"
-the same clock as the receiver.
-.El
-.Pp
-The
-.Em flags
-are a bit field and can be used to force a different
-behaviour than the default.
-.Bl -hang -offset indent
-.It Em 0x01
-The card has only one port.
-.It Em 0x10
-Use separate external clocks for transmit and receive on port 0.
-.It Em 0x40
-Use separate external clocks for transmit and receive on port 1.
-.El
-.Sh NUMBERING
-Only one line for each card is needed in the kernel configuration file.
-The first card's ports will be installed from sr0. The numbering of the
-next card will continue where the first stopped, eg. if the first card
-is a two port card it will use sr0 and sr1. The next card will then
-start at sr2.
-.Pp
-The card only supports IRQ 3, 4, 5, 7, 10, 11, 12 and 15.
-.Pp
-The iomem area is a 16Kb block and must start at a 16Kb boundary.
-.Sh NETGRAPH SUPPORT
-If the kernel is compiled with
-.Cd "options NETGRAPH"
-then the sppp and Cisco HDLC modes are disabled (and the sppp driver
-is unneeded), and this driver functions as a
-.Xr netgraph 4
-node with a single hook named
-.Dv rawdata .
-Connecting to this hook enables the transmission of raw HDLC frames.
-The node will have the same name as the device with ``sync_''
-prepended, e.g.,
-.Dv sync_sr0 .
-.Sh FILES
-.Bl -tag -width ".Pa /sys/dev/netif/sr/if_sr_pci.c" -compact
-.It Pa /sys/dev/netif/sr/if_sr.c
-.It Pa /sys/dev/netif/sr/if_sr.h
-.It Pa /sys/dev/netif/sr/if_sr_pci.c
-.It Pa /sys/dev/netif/sr/if_srregs.h
-.El
-.Sh DIAGNOSTICS
-.Bl -diag
-.It "sr%d: Warning illegal interrupt %d."
-The card cannot use the specified interrupt.
-Choose a different one.
-.El
-.Sh SEE ALSO
-.Xr ar 4 ,
-.Xr netgraph 4 ,
-.Xr netintro 4 ,
-.Xr ifconfig 8
-.Sh AUTHORS
-.An -nosplit
-The
-.Nm
-device driver was written by
-.An John Hay Aq Mt jhay@FreeBSD.org .
-.Pp
-Netgraph support was added by
-.An Julian Elischer Aq Mt julian@FreeBSD.org .
-.Sh BUGS
-At the moment only the X.21 interface is tested.
-The others
-may need tweaks to the clock selection code.
-.Pp
-The code can probably stand some optimizing.
diff --git a/share/man/man4/man4.i386/stl.4 b/share/man/man4/man4.i386/stl.4
deleted file mode 100644
index 2982387..0000000
--- a/share/man/man4/man4.i386/stl.4
+++ /dev/null
@@ -1,86 +0,0 @@
-.\" Copyright (c) 1996-1998 Greg Ungerer (gerg@stallion.oz.au).
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\"    must display the following acknowledgement:
-.\"	This product includes software developed by Greg Ungerer.
-.\" 4. Neither the name of the author nor the names of any co-contributors
-.\"    may be used to endorse or promote products derived from this software
-.\"    without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/usr.sbin/stallion/bootcode/stl.4,v 1.8.2.5 2001/12/14 16:41:52 ru Exp $
-.\"
-.Dd December 1, 2012
-.Dt STL 4 i386
-.Os
-.Sh NAME
-.Nm stl
-.Nd "driver for Stallion Technologies multiport serial controllers"
-.Sh SYNOPSIS
-.Cd "device stl"
-.Sh DESCRIPTION
-The
-.Nm
-driver supports the Stallion Technologies EasyIO,
-EasyConnection 8/32 and
-EasyConnection 8/64-PCI multiport serial boards.
-.Sh CONFIGURATION
-Configuration of the hardware - DIP switches, jumpers, etc - varies
-from board to board.
-Consult documentation supplied with the board for hardware
-configuration details.
-.Sh FILES
-.Bl -tag -width "/dev/staliomem?" -compact
-.It Pa /dev/ttyE?
-stl standard callin devices
-.It Pa /dev/ttyiE?
-stl initial-state callin devices
-.It Pa /dev/ttylE?
-stl lock-state callin devices
-.It Pa /dev/cuaE?
-stl standard callout devices
-.It Pa /dev/cuaiE?
-stl initial-state callout devices
-.It Pa /dev/cualE?
-stl lock-state callout devices
-.It Pa /dev/staliomem?
-board control device
-.El
-.Pp
-Note that the port numbers start at 0 for port 0 of board 0.
-Each board has 64 port slots allocated for it.
-So the second boards ports start at 64 and go through 127.
-.Sh SEE ALSO
-.Xr stty 1 ,
-.Xr termios 4 ,
-.Xr tty 4 ,
-.Xr comcontrol 8 ,
-.Xr stlstats 8
-.Sh HISTORY
-This driver was originally developed by Greg Ungerer (gerg@stallion.com).
-.Sh BUGS
-Device names use integer suffixes, rather than the 0-9 a-z sequence
-that other drivers use.
-.Pp
-There will be many unused ttyE device names in a system with more than
-one card.
diff --git a/share/man/man4/man4.i386/vx.4 b/share/man/man4/man4.i386/vx.4
deleted file mode 100644
index 112746d..0000000
--- a/share/man/man4/man4.i386/vx.4
+++ /dev/null
@@ -1,108 +0,0 @@
-.\"
-.\" Copyright (c) 1996, Fred Gray
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\"    must display the following acknowledgement:
-.\"     This product includes software developed by David Greenman.
-.\" 4. The name of the author may not be used to endorse or promote products
-.\"    derived from this software without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/man4.i386/vx.4,v 1.10.2.5 2001/08/17 13:08:46 ru Exp $
-.\"
-.Dd January 15, 1996
-.Dt VX 4 i386
-.Os
-.Sh NAME
-.Nm vx
-.Nd PCI Ethernet device driver
-.Sh SYNOPSIS
-.Cd "device vx"
-.Sh DESCRIPTION
-The
-.Nm
-driver provides support for the 3Com 3c590 and 3c595 EtherLink III and Fast
-EtherLink III PCI Ethernet cards in 10 Mbps mode.  The medium selection
-can be influenced by the following link flags to the
-.Xr ifconfig 8
-command:
-.Pp
-.Bl -tag -width LINK0X -compact
-.It Em link0
-Use the AUI port.
-.It Em link1
-Use the BNC port.
-.It Em link2
-Use the UTP port.
-.El
-.Sh DIAGNOSTICS
-.Bl -diag
-.It "vx%d: not configured; kernel is built for only %d devices."
-There are not enough devices in the kernel configuration file for the number
-of adapters present in the system.  Add devices to the configuration file,
-rebuild the kernel, and reboot.
-.El
-.Pp
-All other diagnostics indicate either a hardware problem or a bug in the
-driver.
-.Sh CAVEATS
-Some early-revision 3c590 cards are defective and suffer from many receive
-overruns, which cause lost packets.  The author has attempted to implement
-a test for it based on the information supplied by 3Com, but the test resulted
-mostly in spurious warnings.
-.Pp
-The performance of this driver is somewhat limited by the fact that it uses
-only polled-mode I/O and does not make use of the bus-mastering capability
-of the cards.
-.Sh SEE ALSO
-.Xr arp 4 ,
-.Xr netintro 4 ,
-.Xr ng_ether 4 ,
-.Xr ifconfig 8
-.Sh HISTORY
-The
-.Nm
-device driver first appeared in
-.Fx 2.1 .
-It was derived from the
-.Nm ep
-driver, from which it inherits most of its limitations.
-.Sh AUTHORS
-.An -nosplit
-The
-.Nm
-device driver and this manual page were written by
-.An Fred Gray Aq Mt fgray@rice.edu ,
-based on the work of
-.An Herb Peyerl
-and with the assistance of numerous others.
-.Sh BUGS
-The
-.Nm
-driver is known not to reset the adapter correctly following a warm boot
-on some systems.
-.Pp
-The
-.Nm
-driver has not been exhaustively tested with all the models of cards that it
-claims to support.
diff --git a/share/man/man4/man4.i386/tx.4 b/share/man/man4/tx.4
similarity index 96%
rename from share/man/man4/man4.i386/tx.4
rename to share/man/man4/tx.4
index 3bdcf4e..5f15631 100644
--- a/share/man/man4/man4.i386/tx.4
+++ b/share/man/man4/tx.4
@@ -24,10 +24,9 @@
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
 .\" $FreeBSD: src/share/man/man4/man4.i386/tx.4,v 1.11.2.10 2003/02/17 21:20:40 trhodes Exp $
-.\" $DragonFly: src/share/man/man4/man4.i386/tx.4,v 1.6 2008/05/02 02:05:06 swildner Exp $
 .\"
 .Dd February 8, 2001
-.Dt TX 4 i386
+.Dt TX 4
 .Os
 .Sh NAME
 .Nm tx
diff --git a/share/man/man4/man4.i386/viapm.4 b/share/man/man4/viapm.4
similarity index 94%
rename from share/man/man4/man4.i386/viapm.4
rename to share/man/man4/viapm.4
index e7f8404..fa69fe1 100644
--- a/share/man/man4/man4.i386/viapm.4
+++ b/share/man/man4/viapm.4
@@ -25,7 +25,7 @@
 .\" $FreeBSD: src/share/man/man4/man4.i386/viapm.4,v 1.1.2.4 2002/10/10 19:17:58 ceri Exp $
 .\"
 .Dd April 17, 2002
-.Dt VIAPM 4 i386
+.Dt VIAPM 4
 .Os
 .Sh NAME
 .Nm viapm
@@ -39,8 +39,8 @@
 .Cd device viapm
 .Sh DESCRIPTION
 This driver provides access to the
-.Tn VIA chipset Power Management Unit family.They are
-VT82C586B, VT82C596A, VT82C596B, VT82C686A and VT8233.
+.Tn VIA chipset Power Management Unit family.
+They are VT82C586B, VT82C596A, VT82C596B, VT82C686A and VT8233.
 .Pp
 The embedded controller of the VIA chipset may give you access
 to the monitoring facilities of your mainboard.
diff --git a/sys/config/LINT64 b/sys/config/LINT64
index 65302f4..4b4a0d4 100644
--- a/sys/config/LINT64
+++ b/sys/config/LINT64
@@ -313,7 +313,7 @@ device		mn	# Munich32x/Falc54 Nx64kbit/sec cards.
 #  Ethernets; it is MANDATORY when a Ethernet device driver is
 #  configured.
 #  The `sppp' pseudo-device serves a similar role for certain types
-#  of synchronous PPP links (like `ar').
+#  of synchronous PPP links.
 #  The `sl' pseudo-device implements the Serial Line IP (SLIP) service.
 #  The `ppp' pseudo-device implements the Point-to-Point Protocol.
 #  The `bpf' pseudo-device enables the Berkeley Packet Filter.  Be
@@ -1104,7 +1104,7 @@ options 	COM_MULTIPORT		#code for some cards with shared IRQs
 device		puc
 
 #
-# Network interfaces: `ed', `is', `lnc'
+# Network interfaces: `is', `lnc'
 #
 # lnc: Lance/PCnet cards (Isolan, Novell NE2100, NE32-VL, AMD Am7990 & Am79C960)
 # sbsh: Granch SBNI16 SHDSL modem PCI adapters
-- 
2.9.2

