Index: head/libexec/getty/ttys.5
===================================================================
--- head/libexec/getty/ttys.5	(revision 363110)
+++ head/libexec/getty/ttys.5	(revision 363111)
@@ -1,176 +1,179 @@
 .\" Copyright (c) 1985, 1991, 1993
 .\"	The Regents of the University of California.  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 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: @(#)ttys.5	8.1 (Berkeley) 6/4/93
 .\" $FreeBSD$
 .\" "
-.Dd August 3, 2018
+.Dd July 11, 2020
 .Dt TTYS 5
 .Os
 .Sh NAME
 .Nm ttys
 .Nd terminal initialization information
 .Sh DESCRIPTION
 The file
 .Nm
 contains information that is used by various routines to initialize
 and control the use of terminal special files.
 Pseudo-terminals (see
 .Xr pts 4 )
 are not listed.
 This information is read with the
 .Xr getttyent 3
 library routines.
 There is one line in the
 .Nm
 file per special device file.
 Fields are separated by tabs and/or spaces.
 Fields comprised of more than one word should be enclosed in double
 quotes (``"'').
 Blank lines and comments may appear anywhere in the file; comments
 are delimited by hash marks (``#'') and new lines.
 Any unspecified fields will default to null.
 .Pp
 The first field is normally the
 name of the terminal special file as it is found in
 .Pa /dev .
 However, it can be any arbitrary string
 when the associated command is not related to a tty.
 .Pp
 The second field of the file is the command to execute for the line,
 usually
 .Xr getty 8 ,
 which initializes and opens the line, setting the speed, waiting for
 a user name and executing the
 .Xr login 1
 program.
 It can be, however, any desired command, for example
 the start up for a window system terminal emulator or some other
 daemon process, and can contain multiple words if quoted.
 .Pp
 The third field is the type of terminal usually connected to that
 tty line, normally the one found in the
 .Xr termcap 5
 data base file.
 The environment variable
 .Ev TERM
 is initialized with the value by
 either
 .Xr getty 8
 or
 .Xr login 1 .
 .Pp
 The remaining fields set flags in the
 .Fa ty_status
 entry (see
 .Xr getttyent 3 ) ,
 specify a window system process that
 .Xr init 8
 will maintain for the terminal line, optionally determine the
 type of tty (whether dialin, network or otherwise),
 or specify a tty group
 name that allows the login class database (see
 .Xr login.conf 5 )
 to refer to many ttys as a group, to selectively allow or
 deny access or enable or disable accounting facilities for
 ttys as a group.
 .Pp
 As flag values, the strings ``on'' and ``off'' specify that
 .Xr init 8
 should (should not) execute the command given in the second field.
 ``onifconsole'' will cause this line to be enabled if and only if it is
 an active kernel console device (it is equivalent to ``on'' in this
 case).
 The flag ``onifexists'' will cause this line to be enabled if and only
 if the name exists.
 If the name starts with a ``/'', it will be considered an absolute
 path.
 Otherwise, it is considered a path relative to
 .Pa /dev .
 The flag ``secure'' (if the console is enabled) allows users with a
 uid of 0 to login on
 this line.
 The flag ``dialin'' indicates that a tty entry describes a dialin
 line, and ``network'' is obsolete and does nothing.
 Either of these strings may also be specified in the terminal type
 field.
 The string ``window='' may be followed by a quoted command
 string which
 .Xr init 8
 will execute
 .Em before
 starting the command specified by the second field.
 .Pp
 The string ``group='' may be followed by a group name comprised of
 alphanumeric characters that can be used by
 .Xr login.conf 5
 to refer to many tty lines as a group to enable or disable access
 and accounting facilities.
 If no group is specified, then the tty becomes a member of the group
 "none".
 For backwards compatibility, the ``group='' should appear last on the
 line, immediately before the optional comment.
 .Pp
 Both the second field and any command specified with ``window=''
 will be split into words and executed using
 .Xr execve 2 .
 Words are separated by any combinations of tabs and spaces.
 Arguments containing whitespace should be enclosed in single quotes
 .Pq Li ' .
 Note that no shell-style globbing or other variable substitution occurs.
 .Sh FILES
 .Bl -tag -width /etc/ttys -compact
 .It Pa /etc/ttys
 .El
 .Sh EXAMPLES
 .Bd -literal
 # root login on console at 1200 baud
 console	"/usr/libexec/getty std.1200"	vt100	on secure
 # dialup at 1200 baud, no root logins
 ttyd0	"/usr/libexec/getty d1200"	dialup	on group=dialup	# 555-1234
 # Mike's terminal: hp2621
 ttyh0	"/usr/libexec/getty std.9600"	hp2621-nl	on group=dialup	# 457 Evans
 # John's terminal: vt100
 ttyh1	"/usr/libexec/getty std.9600"	vt100	on group=dialup		# 459 Evans
 # terminal emulate/window system
 ttyv0	"/usr/local/bin/xterm -display :0"	xterm	on window="/usr/local/bin/X :0"
 .Ed
 .Sh SEE ALSO
 .Xr login 1 ,
 .Xr getttyent 3 ,
+.Xr nmdm 4 ,
+.Xr uart 4 ,
+.Xr ucom 4 ,
 .Xr gettytab 5 ,
 .Xr login.conf 5 ,
 .Xr termcap 5 ,
 .Xr getty 8 ,
 .Xr init 8 ,
 .Xr pam_securetty 8 ,
 .Xr pstat 8
 .Sh HISTORY
 A
 .Nm
 file appeared in
 .At v6 .
Index: head/share/man/man4/nmdm.4
===================================================================
--- head/share/man/man4/nmdm.4	(revision 363110)
+++ head/share/man/man4/nmdm.4	(revision 363111)
@@ -1,97 +1,98 @@
 .\" Copyright (c) 2001
 .\"	The FreeBSD Project
 .\"
 .\" 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.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHORS 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 AUTHORS 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$
 .\"
-.Dd January 23, 2018
+.Dd July 11, 2020
 .Dt NMDM 4
 .Os
 .Sh NAME
 .Nm nmdm
 .Nd nullmodem terminal driver
 .Sh SYNOPSIS
 To compile this driver into the kernel,
 place the following line in your
 kernel configuration file:
 .Bd -ragged -offset indent
 .Cd "device nmdm"
 .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
 nmdm_load="YES"
 .Ed
 .Sh DESCRIPTION
 The
 .Nm
 driver provides two
 .Xr tty 4
 devices connected
 by a virtual
 .Dq "null modem"
 cable.
 .Pp
 If either of the two tty devices have the
 .Dv CDSR_OFLOW
 bit
 .Pq Dq Li "stty dsrflow"
 set in their line discipline, the
 .Nm
 device will emulate the speed configured in the
 .Xr termios 4
 settings.
 The speed emulation works independently in the two directions,
 controlled by the slower end's termios settings
 .Va ( c_ispeed , c_ospeed ,
 .Dv CS5 ... CS8 , CSTOPB
 and
 .Dv PARENB ) .
 .Sh FILES
 .Bl -tag -width ".Pa /dev/nmdm Ns Ar N Ns Op Pa AB" -compact
 .It Pa /dev/nmdm Ns Ar N Ns Op Pa AB
 nullmodem device nodes.
 Where the
 .Pa A
 node has a matching
 .Pa B
 node.
 .El
 .Pp
 The
 .Nm
 driver implements
 .Dq "on-demand device creation"
 so simply accessing a given instance in
 .Pa /dev
 will create it.
 .Sh DIAGNOSTICS
 None.
 .Sh SEE ALSO
 .Xr stty 1 ,
 .Xr termios 4 ,
-.Xr tty 4
+.Xr tty 4 ,
+.Xr ttys 5
 .Sh HISTORY
 The
 .Nm
 driver first appeared in
 .Fx 4.4 .
Index: head/share/man/man4/uart.4
===================================================================
--- head/share/man/man4/uart.4	(revision 363110)
+++ head/share/man/man4/uart.4	(revision 363111)
@@ -1,301 +1,303 @@
 .\"
 .\" Copyright (c) 2003 Marcel Moolenaar
 .\" 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 ``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$
 .\"
-.Dd April 26, 2017
+.Dd July 11, 2020
 .Dt UART 4
 .Os
 .Sh NAME
 .Nm uart
 .Nd driver for Universal Asynchronous Receiver/Transmitter (UART) devices
 .Sh SYNOPSIS
 .Cd "device uart"
 .Pp
 .Cd "device puc"
 .Cd "device uart"
 .Pp
 .Cd "device scc"
 .Cd "device uart"
 .Pp
 In
 .Pa /boot/device.hints :
 .Cd hint.uart.0.disabled="1"
 .Cd hint.uart.0.baud="38400"
 .Cd hint.uart.0.port="0x3f8"
 .Cd hint.uart.0.flags="0x10"
 .Pp
 With
 .Ar flags
 encoded as:
 .Bl -tag -compact -width 0x000000
 .It 0x00010
 device is potential system console
 .It 0x00080
 use this port for remote kernel debugging
 .It 0x00100
 set RX FIFO trigger level to ``low'' (NS8250 only)
 .It 0x00200
 set RX FIFO trigger level to ``medium low'' (NS8250 only)
 .It 0x00400
 set RX FIFO trigger level to ``medium high'' (default, NS8250 only)
 .It 0x00800
 set RX FIFO trigger level to ``high'' (NS8250 only)
 .El
 .\"
 .Sh DESCRIPTION
 The
 .Nm
 device driver provides support for various classes of UARTs implementing the
 EIA RS-232C (CCITT V.24) serial communications interface.
 Each such interface is controlled by a separate and independent instance of
 the
 .Nm
 driver.
 The primary support for devices that contain multiple serial interfaces or
 that contain other functionality besides one or more serial interfaces is
 provided by the
 .Xr puc 4 ,
 or
 .Xr scc 4
 device drivers.
 However, the serial interfaces of those devices that are managed by the
 .Xr puc 4 ,
 or
 .Xr scc 4
 driver are each independently controlled by the
 .Nm
 driver.
 As such, the
 .Xr puc 4 ,
 or
 .Xr scc 4
 driver provides umbrella functionality for the
 .Nm
 driver and hides the complexities that are inherent when elementary components
 are packaged together.
 .Pp
 The
 .Nm
 driver has a modular design to allow it to be used on differing hardware and
 for various purposes.
 In the following sections the components are discussed in detail.
 Options are described in the section that covers the component to which each
 option applies.
 .\"
 .Ss CORE COMPONENT
 At the heart of the
 .Nm
 driver is the core component.
 It contains the bus attachments and the low-level interrupt handler.
 .\"
 .Ss HARDWARE DRIVERS
 The core component and the kernel interfaces talk to the hardware through the
 hardware interface.
 This interface serves as an abstraction of the hardware and allows varying
 UARTs to be used for serial communications.
 .\"
 .Ss SYSTEM DEVICES
 System devices are UARTs that have a special purpose by way of hardware
 design or software setup.
 For example, Sun UltraSparc machines use UARTs as their keyboard interface.
 Such an UART cannot be used for general purpose communications.
 Likewise, when the kernel is configured for a serial console, the
 corresponding UART will in turn be a system device so that the kernel can
 output boot messages early on in the boot process.
 .\"
 .Ss KERNEL INTERFACES
 The last but not least of the components is the kernel interface.
 This component ultimately determines how the UART is made visible to the
 kernel in particular and to users in general.
 The default kernel interface is the TTY interface.
 This allows the UART to be used for terminals, modems and serial line IP
 applications.
 System devices, with the notable exception of serial consoles, generally
 have specialized kernel interfaces.
 .\"
 .Sh HARDWARE
 The
 .Nm
 driver supports the following classes of UARTs:
 .Pp
 .Bl -bullet -compact
 .It
 NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or
 the 16950 UARTs.
 .It
 SCC: serial communications controllers supported by the
 .Xr scc 4
 device driver.
 .El
 .\"
 .Sh Pulse Per Second (PPS) Timing Interface
 The
 .Nm
 driver can capture PPS timing information as defined in RFC 2783.
 The API, accessed via
 .Xr ioctl 2 ,
 is available on the tty device.
 To use the PPS capture feature with
 .Xr ntpd 8 ,
 symlink the tty callout device
 .Va /dev/cuau?
 to
 .Va /dev/pps0.
 .Pp
 The
 .Va hw.uart.pps_mode
 tunable configures the PPS capture mode for all uart devices;
 it can be set in
 .Xr loader.conf 5 .
 The
 .Va dev.uart.0.pps_mode
 sysctl configures the PPS capture mode for a specific uart device;
 it can be set in
 .Xr loader.conf 5
 or
 .Xr sysctl.conf 5 .
 .Pp
 The following capture modes are available:
 .Bl -tag -compact -offset "mmmm" -width "mmmm"
 .It 0x00
 Capture disabled.
 .It 0x01
 Capture pulses on the CTS line.
 .It 0x02
 Capture pulses on the DCD line.
 .El
 .Pp
 The following values may be ORed with the capture mode to configure
 capture processing options:
 .Bl -tag -compact -offset "mmmm" -width "mmmm"
 .It 0x10
 Invert the pulse (RS-232 logic low = ASSERT, high = CLEAR).
 .It 0x20
 Attempt to capture narrow pulses.
 .El
 .Pp
 Add the narrow pulse option when the incoming PPS pulse width is small
 enough to prevent reliable capture in normal mode.
 In narrow mode the driver uses the hardware's ability to latch a line
 state change; not all hardware has this capability.
 The hardware latch provides a reliable indication that a pulse occurred,
 but prevents distinguishing between the CLEAR and ASSERT edges of the pulse.
 For each detected pulse, the driver synthesizes both an ASSERT and a CLEAR
 event, using the same timestamp for each.
 To prevent spurious events when the hardware is intermittently able to
 see both edges of a pulse, the driver will not generate a new pair of
 events within a half second of the prior pair.
 Both normal and narrow pulse modes work with
 .Xr ntpd 8 .
 .Pp
 Add the invert option when the connection to the uart device uses TTL
 level signals, or when the PPS source emits inverted pulses.
 RFC 2783 defines an ASSERT event as a higher-voltage line level, and a CLEAR
 event as a lower-voltage line level, in the context of the RS-232 protocol.
 The modem control signals on a TTL-level connection are typically
 inverted from the RS-232 levels.
 For example, carrier presence is indicated by a high signal on an RS-232
 DCD line, and by a low signal on a TTL DCD line.
 This is due to the use of inverting line driver buffers to convert between
 TTL and RS-232 line levels in most hardware designs.
 Generally speaking, a connection to a DB-9 style connector is an RS-232
 level signal at up to 12 volts.
 A connection to header pins or an edge-connector on an embedded board
 is typically a TTL signal at 3.3 or 5 volts.
 .Sh Special Devices
 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 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.
 E.g., to lock a speed to 115200, use
 .Dq Li stty 115200
 on the initial-state device and
 .Dq Li stty 1
 on the lock-state device.
 .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 do not
 support it at all.
 CLOCAL should be locked on for devices that do not support carrier.
 HUPCL may be locked off if you do not
 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
 .Bl -tag -width "/dev/ttyu?.init" -compact
 .It Pa /dev/ttyu?
 for callin ports
 .It Pa /dev/ttyu?.init
 .It Pa /dev/ttyu?.lock
 corresponding callin initial-state and lock-state devices
 .Pp
 .It Pa /dev/cuau?
 for callout ports
 .It Pa /dev/cuau?.init
 .It Pa /dev/cuau?.lock
 corresponding callout initial-state and lock-state devices
 .El
 .Sh SEE ALSO
+.Xr cu 1 ,
 .Xr puc 4 ,
-.Xr scc 4
+.Xr scc 4 ,
+.Xr ttys 5
 .\"
 .Sh HISTORY
 The
 .Nm
 device driver first appeared in
 .Fx 5.2 .
 .Sh AUTHORS
 The
 .Nm
 device driver and this manual page were written by
 .An Marcel Moolenaar Aq Mt marcel@xcllnt.net .
Index: head/share/man/man4/ucom.4
===================================================================
--- head/share/man/man4/ucom.4	(revision 363110)
+++ head/share/man/man4/ucom.4	(revision 363111)
@@ -1,166 +1,168 @@
 .\" $NetBSD: ucom.4,v 1.9 2002/03/22 00:39:40 augustss Exp $
 .\"
 .\" Copyright (c) 1999 The NetBSD Foundation, Inc.
 .\" All rights reserved.
 .\"
 .\" This code is derived from software contributed to The NetBSD Foundation
 .\" by Lennart Augustsson.
 .\"
 .\" 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 NETBSD FOUNDATION, INC. 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 FOUNDATION 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$
 .\"
-.Dd April 25, 2018
+.Dd July 11, 2020
 .Dt UCOM 4
 .Os
 .Sh NAME
 .Nm ucom
 .Nd USB tty support
 .Sh SYNOPSIS
 To compile this driver into the kernel,
 place the following line in your
 kernel configuration file:
 .Bd -ragged -offset indent
 .Cd "device ucom"
 .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
 ucom_load="YES"
 .Ed
 .Sh DESCRIPTION
 The
 .Nm
 driver attaches to USB modems, serial ports, and other devices that need
 to look like a tty.
 The
 .Nm
 driver shows a behavior like a
 .Xr tty 4 .
 This means that normal programs such as
 .Xr tip 1
 or
 .Xr ppp 8
 can be used to access the device.
 .Sh SYSCTL VARIABLES
 The following variables are available as both
 .Xr sysctl 8
 variables and
 .Xr loader 8
 tunables:
 .Bl -tag -width indent
 .It Va hw.usb.ucom.debug
 Debug output level, where 0 is debugging disabled and larger values increase
 debug message verbosity.
 Default is 0.
 .It Va hw.usb.ucom.device_mode_console
 When set to 1, the
 .Nm
 driver will mark terminals as console devices when operating in device mode.
 Default is 1.
 .It Va hw.usb.ucom.pps_mode
 Enables and configure PPS capture mode as described below.
 .El
 .Sh Pulse Per Second (PPS) Timing Interface
 The
 .Nm
 driver can capture PPS timing information as defined in RFC 2783.
 The API, accessed via
 .Xr ioctl 2 ,
 is available on the tty device.
 To use the PPS capture feature with
 .Xr ntpd 8 ,
 symlink the tty device to
 .Va /dev/pps0.
 .Pp
 The
 .Va hw.usb.ucom.pps_mode
 sysctl configures the PPS capture mode.
 It can be set in
 .Xr loader.conf 5
 or
 .Xr sysctl.conf 5 .
 The following capture modes are available:
 .Bl -tag -compact -offset "mmmm" -width "mmmm"
 .It 0
 Capture disabled (default).
 .It 1
 Capture pulses on the CTS line.
 .It 2
 Capture pulses on the DCD line.
 .El
 .Sh FILES
 .Bl -tag -width "/dev/ttyU*.init" -compact
 .It Pa /dev/ttyU*
 for callin ports
 .It Pa /dev/ttyU*.init
 .It Pa /dev/ttyU*.lock
 corresponding callin initial-state and lock-state devices
 .Pp
 .It Pa /dev/cuaU*
 for callout ports
 .It Pa /dev/cuaU*.init
 .It Pa /dev/cuaU*.lock
 corresponding callout initial-state and lock-state devices
 .El
 .Sh SEE ALSO
+.Xr cu 1 ,
 .Xr tty 4 ,
 .Xr uark 4 ,
 .Xr ubsa 4 ,
 .Xr ubser 4 ,
 .Xr uchcom 4 ,
 .Xr ucycom 4 ,
 .Xr ufoma 4 ,
 .Xr uftdi 4 ,
 .Xr uhso 4 ,
 .\".Xr ugensa 4 ,
 .Xr uipaq 4 ,
 .Xr umcs 4 ,
 .Xr umct 4 ,
 .Xr umodem 4 ,
 .Xr umoscom 4 ,
 .Xr uplcom 4 ,
 .Xr usb 4 ,
 .Xr uslcom 4 ,
 .Xr uvisor 4 ,
-.Xr uvscom 4
+.Xr uvscom 4 ,
+.Xr ttys 5
 .Sh HISTORY
 The
 .Nm
 driver was adopted from
 .Nx
 in March of 2002.
 This manual page was adopted from
 .Nx
 by
 .An Tom Rhodes Aq Mt trhodes@FreeBSD.org
 in April 2002.
 .Sh BUGS
 Prior to
 .Fx 6.0
 .Nm
 created
 .Pa /dev/ucom?
 rather than the uniform device names created today.
 Old scripts must be adjusted accordingly.