Spelling fixes.
Submitted by: Josh Gilliam <josh@quick.net> PR: 6880
This commit is contained in:
parent
42ef2606c3
commit
68bf8f9eea
@ -139,7 +139,7 @@ from the list(s). The values which it will take and recognise are FR_INQUE
|
||||
and FR_OUTQUE (see above).
|
||||
|
||||
\fBGeneral Logging Flags\fP
|
||||
There are two flags which can be set to log packets independantly of the
|
||||
There are two flags which can be set to log packets independently of the
|
||||
rules used. These allow for packets which are either passed or blocked
|
||||
to be logged. To set (and clear)/get these flags, two ioctls are
|
||||
provided:
|
||||
|
@ -26,7 +26,7 @@ being that the fd must be that of the device associated with the module
|
||||
(i.e., /dev/ipl).
|
||||
.LP
|
||||
.PP
|
||||
The strcture used with the NAT interface is described below:
|
||||
The structure used with the NAT interface is described below:
|
||||
.LP
|
||||
.nf
|
||||
typedef struct ipnat {
|
||||
|
@ -24,7 +24,7 @@
|
||||
.\" (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: ahc.4,v 1.9 1997/05/30 15:43:36 max Exp $
|
||||
.\" $Id: ahc.4,v 1.10 1998/03/12 07:30:30 charnier Exp $
|
||||
.\"
|
||||
.Dd April 20, 1996
|
||||
.Dt AHC 4 i386
|
||||
@ -101,7 +101,7 @@ seek distance,
|
||||
and to increase throughput.
|
||||
Tagged queueing can have a significant impact on performance for seek
|
||||
bound applications and should be enabled for most configurations.
|
||||
Unfortunantly, some devices that claim to support tagged queueing fail
|
||||
Unfortunately, some devices that claim to support tagged queueing fail
|
||||
miserable when it is used.
|
||||
The only reason tagged queueing remains as a controller option is as a
|
||||
stop gap measure until a mechanism to detect these broken devices and to
|
||||
|
@ -28,7 +28,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: ed.4,v 1.10 1997/03/21 20:13:43 mpp Exp $
|
||||
.\" $Id: ed.4,v 1.11 1998/03/12 07:30:31 charnier Exp $
|
||||
.\"
|
||||
.Dd October 28, 1995
|
||||
.Dt ED 4 i386
|
||||
@ -46,7 +46,7 @@ The
|
||||
driver provides support for 8 and 16bit ISA ethernet cards that are based on
|
||||
the National Semiconductor DS8390 and similar NICs manufactured by other companies.
|
||||
.Pp
|
||||
It supports all 80x3 series ISA ethernet cards manufatured by Western Digital and SMC,
|
||||
It supports all 80x3 series ISA ethernet cards manufactured by Western Digital and SMC,
|
||||
the SMC Ultra, the 3Com 3c503, the Novell NE1000/NE2000, and HP PC Lan+.
|
||||
.Pp
|
||||
The
|
||||
@ -64,7 +64,7 @@ interface type (AUI/BNC, and for cards with twisted pair, AUI/10BaseT).
|
||||
.Pp
|
||||
The
|
||||
.Em flags
|
||||
are a bit field, and are summerized as follows:
|
||||
are a bit field, and are summarized as follows:
|
||||
.Pp
|
||||
.Bl -hang -offset indent
|
||||
.It Em 0x01
|
||||
@ -135,7 +135,7 @@ too fast.
|
||||
.El
|
||||
.Sh CAVEATS
|
||||
Early revision DS8390 chips have problems. They lock up whenever the receive
|
||||
ring-buffer overflows. They occassionally switch the byte order
|
||||
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 "NIC
|
||||
memory corrupt - invalid packet length" messages. The card is reset
|
||||
@ -148,7 +148,7 @@ 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 acheived by specifying
|
||||
work in 8bit mode, much higher performance can be achieved by specifying
|
||||
.Em "flags 0x04"
|
||||
(force 16bit mode) in your kernel config file. In addition, you should also specify
|
||||
.Em "iosize 16384"
|
||||
|
@ -1,5 +1,5 @@
|
||||
.\"
|
||||
.\" $Id: keyboard.4,v 1.12 1997/03/09 20:53:20 jmg Exp $
|
||||
.\" $Id: keyboard.4,v 1.13 1998/03/12 07:30:34 charnier Exp $
|
||||
.\"
|
||||
.Dd January 8, 1995
|
||||
.Dt KEYBOARD 4 i386
|
||||
@ -78,7 +78,7 @@ represented by the map array, as shown below:
|
||||
---- ------------------------------------------------------
|
||||
0x1E 'a' 'A' 0x01 0x01 'a' 'A' 0x01 0x01
|
||||
|
||||
This is the default mapping for the key labelled 'A' wich normally has
|
||||
This is the default mapping for the key labelled 'A' which normally has
|
||||
scancode 0x1E. The eight states is as shown, giving the 'A' key its
|
||||
normal behavior.
|
||||
The spcl field is used to give the key "special" treatment, and is
|
||||
@ -113,7 +113,7 @@ The field keynum defines which function key that is programmed.
|
||||
The array keydef should contain the new string to be used (MAXFK long),
|
||||
and the length should be entered in flen.
|
||||
|
||||
The GETFKEY ioctl call works in a semilar manner, execpt it returns
|
||||
The GETFKEY ioctl call works in a similar manner, execpt it returns
|
||||
the current setting of keynum.
|
||||
|
||||
The function keys are numbered like this:
|
||||
|
@ -24,7 +24,7 @@
|
||||
.\" (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: ahc.4,v 1.9 1997/05/30 15:43:36 max Exp $
|
||||
.\" $Id: ahc.4,v 1.10 1998/03/12 07:30:30 charnier Exp $
|
||||
.\"
|
||||
.Dd April 20, 1996
|
||||
.Dt AHC 4 i386
|
||||
@ -101,7 +101,7 @@ seek distance,
|
||||
and to increase throughput.
|
||||
Tagged queueing can have a significant impact on performance for seek
|
||||
bound applications and should be enabled for most configurations.
|
||||
Unfortunantly, some devices that claim to support tagged queueing fail
|
||||
Unfortunately, some devices that claim to support tagged queueing fail
|
||||
miserable when it is used.
|
||||
The only reason tagged queueing remains as a controller option is as a
|
||||
stop gap measure until a mechanism to detect these broken devices and to
|
||||
|
@ -125,7 +125,7 @@ Stops the clocked accumulation of sample values into a channel's driver fifo.
|
||||
On the \fIAIO8-P\fP, interrupt driven conversion (the only type
|
||||
supported by the
|
||||
.Nm
|
||||
driver) is facilitated through 8253 timer #2. In order for interrrupts to
|
||||
driver) is facilitated through 8253 timer #2. In order for interrupts to
|
||||
be generated you must connect line 6 to line 24 (counter 2 output to
|
||||
interrupt input) and line 23 to line 29 (counter 2 gate to +5VDC).
|
||||
The design of the \fIAIO8-P\fP precludes the use of programmable
|
||||
|
@ -9,7 +9,7 @@
|
||||
.\" the author assume any responsibility for damages incurred with its
|
||||
.\" use.
|
||||
.\"
|
||||
.\" $Id: apm.4,v 1.6 1997/02/22 13:25:11 peter Exp $
|
||||
.\" $Id: apm.4,v 1.7 1998/02/20 07:19:51 hosokawa Exp $
|
||||
.\"
|
||||
.Dd November 1, 1994
|
||||
.Dt APM 4 i386
|
||||
@ -117,7 +117,7 @@ today are buggy. You may be putting your LCD-display and batteries at
|
||||
a risk by using this interface. (The reason this isn't a problem for
|
||||
MS-windows is that they use the real-mode interface.) If you see any
|
||||
weird behaviour from your system with this code in use, unplug the
|
||||
power and batteries ASAP, if not imidiately, and disable this code.
|
||||
power and batteries ASAP, if not immediately, and disable this code.
|
||||
.Pp
|
||||
We are very interested in getting this code working, so please send you
|
||||
observations of any anormalous behaviour to us.
|
||||
|
@ -28,7 +28,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: ar.4,v 1.6 1997/03/21 20:13:40 mpp Exp $
|
||||
.\" $Id: ar.4,v 1.7 1998/03/12 07:30:30 charnier Exp $
|
||||
.\"
|
||||
.Dd November 19, 1995
|
||||
.Dt AR 4 i386
|
||||
@ -37,7 +37,7 @@
|
||||
.Nm ar
|
||||
.Nd
|
||||
synchronous Arnet device driver.
|
||||
.Sh SYNOPSYS
|
||||
.Sh SYNOPSIS
|
||||
.Cd "device ar0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector arintr"
|
||||
.Cd "device ar1 at isa? port 0x310 net irq 11 iomem 0xd0000 vector arintr"
|
||||
.Pp
|
||||
|
@ -29,7 +29,7 @@
|
||||
.\" (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$
|
||||
.\" $Id: asc.4,v 1.6 1997/02/22 13:25:13 peter Exp $
|
||||
.Dd January 19, 1995
|
||||
.Dt ASC 4 i386
|
||||
.Os FreeBSD
|
||||
@ -133,7 +133,7 @@ Consequently, the selections are
|
||||
.Em not
|
||||
reset when the device is opened or closed.
|
||||
.Pp
|
||||
Similarily, requests that read a value do not report the value that is
|
||||
Similarly, requests that read a value do not report the value that is
|
||||
used for the ongoing scan process. The values needed during the scan
|
||||
process are saved when it starts and thus are not accessed by
|
||||
.Fn ioctl
|
||||
|
@ -28,7 +28,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: ed.4,v 1.10 1997/03/21 20:13:43 mpp Exp $
|
||||
.\" $Id: ed.4,v 1.11 1998/03/12 07:30:31 charnier Exp $
|
||||
.\"
|
||||
.Dd October 28, 1995
|
||||
.Dt ED 4 i386
|
||||
@ -46,7 +46,7 @@ The
|
||||
driver provides support for 8 and 16bit ISA ethernet cards that are based on
|
||||
the National Semiconductor DS8390 and similar NICs manufactured by other companies.
|
||||
.Pp
|
||||
It supports all 80x3 series ISA ethernet cards manufatured by Western Digital and SMC,
|
||||
It supports all 80x3 series ISA ethernet cards manufactured by Western Digital and SMC,
|
||||
the SMC Ultra, the 3Com 3c503, the Novell NE1000/NE2000, and HP PC Lan+.
|
||||
.Pp
|
||||
The
|
||||
@ -64,7 +64,7 @@ interface type (AUI/BNC, and for cards with twisted pair, AUI/10BaseT).
|
||||
.Pp
|
||||
The
|
||||
.Em flags
|
||||
are a bit field, and are summerized as follows:
|
||||
are a bit field, and are summarized as follows:
|
||||
.Pp
|
||||
.Bl -hang -offset indent
|
||||
.It Em 0x01
|
||||
@ -135,7 +135,7 @@ too fast.
|
||||
.El
|
||||
.Sh CAVEATS
|
||||
Early revision DS8390 chips have problems. They lock up whenever the receive
|
||||
ring-buffer overflows. They occassionally switch the byte order
|
||||
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 "NIC
|
||||
memory corrupt - invalid packet length" messages. The card is reset
|
||||
@ -148,7 +148,7 @@ 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 acheived by specifying
|
||||
work in 8bit mode, much higher performance can be achieved by specifying
|
||||
.Em "flags 0x04"
|
||||
(force 16bit mode) in your kernel config file. In addition, you should also specify
|
||||
.Em "iosize 16384"
|
||||
|
@ -28,7 +28,7 @@
|
||||
.\" (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: gsc.4,v 1.7 1997/05/19 16:33:25 eivind Exp $
|
||||
.\" $Id: gsc.4,v 1.8 1998/03/12 07:30:33 charnier Exp $
|
||||
.\"
|
||||
.Dd January 9, 1995
|
||||
.Os FreeBSD
|
||||
@ -102,7 +102,7 @@ supplied in
|
||||
.Em pnm
|
||||
mode since the driver must know at what time the
|
||||
'end-of-file' shall be reached. With this feature you are able to
|
||||
directly copy the scanner output into a pbm file whith
|
||||
directly copy the scanner output into a pbm file with
|
||||
.Xr cat .
|
||||
Of course you can obtain a similar effect by using
|
||||
.Xr dd 1
|
||||
@ -184,7 +184,7 @@ mode. This is actually
|
||||
a limit on the amount of lines scannable after the first read
|
||||
operation. When the limit is reached read will return 0. However, the
|
||||
device is turned off only when a close is performed (either
|
||||
explicitely or implicitely on exit of the calling process).
|
||||
explicitly or implicitly on exit of the calling process).
|
||||
.It GSC_GHEIGHT int
|
||||
Get the current height of the bitmap.
|
||||
.It GSC_SBLEN int
|
||||
@ -220,7 +220,7 @@ request that follows open. You must close the device and open it again
|
||||
for the new selections to take effect. Consequently, the selections
|
||||
are not reset when you close or open the device.
|
||||
.Pp
|
||||
Similarily, requests that read a value do not report the value that is
|
||||
Similarly, requests that read a value do not report the value that is
|
||||
used for the ongoing scan process. The values needed during the scan
|
||||
process are saved when it starts and thus are not accessed by ioctl
|
||||
requests.
|
||||
@ -249,7 +249,7 @@ output, has minor number 0.
|
||||
.It Pa /dev/gsc0d
|
||||
device node for
|
||||
.Em raw
|
||||
output emiting
|
||||
output emitting
|
||||
.Em debug
|
||||
messages if the
|
||||
GSCDEBUG option was given at compile time, has minor number 32.
|
||||
|
@ -1,5 +1,5 @@
|
||||
.\"
|
||||
.\" $Id: keyboard.4,v 1.12 1997/03/09 20:53:20 jmg Exp $
|
||||
.\" $Id: keyboard.4,v 1.13 1998/03/12 07:30:34 charnier Exp $
|
||||
.\"
|
||||
.Dd January 8, 1995
|
||||
.Dt KEYBOARD 4 i386
|
||||
@ -78,7 +78,7 @@ represented by the map array, as shown below:
|
||||
---- ------------------------------------------------------
|
||||
0x1E 'a' 'A' 0x01 0x01 'a' 'A' 0x01 0x01
|
||||
|
||||
This is the default mapping for the key labelled 'A' wich normally has
|
||||
This is the default mapping for the key labelled 'A' which normally has
|
||||
scancode 0x1E. The eight states is as shown, giving the 'A' key its
|
||||
normal behavior.
|
||||
The spcl field is used to give the key "special" treatment, and is
|
||||
@ -113,7 +113,7 @@ The field keynum defines which function key that is programmed.
|
||||
The array keydef should contain the new string to be used (MAXFK long),
|
||||
and the length should be entered in flen.
|
||||
|
||||
The GETFKEY ioctl call works in a semilar manner, execpt it returns
|
||||
The GETFKEY ioctl call works in a similar manner, execpt it returns
|
||||
the current setting of keynum.
|
||||
|
||||
The function keys are numbered like this:
|
||||
|
@ -27,7 +27,7 @@
|
||||
.\" (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$
|
||||
.\" $Id: labpc.4,v 1.4 1997/03/07 02:49:48 jmg Exp $
|
||||
.\"
|
||||
.rm ES
|
||||
.rm EE
|
||||
@ -117,7 +117,7 @@ AD_NCHANS_GET) integers and sets the board gains. These are indices
|
||||
into the supported gain array, with one gain for each channel.
|
||||
.Pp
|
||||
AD_GAINS_GET takes an array of NCHANS (returned by AD_NCHANS_GET)
|
||||
integers and returns the cuurrent board gains.
|
||||
integers and returns the current board gains.
|
||||
.Sh BUGS
|
||||
In general, only those capabilities that I needed are present. In
|
||||
particular the following notable restrictions are present.
|
||||
|
@ -1,5 +1,5 @@
|
||||
.\"
|
||||
.\" $Id: meteor.4,v 1.5 1997/03/07 02:49:52 jmg Exp $
|
||||
.\" $Id: meteor.4,v 1.6 1997/03/21 20:13:50 mpp Exp $
|
||||
.\"
|
||||
.Dd August 15, 1995
|
||||
.br
|
||||
@ -516,7 +516,7 @@ external variable errno will be set to:
|
||||
invalid meteor_geomet structure pointer, rows, columns,
|
||||
frames were invalid.
|
||||
.It Dv ENOMEM
|
||||
could not allocate the contigous block.
|
||||
could not allocate the contiguous block.
|
||||
.El
|
||||
.in -0.5i
|
||||
.Pp
|
||||
|
@ -3,7 +3,7 @@
|
||||
.\" Copyright (c) 1997, Alex Zepeda.
|
||||
.\"
|
||||
.\" This documentation is public domain, and is provided without warranty.
|
||||
.\" Alex Zepeda, the "author" of this page is not resposible for any
|
||||
.\" Alex Zepeda, the "author" of this page is not responsible for any
|
||||
.\" consequences of any sort of manipulation of this document.
|
||||
.\"
|
||||
.\" SoundBlaster and any phrases including it's name are copyright
|
||||
@ -16,7 +16,7 @@
|
||||
.Os FreeBSD
|
||||
.Sh NAME
|
||||
.Nm sb
|
||||
.Nd Creative Labs Sound Blaster and compatable device driver
|
||||
.Nd Creative Labs Sound Blaster and compatible device driver
|
||||
.Sh SYNOPSIS
|
||||
For all sound cards supported with the sb driver this is needed:
|
||||
.Cd controller snd0
|
||||
@ -46,7 +46,7 @@ Pro Audio Spectrum. For Yamaha OPL-2/OPL-3 FM support:
|
||||
.Sh DESCRIPTION
|
||||
This driver covers the SoundBlaster family of cards including the
|
||||
SoundBlaster 1.0 to the SoundBlaster 16/SoundBlaster 32. The awe driver
|
||||
provides AWE32/64 functionality. This driver is provied in FreeBSD
|
||||
provides AWE32/64 functionality. This driver is provided in FreeBSD
|
||||
versions 2.0-current through 3.0-current. You can also configure more
|
||||
then one card on a single DMA using the conflicts keyword in your
|
||||
configuration file. This is useful for boards with more then one type of
|
||||
@ -68,7 +68,7 @@ drivers were written by
|
||||
.An Hannu Savolainen .
|
||||
The SoundBlaster 16 DSP code was written by
|
||||
.An J. Schuber Aq jsb@sth.ruhr-uni-bochum.de .
|
||||
Improvments to the OPL-3 drivers were made by
|
||||
Improvements to the OPL-3 drivers were made by
|
||||
.An Rob Hooft Aq hooft@chem.ruu.nl .
|
||||
.Sh HISTORY
|
||||
Sound Galaxy NX Pro support added by Hunyue Yau (Jan 6 1994). MV
|
||||
|
@ -1,5 +1,5 @@
|
||||
.\"
|
||||
.\" $Id: screen.4,v 1.8 1997/03/07 02:49:57 jmg Exp $
|
||||
.\" $Id: screen.4,v 1.9 1998/03/12 07:30:37 charnier Exp $
|
||||
.\"
|
||||
.Dd January 8, 1995
|
||||
.Dt SCREEN 4 i386
|
||||
@ -13,7 +13,7 @@ Access to the
|
||||
.Ar virtual consoles
|
||||
are obtained through the device files
|
||||
ttyv0 - ttyvb in /dev.
|
||||
Each of these files correspond to a seperate
|
||||
Each of these files correspond to a separate
|
||||
virtual console.
|
||||
All virtual console devices can be open at once, but only one is
|
||||
active at a time. The active virtual console "owns" the keyboard and
|
||||
@ -40,7 +40,7 @@ To use this facility press and hold down ALT,
|
||||
then enter a decimal number from 0-255 via the numerical keypad, then
|
||||
release ALT. The entered value is then used as the ASCII value for one
|
||||
character. This way it is possible to enter any ASCII value.
|
||||
The console driver also includes a history function. It is activatet by
|
||||
The console driver also includes a history function. It is activated by
|
||||
pressing the scroll-lock key. This holds the display, and enables the cursor
|
||||
arrows for scrolling up and down through the last scrolled out lines.
|
||||
|
||||
|
@ -7,7 +7,7 @@
|
||||
.\"modification, are permitted provided redistributions must retain
|
||||
.\"the above copyright notice and this condition.
|
||||
.\"
|
||||
.\" $Id$
|
||||
.\" $Id: sea.4,v 1.6 1997/02/22 13:25:40 peter Exp $
|
||||
.Dd December 25, 1994
|
||||
.Dt SEA 4 i386
|
||||
.Os FreeBSD
|
||||
@ -56,7 +56,7 @@ without BIOS: just unplug the ST02 BIOS chip from the board.
|
||||
.Pp
|
||||
Another problem is the floppy adapter on ST02 which could not be
|
||||
disabled by jumpers. The ST02 adapter it the best as a cheap solution
|
||||
for atttaching the tape and CD-ROM drives, and an extra floppy controller
|
||||
for attaching the tape and CD-ROM drives, and an extra floppy controller
|
||||
is just a headache. There exist a simple workaround: cutting off
|
||||
the AEN signal (A11 contact on ISA connector). AEN then goes high and
|
||||
disables the floppy adapter port address decoder.
|
||||
|
@ -1,4 +1,4 @@
|
||||
.\" $Id: si.4,v 1.11 1998/03/12 07:30:38 charnier Exp $
|
||||
.\" $Id: si.4,v 1.12 1998/03/23 20:24:31 peter Exp $
|
||||
.\" The following requests are required for all man pages.
|
||||
.Dd September 16, 1995
|
||||
.Os FreeBSD
|
||||
@ -55,7 +55,7 @@ The si device driver also responds to the
|
||||
.Xr comcontrol 8
|
||||
utility for configuring drain-on-close timeouts.
|
||||
.Pp
|
||||
The driver also devines 3 sysctl variables that can be manipulated:
|
||||
The driver also defines 3 sysctl variables that can be manipulated:
|
||||
machdep.si_debug sets the debug level for the whole driver. It depends
|
||||
on the driver being compiled with SI_DEBUG. machdep.si_pollrate
|
||||
sets how often per second the driver polls for lost interrupts.
|
||||
|
@ -34,7 +34,7 @@
|
||||
.\"
|
||||
.\" from: @(#)dca.4 5.2 (Berkeley) 3/27/91
|
||||
.\" from: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp
|
||||
.\" $Id: sio.4,v 1.25 1997/09/14 18:55:41 joerg Exp $
|
||||
.\" $Id: sio.4,v 1.26 1998/05/31 11:16:09 bde Exp $
|
||||
.\"
|
||||
.Dd October 10, 1995
|
||||
.Dt SIO 4 i386
|
||||
@ -123,7 +123,7 @@ that share an Interrupt Request (IRQ) line per group.
|
||||
Shared IRQs on different cards are not supported.
|
||||
Frequently 4 ports share 1 IRQ; some 8 port cards have 2 groups of 4 ports,
|
||||
thus using 2 IRQs.
|
||||
Some cards allow the first 2 serial ports to have seperate IRQs per port
|
||||
Some cards allow the first 2 serial ports to have separate IRQs per port
|
||||
(as per DOS PC standard).
|
||||
.Pp
|
||||
Some cards have an IRQ control register for each group.
|
||||
|
@ -28,7 +28,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: sr.4,v 1.7 1998/02/28 07:06:25 jhay Exp $
|
||||
.\" $Id: sr.4,v 1.8 1998/03/12 07:30:38 charnier Exp $
|
||||
.\"
|
||||
.Dd July 4, 1996
|
||||
.Dt SR 4 i386
|
||||
@ -36,7 +36,7 @@
|
||||
.Sh NAME
|
||||
.Nm sr
|
||||
.Nd synchronous RISCom/N2 / WANic 400/405 device driver.
|
||||
.Sh SYNOPSYS
|
||||
.Sh SYNOPSIS
|
||||
.Cd "device sr0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector srintr"
|
||||
.Cd "device sr1 at isa? port 0x310 net irq 11 flags 0x1 iomem 0xd0000 vector srintr"
|
||||
.Pp
|
||||
@ -76,9 +76,9 @@ behaviour than the default.
|
||||
.It Em 0x01
|
||||
The card has only one port.
|
||||
.It Em 0x10
|
||||
Use sepperate external clocks for transmit and receive on port 0.
|
||||
Use separate external clocks for transmit and receive on port 0.
|
||||
.It Em 0x40
|
||||
Use sepperate external clocks for transmit and receive on port 1.
|
||||
Use separate external clocks for transmit and receive on port 1.
|
||||
.El
|
||||
.Pp
|
||||
.Sh NUMBERING
|
||||
|
@ -69,7 +69,7 @@ The device stops responding. Device and driver reset follows this error.
|
||||
.It "tx%d: PCI fatal error occured (%s)"
|
||||
One of following errors occured: PCI Target Abort, PCI Master Abort, Data
|
||||
Parity Error or Address Parity Error. Device and driver reset follows this error.
|
||||
.It "tx%d: WARNING! no link estabilished"
|
||||
.It "tx%d: WARNING! no link established"
|
||||
No media connected. Displayed at startup only.
|
||||
.It "tx%d: cannot allocate mbuf header/cluster"
|
||||
Cannot allocate memory for received packet. Packet througth away.
|
||||
|
@ -24,7 +24,7 @@
|
||||
.\" (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: wd.4,v 1.7 1997/09/04 18:49:53 sos Exp $
|
||||
.\" $Id: wd.4,v 1.8 1998/04/09 22:31:47 sos Exp $
|
||||
.\"
|
||||
.Dd August 31, 1994
|
||||
.Dt WD 4 i386
|
||||
@ -59,7 +59,7 @@ For each drive there are four bit-fields encoded in a 16 bit integer:
|
||||
.It 0x8000
|
||||
Test and use the 32bit transfer capability of the drive.
|
||||
.It 0x4000
|
||||
If drive looks like it's comming out of sleep mode, assume it's
|
||||
If drive looks like it's coming out of sleep mode, assume it's
|
||||
confused and reinitialize it.
|
||||
.It 0x2000
|
||||
Probe for and use the bus-mastering DMA capabilities of modern
|
||||
|
@ -28,7 +28,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: wl.4,v 1.2 1997/08/01 03:32:39 msmith Exp $
|
||||
.\" $Id: wl.4,v 1.3 1998/03/12 07:30:40 charnier Exp $
|
||||
.Dd July 7, 1997
|
||||
.Dt WL 4 i386
|
||||
.Os FreeBSD
|
||||
@ -47,7 +47,7 @@ about 400 feet (indoors, more outdoors) can be covered in circumference.
|
||||
This card can talk to the companion (wlp0) pccard. Speeds vary
|
||||
from 1 megabit to theoretically 2 megabits (roughly T1 in speed).
|
||||
.Pp
|
||||
The card has 3 fundmental hardware
|
||||
The card has 3 fundamental hardware
|
||||
units, a so-called PSA or programmable storage area, a radio modem,
|
||||
and a ethernet lan controller. The latter component is the
|
||||
ancient (and not very honorable) Intel 82586 ethernet chip.
|
||||
|
@ -1,5 +1,5 @@
|
||||
.\"
|
||||
.\" $Id: screen.4,v 1.8 1997/03/07 02:49:57 jmg Exp $
|
||||
.\" $Id: screen.4,v 1.9 1998/03/12 07:30:37 charnier Exp $
|
||||
.\"
|
||||
.Dd January 8, 1995
|
||||
.Dt SCREEN 4 i386
|
||||
@ -13,7 +13,7 @@ Access to the
|
||||
.Ar virtual consoles
|
||||
are obtained through the device files
|
||||
ttyv0 - ttyvb in /dev.
|
||||
Each of these files correspond to a seperate
|
||||
Each of these files correspond to a separate
|
||||
virtual console.
|
||||
All virtual console devices can be open at once, but only one is
|
||||
active at a time. The active virtual console "owns" the keyboard and
|
||||
@ -40,7 +40,7 @@ To use this facility press and hold down ALT,
|
||||
then enter a decimal number from 0-255 via the numerical keypad, then
|
||||
release ALT. The entered value is then used as the ASCII value for one
|
||||
character. This way it is possible to enter any ASCII value.
|
||||
The console driver also includes a history function. It is activatet by
|
||||
The console driver also includes a history function. It is activated by
|
||||
pressing the scroll-lock key. This holds the display, and enables the cursor
|
||||
arrows for scrolling up and down through the last scrolled out lines.
|
||||
|
||||
|
@ -1,4 +1,4 @@
|
||||
.\" $Id: si.4,v 1.11 1998/03/12 07:30:38 charnier Exp $
|
||||
.\" $Id: si.4,v 1.12 1998/03/23 20:24:31 peter Exp $
|
||||
.\" The following requests are required for all man pages.
|
||||
.Dd September 16, 1995
|
||||
.Os FreeBSD
|
||||
@ -55,7 +55,7 @@ The si device driver also responds to the
|
||||
.Xr comcontrol 8
|
||||
utility for configuring drain-on-close timeouts.
|
||||
.Pp
|
||||
The driver also devines 3 sysctl variables that can be manipulated:
|
||||
The driver also defines 3 sysctl variables that can be manipulated:
|
||||
machdep.si_debug sets the debug level for the whole driver. It depends
|
||||
on the driver being compiled with SI_DEBUG. machdep.si_pollrate
|
||||
sets how often per second the driver polls for lost interrupts.
|
||||
|
@ -34,7 +34,7 @@
|
||||
.\"
|
||||
.\" from: @(#)dca.4 5.2 (Berkeley) 3/27/91
|
||||
.\" from: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp
|
||||
.\" $Id: sio.4,v 1.25 1997/09/14 18:55:41 joerg Exp $
|
||||
.\" $Id: sio.4,v 1.26 1998/05/31 11:16:09 bde Exp $
|
||||
.\"
|
||||
.Dd October 10, 1995
|
||||
.Dt SIO 4 i386
|
||||
@ -123,7 +123,7 @@ that share an Interrupt Request (IRQ) line per group.
|
||||
Shared IRQs on different cards are not supported.
|
||||
Frequently 4 ports share 1 IRQ; some 8 port cards have 2 groups of 4 ports,
|
||||
thus using 2 IRQs.
|
||||
Some cards allow the first 2 serial ports to have seperate IRQs per port
|
||||
Some cards allow the first 2 serial ports to have separate IRQs per port
|
||||
(as per DOS PC standard).
|
||||
.Pp
|
||||
Some cards have an IRQ control register for each group.
|
||||
|
@ -31,7 +31,7 @@
|
||||
.Sh DESCRIPTION
|
||||
The
|
||||
.Nm
|
||||
kernel impliments symmetric multiprocessor support.
|
||||
kernel implements symmetric multiprocessor support.
|
||||
|
||||
.Sh COMPATIBILITY
|
||||
The
|
||||
|
@ -23,14 +23,14 @@
|
||||
.\" (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: sppp.4,v 1.4 1998/02/28 21:00:55 phk Exp $
|
||||
.\" $Id: sppp.4,v 1.5 1998/03/12 07:30:18 charnier Exp $
|
||||
.\"
|
||||
.Dd May 19, 1997
|
||||
.Dt SPPP 4
|
||||
.Os
|
||||
.Sh NAME
|
||||
.Nm sppp
|
||||
.Nd point to point protocol network layer for synchronuous lines
|
||||
.Nd point to point protocol network layer for synchronous lines
|
||||
.Sh SYNOPSIS
|
||||
.Cd "pseudo-device sppp" Op Ar count
|
||||
.Sh DESCRIPTION
|
||||
|
@ -30,7 +30,7 @@
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" @(#)termios.4 8.4 (Berkeley) 4/19/94
|
||||
.\" $Id: termios.4,v 1.5 1997/03/14 05:01:14 mpp Exp $
|
||||
.\" $Id: termios.4,v 1.6 1997/03/18 07:17:22 mpp Exp $
|
||||
.\"
|
||||
.Dd April 19, 1994
|
||||
.Dt TERMIOS 4
|
||||
@ -646,7 +646,7 @@ of alphabetic/underscores or non alphabetic/underscores.
|
||||
As a special case in this second algorithm, the first previous
|
||||
non-whitespace character is skipped in determining
|
||||
whether the preceding word is a sequence of
|
||||
alphabetic/undercores. This sounds confusing but turns
|
||||
alphabetic/underscores. This sounds confusing but turns
|
||||
out to be quite practical.
|
||||
.It Dv REPRINT
|
||||
Special character on input and is recognized if the
|
||||
|
@ -69,7 +69,7 @@ The device stops responding. Device and driver reset follows this error.
|
||||
.It "tx%d: PCI fatal error occured (%s)"
|
||||
One of following errors occured: PCI Target Abort, PCI Master Abort, Data
|
||||
Parity Error or Address Parity Error. Device and driver reset follows this error.
|
||||
.It "tx%d: WARNING! no link estabilished"
|
||||
.It "tx%d: WARNING! no link established"
|
||||
No media connected. Displayed at startup only.
|
||||
.It "tx%d: cannot allocate mbuf header/cluster"
|
||||
Cannot allocate memory for received packet. Packet througth away.
|
||||
|
@ -32,7 +32,7 @@
|
||||
.\" USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
|
||||
.\" DAMAGE.
|
||||
.\"
|
||||
.\" $Id: worm.4,v 1.14 1998/03/12 07:30:19 charnier Exp $
|
||||
.\" $Id: worm.4,v 1.15 1998/03/31 01:55:11 jmz Exp $
|
||||
.\" "
|
||||
.Dd January 27, 1996
|
||||
.Dt WORM 4
|
||||
@ -401,12 +401,12 @@ have a lot of patience and CD-R's.
|
||||
The driver should include all the functionality of the
|
||||
.Xr cd 4
|
||||
driver. No strategy for implementing this kind of interaction has
|
||||
been designed yet, altough it's now finally possible to at least
|
||||
been designed yet, although it's now finally possible to at least
|
||||
read CD-ROM media through it.
|
||||
.Pp
|
||||
The first
|
||||
.Em Unit Attention
|
||||
conditition after a media change is often not yet caught, although
|
||||
condition after a media change is often not yet caught, although
|
||||
the driver was designed to catch it. This can royally screw a user
|
||||
of the driver, thus make sure to manually catch it before actually
|
||||
starting a burn. This can be done for example with a dummy
|
||||
|
Loading…
x
Reference in New Issue
Block a user