1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
.\" $OpenBSD: intro.4,v 1.7 2002/01/18 21:42:09 jason Exp $
.\"
.\" Copyright (c) 2001 The OpenBSD Project
.\" All Rights Reserved.
.\"
.Dd October 4, 2001
.Dt INTRO 4 sparc64
.Os
.Sh NAME
.Nm intro
.Nd introduction to special files and hardware support
.Sh DESCRIPTION
The manual pages in section 4 describe 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
sparc64
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 will have to be rebooted.
.Pp
The autoconfiguration system is described in
.Xr autoconf 4 .
A list of the supported devices is given below.
.Sh LIST OF DEVICES
The devices listed below are supported in this incarnation of
the system.
Pseudo-devices are not listed.
Devices are indicated by their functional interface.
Not all supported devices are listed.
.Pp
.Bl -tag -width le/lebuffer -compact -offset indent
.It audioce
EBus CS4231 based audio.
.It audiocs
SBus CS4231 based audio.
.It be
10BaseT/100BaseTX SBus Ethernet controller.
.It cgsix
8 bit SBus color graphics frame buffer.
.It cgthree
8 bit SBus color graphics frame buffer.
.It esp
ESP SCSI controller.
.It hme
SBus HME Ethernet controllers (SunSwift).
.It isp
Qlogic ISP SBus SCSI controller.
.It le/lebuffer
AMD 7990 LANCE ethernet controller.
.It magma
MAGMA serial/parallel communication boards.
.It openprom
Sun Open boot PROM (what became IEEE 1275) configuration driver.
.It qe
Quad 10BaseT SBus Ethernet controller.
.It qec
Supported as carrier for
.Nm be
or
.Nm qe
Ethernet controllers.
.It sab
Infineon (formerly Siemens) SAB82532 serial controller.
.It spif
Sun SUNW,spif serial/parallel communication boards.
.It zs
Zilog 8530 serial controller.
.El
.Sh SEE ALSO
.Xr autoconf 4 ,
.Xr config 8
.Sh HISTORY
The
sparc64
.Nm intro
first appeared in
.Ox 3.0 .
|
