diff options
author | Theo de Raadt <deraadt@cvs.openbsd.org> | 1996-04-22 01:29:01 +0000 |
---|---|---|
committer | Theo de Raadt <deraadt@cvs.openbsd.org> | 1996-04-22 01:29:01 +0000 |
commit | a78513c1a7210b960ecf8ab449672dcd322a720b (patch) | |
tree | 032dce8b4b496e9207ccac70749a466ce0a0bd69 /share/man/man4/man4.arm32/intro.4 | |
parent | 882e83ccf31fca22178b290a6753a605bb52044c (diff) |
sync with netbsd 960418
Diffstat (limited to 'share/man/man4/man4.arm32/intro.4')
-rw-r--r-- | share/man/man4/man4.arm32/intro.4 | 125 |
1 files changed, 125 insertions, 0 deletions
diff --git a/share/man/man4/man4.arm32/intro.4 b/share/man/man4/man4.arm32/intro.4 new file mode 100644 index 00000000000..74df7d5a233 --- /dev/null +++ b/share/man/man4/man4.arm32/intro.4 @@ -0,0 +1,125 @@ +.\" $OpenBSD: intro.4,v 1.1 1996/04/22 01:27:45 deraadt Exp $ +.\" +.\" Copyright (c) 1995 Mark Brinicombe +.\" Copyright (c) 1994 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. +.\" +.\" $Id: intro.4,v 1.1 1996/04/22 01:27:45 deraadt Exp $ +.\" +.Dd +.Dt INTRO 4 arm32 +.Os +.Sh NAME +.Nm intro +.Nd introduction to special files and hardware support +.Sh DESCRIPTION +This section describes the special files, related driver functions, +and networking support +available in the system. +In this part of the manual, the +.Tn SYNOPSIS +section of +each configurable device gives a sample specification +for use in constructing a system description for the +.Xr config 8 +program. +The +.Tn DIAGNOSTICS +section lists messages which may appear on the console +and/or in the system error log +.Pa /var/log/messages +due to errors in device operation; +see +.Xr syslogd 8 +for more information. +.Pp +This section contains both devices +which may be configured into the system +and network related information. +The networking support is introduced in +.Xr netintro 4 . +.Sh DEVICE SUPPORT +This section describes the hardware supported on the arm32 +(RiscPC) platform. +Software support for these devices comes in two forms. A hardware +device may be supported with a character or block +.Em device driver , +or it may be used within the networking subsystem and have a +.Em network interface driver . +Block and character devices are accessed through files in the file +system of a special type; see +.Xr mknod 8 . +Network interfaces are indirectly accessed through the interprocess +communication facilities provided by the system; see +.Xr socket 2 . +.Pp +A hardware device is identified to the system at configuration time +and the appropriate device or network interface driver is then compiled +into the system. When the resultant system is booted, the +autoconfiguration facilities in the system probe for the device +and, if found, enable the software support for it. +If a device does not respond at autoconfiguration +time it is not accessible at any time afterwards. +To enable a device which did not autoconfigure, +the system must be rebooted. +.Pp +The autoconfiguration system is described in +.Xr autoconf 4 . +A list of the supported devices is given below. +.Sh SEE ALSO +.Xr intro 4 , +.Xr autoconf 4 , +.Xr config 8 . +.Sh LIST OF DEVICES +The devices listed below are supported in this incarnation of +the system. Devices are indicated by their functional interface. +Not all supported devices are listed. +.Pp +.Bl -tag -width speaker -offset indent -compact +.It beep +VIDC20 beep device interface +.It com +NS8250-, NS16450-, and NS16550-based asynchronous serial +communications device interface +.It eb +EtherB network slot device interface. +.It quadmouse +RiscPC quadrature mouse device interface. +.It lpt +Parallel port device interface +.It mem +Main memory interface +.It wd +Standard Internal RiscPC IDE deviceinterface +.El +.Sh HISTORY +The +.Tn arm32 +.Nm intro +appeared in +.Nx 1.0a . |