| uart.4 (63d46d1d5e917088f08cafa7f9b328073417d7e7) | uart.4 (27d5dc189c8e2eaf1cbe7e47078bf065854ba210) |
|---|---|
| 1.\" 2.\" Copyright (c) 2003 Marcel Moolenaar 3.\" All rights reserved. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 8.\" --- 11 unchanged lines hidden (view full) --- 20.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 21.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 22.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 23.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 24.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 25.\" 26.\" $FreeBSD$ 27.\" | 1.\" 2.\" Copyright (c) 2003 Marcel Moolenaar 3.\" All rights reserved. 4.\" 5.\" Redistribution and use in source and binary forms, with or without 6.\" modification, are permitted provided that the following conditions 7.\" are met: 8.\" --- 11 unchanged lines hidden (view full) --- 20.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 21.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 22.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 23.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 24.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 25.\" 26.\" $FreeBSD$ 27.\" |
| 28.Dd March 12, 2008 | 28.Dd August 25, 2003 |
| 29.Dt UART 4 30.Os | 29.Dt UART 4 30.Os |
| 31.\" |
|
| 31.Sh NAME 32.Nm uart 33.Nd driver for Universal Asynchronous Receiver/Transmitter (UART) devices | 32.Sh NAME 33.Nm uart 34.Nd driver for Universal Asynchronous Receiver/Transmitter (UART) devices |
| 35.\" |
|
| 34.Sh SYNOPSIS 35.Cd "device uart" 36.Pp 37.Cd "device puc" 38.Cd "device uart" 39.Pp | 36.Sh SYNOPSIS 37.Cd "device uart" 38.Pp 39.Cd "device puc" 40.Cd "device uart" 41.Pp |
| 40.Cd "device scc" 41.Cd "device uart" 42.Pp 43In 44.Pa /boot/device.hints : 45.Cd hint.uart.0.disabled="1" 46.Cd hint.uart.0.baud="38400" 47.Cd hint.uart.0.port="0x3f8" 48.Cd hint.uart.0.flags="0x10" 49.Pp 50With 51.Ar flags 52encoded as: 53.Bl -tag -compact -width 0x000000 54.It 0x00010 55device is potential system console 56.It 0x00080 57use this port for remote kernel debugging 58.It 0x00100 59set RX FIFO trigger level to ``low'' (NS8250 only) 60.It 0x00200 61set RX FIFO trigger level to ``medium low'' (NS8250 only) 62.It 0x00400 63set RX FIFO trigger level to ``medium high'' (default, NS8250 only) 64.It 0x00800 65set RX FIFO trigger level to ``high'' (NS8250 only) 66.El | |
| 67.\" 68.Sh DESCRIPTION 69The 70.Nm 71device driver provides support for various classes of UARTs implementing the 72EIA RS-232C (CCITT V.24) serial communications interface. | 42.\" 43.Sh DESCRIPTION 44The 45.Nm 46device driver provides support for various classes of UARTs implementing the 47EIA RS-232C (CCITT V.24) serial communications interface. |
| 73Each such interface is controlled by a separate and independent instance of | 48Each such interface is controlled by a seperate and independent instance of |
| 74the 75.Nm 76driver. 77The primary support for devices that contain multiple serial interfaces or 78that contain other functionality besides one or more serial interfaces is 79provided by the | 49the 50.Nm 51driver. 52The primary support for devices that contain multiple serial interfaces or 53that contain other functionality besides one or more serial interfaces is 54provided by the |
| 80.Xr puc 4 , 81or 82.Xr scc 4 83device drivers. | 55.Xr puc 4 56device driver. |
| 84However, the serial interfaces of those devices that are managed by the | 57However, the serial interfaces of those devices that are managed by the |
| 85.Xr puc 4 , 86or 87.Xr scc 4 88driver are each independently controlled by the | 58.Xr puc 4 59driver are controlled by the |
| 89.Nm 90driver. 91As such, the | 60.Nm 61driver. 62As such, the |
| 92.Xr puc 4 , 93or 94.Xr scc 4 | 63.Xr puc 4 |
| 95driver provides umbrella functionality for the 96.Nm 97driver and hides the complexities that are inherent when elementary components 98are packaged together. 99.Pp 100The 101.Nm 102driver has a modular design to allow it to be used on differing hardware and 103for various purposes. 104In the following sections the components are discussed in detail. 105Options are described in the section that covers the component to which each 106option applies. 107.\" 108.Ss CORE COMPONENT 109At the heart of the 110.Nm | 64driver provides umbrella functionality for the 65.Nm 66driver and hides the complexities that are inherent when elementary components 67are packaged together. 68.Pp 69The 70.Nm 71driver has a modular design to allow it to be used on differing hardware and 72for various purposes. 73In the following sections the components are discussed in detail. 74Options are described in the section that covers the component to which each 75option applies. 76.\" 77.Ss CORE COMPONENT 78At the heart of the 79.Nm |
| 111driver is the core component. 112It contains the bus attachments and the low-level interrupt handler. | 80driver is the core component. It contains the bus attachments and the low-level 81interrupt handler. |
| 113.\" 114.Ss HARDWARE DRIVERS 115The core component and the kernel interfaces talk to the hardware through the 116hardware interface. 117This interface serves as an abstraction of the hardware and allows varying 118UARTs to be used for serial communications. 119.\" 120.Ss SYSTEM DEVICES --- 10 unchanged lines hidden (view full) --- 131This component ultimately determines how the UART is made visible to the 132kernel in particular and to users in general. 133The default kernel interface is the TTY interface. 134This allows the UART to be used for terminals, modems and serial line IP 135applications. 136System devices, with the notable exception of serial consoles, generally 137have specialized kernel interfaces. 138.\" | 82.\" 83.Ss HARDWARE DRIVERS 84The core component and the kernel interfaces talk to the hardware through the 85hardware interface. 86This interface serves as an abstraction of the hardware and allows varying 87UARTs to be used for serial communications. 88.\" 89.Ss SYSTEM DEVICES --- 10 unchanged lines hidden (view full) --- 100This component ultimately determines how the UART is made visible to the 101kernel in particular and to users in general. 102The default kernel interface is the TTY interface. 103This allows the UART to be used for terminals, modems and serial line IP 104applications. 105System devices, with the notable exception of serial consoles, generally 106have specialized kernel interfaces. 107.\" |
| 139.Sh HARDWARE 140The 141.Nm 142driver supports the following classes of UARTs: 143.Pp 144.Bl -bullet -compact 145.It 146NS8250: standard hardware based on the 8250, 16450, 16550, 16650, 16750 or 147the 16950 UARTs. 148.It 149SCC: serial communications controllers supported by the 150.Xr scc 4 151device driver. 152.El 153.\" 154.Sh FILES 155.Bl -tag -width ".Pa /dev/ttyu?.init" -compact 156.It Pa /dev/ttyu? 157for callin ports 158.It Pa /dev/ttyu?.init 159.It Pa /dev/ttyu?.lock 160corresponding callin initial-state and lock-state devices 161.Pp 162.It Pa /dev/cuau? 163for callout ports 164.It Pa /dev/cuau?.init 165.It Pa /dev/cuau?.lock 166corresponding callout initial-state and lock-state devices 167.El | |
| 168.Sh SEE ALSO | 108.Sh SEE ALSO |
| 169.Xr puc 4 , 170.Xr scc 4 | 109.Xr puc 4 |
| 171.\" 172.Sh HISTORY 173The 174.Nm 175device driver first appeared in 176.Fx 5.2 . | 110.\" 111.Sh HISTORY 112The 113.Nm 114device driver first appeared in 115.Fx 5.2 . |
| 177.Sh AUTHORS 178The 179.Nm 180device driver and this manual page were written by 181.An Marcel Moolenaar Aq marcel@xcllnt.net . | |