Remove single-space hard sentence breaks. These degrade the quality
of the typeset output, tend to make diffs harder to read and provide bad examples for new-comers to mdoc.
This commit is contained in:
parent
1b7dce690e
commit
88dd9b4faa
@ -80,7 +80,8 @@ This means that there are (216*4096) bytes available for use.
|
||||
.br
|
||||
.Em options BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_NTSC
|
||||
.br
|
||||
One of these options can be used to set the default video format for the driver. This fixed random hangs and lockups with the VideoLogic Captivator PCI card.
|
||||
One of these options can be used to set the default video format for the driver.
|
||||
This fixed random hangs and lockups with the VideoLogic Captivator PCI card.
|
||||
.br
|
||||
.Pp
|
||||
The following sysctls may be used to further configure the driver:
|
||||
@ -177,7 +178,8 @@ An FM Radio Tuner for cards which have an FM Radio tuner fitted. - requires that
|
||||
.Em The X Window System
|
||||
and
|
||||
.Em The Ports Collection
|
||||
also be installed. It also requires
|
||||
also be installed.
|
||||
It also requires
|
||||
.Em Motif
|
||||
or the
|
||||
.Em lesstif
|
||||
|
@ -16,7 +16,8 @@ the PC joystick.
|
||||
This device may be opened by only one process at a time.
|
||||
.Pp
|
||||
The joystick status is read from a structure via a read()
|
||||
call. The structure is defined in the header file as follows:
|
||||
call.
|
||||
The structure is defined in the header file as follows:
|
||||
.Pp
|
||||
.Bd -literal -offset indent
|
||||
struct joystick {
|
||||
@ -33,12 +34,14 @@ perl -e 'open(JOY,"/dev/joy0")||die;while(1)
|
||||
.br
|
||||
{sysread(JOY,$x,16);@j=unpack("iiii",$x);print "@j\\n";sleep(1);}'
|
||||
.Ss ioctl calls
|
||||
Several ioctl() calls are also available. They take an argument of
|
||||
Several ioctl() calls are also available.
|
||||
They take an argument of
|
||||
type int *
|
||||
.Bl -tag -width JOY_SET_X_OFFSET
|
||||
.It Dv JOY_SETTIMEOUT Fa int *limit
|
||||
Set the time limit (in microseconds) for reading the joystick
|
||||
status. Setting a value
|
||||
status.
|
||||
Setting a value
|
||||
too small may prevent to get correct values for the positions (which
|
||||
are then set to -2147483648), however this can be useful if one is
|
||||
only interested by the buttons status.
|
||||
|
@ -39,7 +39,8 @@ This driver provides access to the
|
||||
function is implemented.
|
||||
|
||||
The embedded SMBus controller of the Aladdin chipset may give you access
|
||||
to the monitoring facilities of your mainboard. See
|
||||
to the monitoring facilities of your mainboard.
|
||||
See
|
||||
.Xr smb 4
|
||||
for writing user code to fetch voltages, temperature and so on from the
|
||||
monitoring chip of your mainboard.
|
||||
|
@ -43,12 +43,15 @@ synchronous Digi/Arnet device driver.
|
||||
The
|
||||
.Nm ar
|
||||
driver supports the Digi/Arnet SYNC/570i ISA and PCI cards that is based on the
|
||||
HD64570 chip. Both the 2 and 4 port cards are supported and auto detected.
|
||||
HD64570 chip.
|
||||
Both the 2 and 4 port cards are supported and auto detected.
|
||||
.Pp
|
||||
The standard
|
||||
.Tn FreeBSD
|
||||
sppp code is used for the link level layer. The
|
||||
default protocol used is PPP. The Cisco HDLC protocol can be used by
|
||||
sppp code is used for the link level layer.
|
||||
The
|
||||
default protocol used is PPP.
|
||||
The Cisco HDLC protocol can be used by
|
||||
adding
|
||||
.Ar link2
|
||||
to
|
||||
@ -83,7 +86,8 @@ prepended, e.g.,
|
||||
.Sh DIAGNOSTICS
|
||||
.Bl -diag
|
||||
.It "ar%d: Warning illegal interrupt %d."
|
||||
The card cannot use the specified interrupt. Choose a different one.
|
||||
The card cannot use the specified interrupt.
|
||||
Choose a different one.
|
||||
.El
|
||||
.Sh FILES
|
||||
.Bl -tag -width /sys/i386/isa/ic/hd64570.h -compact
|
||||
@ -94,7 +98,8 @@ The card cannot use the specified interrupt. Choose a different one.
|
||||
.It Pa /sys/pci/if_ar_p.c
|
||||
.El
|
||||
.Sh BUGS
|
||||
At the moment only the V.35 and X.21 interfaces are tested. The others
|
||||
At the moment only the V.35 and X.21 interfaces are tested.
|
||||
The others
|
||||
may need tweaks to the clock selection code.
|
||||
.Pp
|
||||
The code can probably stand some optimizing.
|
||||
|
@ -48,7 +48,8 @@ It uses DMA and interrupts.
|
||||
Up to 50 lines of scanned input data are buffered in the driver.
|
||||
.Pp
|
||||
The device can operate at four different resolutions: 100, 200, 300
|
||||
and 400 dots per inch. It produces a simple bitmap with the most
|
||||
and 400 dots per inch.
|
||||
It produces a simple bitmap with the most
|
||||
significant bit at the left side. The driver can optionally output
|
||||
the simple portable bitmap file format
|
||||
.Xr pbm 5 ;
|
||||
@ -100,7 +101,8 @@ Get the current height of the bitmap.
|
||||
.It Dv ASC_SBLEN
|
||||
.Pq Li int
|
||||
Set the length of the buffer used internally to do the DMA transfer.
|
||||
The buffer length is supplied in lines of the bitmap. Since the buffer
|
||||
The buffer length is supplied in lines of the bitmap.
|
||||
Since the buffer
|
||||
size limit is (currently) 0x3000 bytes, the maximum number of lines
|
||||
allowed will vary with the width of each line. An
|
||||
.Er ENOMEM
|
||||
@ -110,7 +112,8 @@ error is returned if the requested length would exceed this limit.
|
||||
Get the current buffer length in lines.
|
||||
.It Dv ASC_SBTIME
|
||||
.Pq Li int
|
||||
Set the timeout for the completion of reading one buffer. Since a
|
||||
Set the timeout for the completion of reading one buffer.
|
||||
Since a
|
||||
handy scanner is a human/computer interface timeout values are usually
|
||||
higher than those of a flat scanner; the default is 15 seconds. After
|
||||
timeout is reached the read operation will fail with
|
||||
|
@ -80,7 +80,8 @@ This means that there are (216*4096) bytes available for use.
|
||||
.br
|
||||
.Em options BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_NTSC
|
||||
.br
|
||||
One of these options can be used to set the default video format for the driver. This fixed random hangs and lockups with the VideoLogic Captivator PCI card.
|
||||
One of these options can be used to set the default video format for the driver.
|
||||
This fixed random hangs and lockups with the VideoLogic Captivator PCI card.
|
||||
.br
|
||||
.Pp
|
||||
The following sysctls may be used to further configure the driver:
|
||||
@ -177,7 +178,8 @@ An FM Radio Tuner for cards which have an FM Radio tuner fitted. - requires that
|
||||
.Em The X Window System
|
||||
and
|
||||
.Em The Ports Collection
|
||||
also be installed. It also requires
|
||||
also be installed.
|
||||
It also requires
|
||||
.Em Motif
|
||||
or the
|
||||
.Em lesstif
|
||||
|
@ -77,7 +77,8 @@ The IRQ specified in the configuration entry is not valid for the adapter.
|
||||
.It "cs%d: Could not allocate memory for NIC"
|
||||
There is a critical memory shortage. The adapter will not function.
|
||||
.It "cs%d: Adapter has no media"
|
||||
The adapter is not configured for a specific media type. The media type will have
|
||||
The adapter is not configured for a specific media type.
|
||||
The media type will have
|
||||
to be manually set.
|
||||
.It "This is a %s, but LDN %d is disabled"
|
||||
The PnP probe code found a recognised adapter, but the adapter is disabled.
|
||||
|
@ -17,7 +17,8 @@ ethernet device driver
|
||||
The
|
||||
.Nm ie
|
||||
driver provides support for 8 and 16bit ISA ethernet cards that are based on
|
||||
the Intel i82586 chip. It supports the AT&T Starlan 10 and Starlan Fiber,
|
||||
the Intel i82586 chip.
|
||||
It supports the AT&T Starlan 10 and Starlan Fiber,
|
||||
the EN100, the Intel EtherExpress 16, the 3COM 3C507 and the RACAL Interlan
|
||||
NI5210.
|
||||
.Pp
|
||||
@ -40,16 +41,20 @@ interrupt than the one specified in the kernel configuration file.
|
||||
.It "ie%d: reset"
|
||||
The Intel i82586 had to be reset by the driver.
|
||||
.It "ie%d: transceiver problem"
|
||||
The driver has detected a problem with the ethernet transceiver. This is
|
||||
The driver has detected a problem with the ethernet transceiver.
|
||||
This is
|
||||
usually due to a loose or broken transceiver cable when using an external
|
||||
transceiver. When you experience this problem with an on-card transceiver
|
||||
transceiver.
|
||||
When you experience this problem with an on-card transceiver
|
||||
your card may be incorrectly jumpered for to use an external transceiver.
|
||||
Worst case your on-board transceiver may be broken.
|
||||
.It "ie%d: TDR detected an open %d clocks away"
|
||||
The driver detected an open circuit in the ethernet cable. Check your
|
||||
The driver detected an open circuit in the ethernet cable.
|
||||
Check your
|
||||
coax cable and terminator resistors.
|
||||
.It "ie%d: TDR detected a short %d clocks away"
|
||||
The driver detected a short circuit in the ethernet cable. Check your
|
||||
The driver detected a short circuit in the ethernet cable.
|
||||
Check your
|
||||
coax cable and terminator resistors.
|
||||
.It "ie%d: TDR returned unknown status %x"
|
||||
The driver got an unknown status from the card during the ethernet cable
|
||||
@ -63,7 +68,8 @@ The programming of the Ethernet (MAC) address failed.
|
||||
.El
|
||||
.Sh CAVEATS
|
||||
The Racal Interlan NI5210 comes in variants with 8 and 16 kbytes of
|
||||
shared memory. It is strongly advisable to use the 16 kbyte variant.
|
||||
shared memory.
|
||||
It is strongly advisable to use the 16 kbyte variant.
|
||||
You can upgrade your 8 kbyte card to 16 kbyte by adding an additional
|
||||
RAM chip.
|
||||
.Pp
|
||||
|
@ -16,7 +16,8 @@ the PC joystick.
|
||||
This device may be opened by only one process at a time.
|
||||
.Pp
|
||||
The joystick status is read from a structure via a read()
|
||||
call. The structure is defined in the header file as follows:
|
||||
call.
|
||||
The structure is defined in the header file as follows:
|
||||
.Pp
|
||||
.Bd -literal -offset indent
|
||||
struct joystick {
|
||||
@ -33,12 +34,14 @@ perl -e 'open(JOY,"/dev/joy0")||die;while(1)
|
||||
.br
|
||||
{sysread(JOY,$x,16);@j=unpack("iiii",$x);print "@j\\n";sleep(1);}'
|
||||
.Ss ioctl calls
|
||||
Several ioctl() calls are also available. They take an argument of
|
||||
Several ioctl() calls are also available.
|
||||
They take an argument of
|
||||
type int *
|
||||
.Bl -tag -width JOY_SET_X_OFFSET
|
||||
.It Dv JOY_SETTIMEOUT Fa int *limit
|
||||
Set the time limit (in microseconds) for reading the joystick
|
||||
status. Setting a value
|
||||
status.
|
||||
Setting a value
|
||||
too small may prevent to get correct values for the positions (which
|
||||
are then set to -2147483648), however this can be useful if one is
|
||||
only interested by the buttons status.
|
||||
|
@ -71,7 +71,8 @@ the lower 16Mb of physical memory. The
|
||||
.Nm
|
||||
driver assumes the memory it allocates is within the lower 16Mb range.
|
||||
This is not a very valid assumption but there's nothing that can be done
|
||||
about it yet. For shared memory NICs this isn't relevant.
|
||||
about it yet.
|
||||
For shared memory NICs this isn't relevant.
|
||||
.It "lnc%d: Device timeout -- Resetting"
|
||||
The device has stopped responding to the network, or there is a problem with
|
||||
the network connection (cable). Make sure the network connection in use
|
||||
|
@ -16,7 +16,8 @@ The
|
||||
.Nm meteor
|
||||
driver provides support for a PCI
|
||||
.Em video
|
||||
capture. It allows the capture of 24 bit RGB, 16 bit RGB and 16 bit YUV
|
||||
capture.
|
||||
It allows the capture of 24 bit RGB, 16 bit RGB and 16 bit YUV
|
||||
output formats.
|
||||
.Pp
|
||||
.Sh Meteor Driver Installation
|
||||
@ -66,7 +67,8 @@ probed. The default number of pages allocated by the kernel is 151.
|
||||
This means that there are (151*4096) bytes available for use.
|
||||
.Pp
|
||||
.Em options METEOR_DEALLOC_PAGES
|
||||
deallocate all pages when closing the device. Note, the chance of
|
||||
deallocate all pages when closing the device.
|
||||
Note, the chance of
|
||||
contiguously re-allocating new pages are very small. The default
|
||||
behavior is to not deallocate pages.
|
||||
.Pp
|
||||
@ -88,7 +90,8 @@ The Meteor capture driver has three modes of capture operation.
|
||||
1) Conventional read(2) interface.
|
||||
.in +0.5i
|
||||
.Pp
|
||||
This mode is the easiest and slowest to use. This mode is great for
|
||||
This mode is the easiest and slowest to use.
|
||||
This mode is great for
|
||||
capturing a single field at little programming cost.
|
||||
.Pp
|
||||
In this mode, the user opens the device, set the capture mode
|
||||
@ -175,7 +178,8 @@ main()
|
||||
.Pp
|
||||
The single capture mode is designed for conferencing tools such as nv.
|
||||
These tools need to control the starting of the image capture and also
|
||||
need several frames a second. The continuous capture mode is designed
|
||||
need several frames a second.
|
||||
The continuous capture mode is designed
|
||||
for applications that want free-running data.
|
||||
.Pp
|
||||
In this mode, the user opens the device, set the capture mode
|
||||
@ -266,15 +270,18 @@ main()
|
||||
.Pp
|
||||
.in +0.5i
|
||||
This continuous capture mode is synchronized with the application that
|
||||
processes up to 32 frames. This gives the advantages of both single and
|
||||
processes up to 32 frames.
|
||||
This gives the advantages of both single and
|
||||
continuous capture modes.
|
||||
.Pp
|
||||
The kernel notifies the application of a new data by raising an
|
||||
application defined signal. The driver also shares a structure with
|
||||
application defined signal.
|
||||
The driver also shares a structure with
|
||||
the application that allows them to communicate which frame has been
|
||||
written by the kernel and which frame has been read by the application.
|
||||
.Pp
|
||||
The shared structure starts on the first page after your data. The
|
||||
The shared structure starts on the first page after your data.
|
||||
The
|
||||
structure address can be found by calculation:
|
||||
.in +0.5i
|
||||
.Pp
|
||||
@ -287,25 +294,30 @@ structure address can be found by calculation:
|
||||
((number_rows * number_columns * pixel_depth + 4095)/4096) * 4096
|
||||
.in -0.5i
|
||||
.Pp
|
||||
The shared structure is of type struct meteor_mem. The two most
|
||||
The shared structure is of type struct meteor_mem.
|
||||
The two most
|
||||
important fields are called active and num_active_buf. active
|
||||
is a bitmap of frames written by the kernel. num_active_bufs is
|
||||
a count of frames marked in the active field. When a frame is read
|
||||
a count of frames marked in the active field.
|
||||
When a frame is read
|
||||
in by the driver, the num_active_bufs count is tested, if this
|
||||
count is below the threshold of number of active frames (value
|
||||
in meteor_mem's hiwat variable), the bit representing frame
|
||||
number in the buffer is stored in the active variable, the
|
||||
num_active_bufs is incremented, the kernel then raises the specified
|
||||
signal to activate the user application. The user application's
|
||||
signal to activate the user application.
|
||||
The user application's
|
||||
responsibility when getting the signal is to check the active bitmap
|
||||
to determine the lowest active frame, use the data as the application
|
||||
desires, clear the bitmap entry for that frame, and decrement the
|
||||
num_active_bufs. If the threshold of number of active frames (hiwat)
|
||||
num_active_bufs.
|
||||
If the threshold of number of active frames (hiwat)
|
||||
has been exceeded, no new frames or signal from the kernel will occur
|
||||
until the num_active_bufs is less than or equal to lowat.
|
||||
.Pp
|
||||
The driver loads the frames in a round-robin fashion. it is expected
|
||||
that the user removes them in the same order. The driver does not
|
||||
that the user removes them in the same order.
|
||||
The driver does not
|
||||
check to see if the frame is already active.
|
||||
.Pp
|
||||
The frame_size and number of frames in the buffer are also provided
|
||||
@ -314,7 +326,8 @@ application will not change the operation of the driver.
|
||||
.Pp
|
||||
In programming for this mode, the user opens the device, sets the
|
||||
geometry, mmaps the data/common control structure, then starts the
|
||||
continuous capture mode. A special signal catcher is required to
|
||||
continuous capture mode.
|
||||
A special signal catcher is required to
|
||||
process the frames as they are read by the kernel.
|
||||
.Pp
|
||||
When specifying the geometry (See: ioctl METEORSETGEO), it
|
||||
@ -451,7 +464,8 @@ attributes.
|
||||
.Pp
|
||||
IT IS VERY IMPORTANT TO CHECK FOR ERRORS ON THESE RETURNING IOCTLs.
|
||||
Errors indicate that something is very wrong with the ioctl and the
|
||||
application should not attempt to proceed further with capturing. The
|
||||
application should not attempt to proceed further with capturing.
|
||||
The
|
||||
meteor capture driver still makes attempts to stop the next capture step if
|
||||
an error occurred in a previous step but was ignored by the application
|
||||
programmer.
|
||||
@ -470,12 +484,14 @@ number of rows (lines high) in output image
|
||||
.It Dv columns
|
||||
number of pixels in a row (width) in output image
|
||||
.It Dv frames
|
||||
number of frames in buffer. Should be 1, unless using
|
||||
number of frames in buffer.
|
||||
Should be 1, unless using
|
||||
the multi-framed synchronous capture mode (METEORCAPFRM)
|
||||
which REQUIRES frames to be larger than 1.
|
||||
.Pp
|
||||
Note: if rows, columns or frames is not changed, then
|
||||
the existing values are used. The system defaults
|
||||
the existing values are used.
|
||||
The system defaults
|
||||
is 640x480x1.
|
||||
.It Dv oformat
|
||||
you may choose one of the following output format:
|
||||
@ -499,12 +515,14 @@ rows * column / 4 bytes of odd v)
|
||||
.El
|
||||
.Pp
|
||||
The METEORSETGEO ioctl will fail if more than one entry from a category
|
||||
is selected. It is highly recommended that a METEORSETGEO is done
|
||||
is selected.
|
||||
It is highly recommended that a METEORSETGEO is done
|
||||
before capturing data because you cannot guarantee the initial mode
|
||||
the card.
|
||||
.Pp
|
||||
The METEORSETGEO will also attempt to reallocate a new contiguous
|
||||
kernel buffer if the new geometry exceeds the old geometry. On
|
||||
kernel buffer if the new geometry exceeds the old geometry.
|
||||
On
|
||||
other hand, if the new geometry will fit in the existing buffer,
|
||||
the existing buffer is used.
|
||||
.Pp
|
||||
@ -543,7 +561,8 @@ Autodetect.
|
||||
.in +0.5i
|
||||
.Pp
|
||||
METEORSINPUT and METEORGINPUT are used to set and read the camera
|
||||
input device. Using the DB9 connector on the Meteor card, 4 input
|
||||
input device.
|
||||
Using the DB9 connector on the Meteor card, 4 input
|
||||
devices can be connected and an input camera can be selected with this
|
||||
ioctl.
|
||||
.Pp
|
||||
@ -667,7 +686,8 @@ variables in the structure as inputs
|
||||
.El
|
||||
.It Dv signal
|
||||
signal to send to application when a new
|
||||
frame has been captured. This signal will
|
||||
frame has been captured.
|
||||
This signal will
|
||||
only be raised if the captured frame is saved.
|
||||
.It Dv lowat
|
||||
see below
|
||||
@ -715,7 +735,8 @@ invalid unsigned char pointer.
|
||||
8) ioctl requests METEORGHUE and METEORSHUE
|
||||
.in +0.5i
|
||||
.Pp
|
||||
METEORGHUE and METEORSHUE are used to get and set the hue. The
|
||||
METEORGHUE and METEORSHUE are used to get and set the hue.
|
||||
The
|
||||
signed character has legal values are from +127 which represent
|
||||
+178.6 degrees to -128 which represents -180 degrees.
|
||||
.Pp
|
||||
@ -733,7 +754,8 @@ invalid signed char pointer.
|
||||
.Pp
|
||||
METEORGCOUNT is used to get the count of frame errors, DMA errors and
|
||||
count of the number of frames captured that have occurred since
|
||||
the device was opened. METEORSCOUNT can be used to reinitialize the
|
||||
the device was opened.
|
||||
METEORSCOUNT can be used to reinitialize the
|
||||
counters.
|
||||
.Pp
|
||||
This ioctl routines use the meteor_counts structure that has the
|
||||
@ -758,11 +780,13 @@ invalid meteor_counts structure pointer.
|
||||
.Sh Known Bugs:
|
||||
.in +0.5i
|
||||
.Pp
|
||||
1) IIC register is difficult to set. We got around that by adding a long
|
||||
1) IIC register is difficult to set.
|
||||
We got around that by adding a long
|
||||
wait at each IIC register write.
|
||||
.Pp
|
||||
2) We had difficulties getting the Meteor capture card to work on systems
|
||||
that used NCR chipset SCSI cards. It is possible that the Meteor and NCR SCSI
|
||||
that used NCR chipset SCSI cards.
|
||||
It is possible that the Meteor and NCR SCSI
|
||||
could work together using the newer TRITON motherboards.
|
||||
.in -0.5i
|
||||
.Pp
|
||||
|
@ -45,9 +45,12 @@ system.
|
||||
.Pp
|
||||
The PCF8584 is an integrated circuit designed in CMOS technology which serves
|
||||
as an interface between most standard parallel-bus
|
||||
microcontrollers/microprocessors and the serial I2C-bus. The PCF8584
|
||||
provides both master and slave functions. Communication with I2C-bus is
|
||||
carried out on a byte-wise basis using interrupt or polled handshake. It
|
||||
microcontrollers/microprocessors and the serial I2C-bus.
|
||||
The PCF8584
|
||||
provides both master and slave functions.
|
||||
Communication with I2C-bus is
|
||||
carried out on a byte-wise basis using interrupt or polled handshake.
|
||||
It
|
||||
controls all the I2C-bus specific sequences, protocol, arbitration and timing.
|
||||
The PCF8584 allows parallel-bus systems to communicate bidirectionally with
|
||||
the I2C-bus.
|
||||
|
@ -118,7 +118,8 @@ ppb->ppb_avm field contains the available modes of the chipset.
|
||||
.Xr ppbus 4 ,
|
||||
.Xr ppi 4
|
||||
.Sh BUGS
|
||||
The chipset detection process may corrupt your chipset configuration. You may
|
||||
The chipset detection process may corrupt your chipset configuration.
|
||||
You may
|
||||
disable chipset specific detection by using the above flags.
|
||||
.Sh HISTORY
|
||||
The
|
||||
|
@ -42,7 +42,8 @@ To add SG NX Pro mixer support:
|
||||
.Cd "options __SGNXPRO__"
|
||||
.Pp
|
||||
The OPL-2/3 is used in the SoundBlaster, SoundBlaster Pro, SB 16, and the
|
||||
Pro Audio Spectrum. For Yamaha OPL-2/OPL-3 FM support:
|
||||
Pro Audio Spectrum.
|
||||
For Yamaha OPL-2/OPL-3 FM support:
|
||||
.Cd "device opl0 at isa? port 0x388"
|
||||
.Sh DESCRIPTION
|
||||
This driver covers the SoundBlaster family of cards including the
|
||||
@ -59,7 +60,8 @@ the kernel thinks there is a conflict. This can be worked-around by
|
||||
using the "conflicts" keyword on the sb16's device line.
|
||||
.Pp
|
||||
Current version doesn't support mode changes without closing and reopening
|
||||
the device. Support for this feature may be implemented in a future
|
||||
the device.
|
||||
Support for this feature may be implemented in a future
|
||||
version of this driver.
|
||||
.Sh SEE ALSO
|
||||
.Xr cdcontrol 1 ,
|
||||
|
@ -22,12 +22,15 @@ Only one process may have this device open at any given time;
|
||||
.Xr open 2
|
||||
and
|
||||
.Xr close 2
|
||||
are used to lock and relinquish it. An attempt to open when
|
||||
are used to lock and relinquish it.
|
||||
An attempt to open when
|
||||
another process has the device locked will return -1 with an
|
||||
.Er EBUSY
|
||||
error
|
||||
indication. Writes to the device are interpreted as `play strings' in a
|
||||
simple ASCII melody notation. An
|
||||
indication.
|
||||
Writes to the device are interpreted as `play strings' in a
|
||||
simple ASCII melody notation.
|
||||
An
|
||||
.Xr ioctl 2
|
||||
request
|
||||
for tone generation at arbitrary
|
||||
@ -35,7 +38,8 @@ frequencies is also supported.
|
||||
.Pp
|
||||
Sound-generation does not monopolize the processor; in fact, the driver
|
||||
spends most of its time sleeping while the PC hardware is emitting
|
||||
tones. Other processes may emit beeps while the driver is running.
|
||||
tones.
|
||||
Other processes may emit beeps while the driver is running.
|
||||
.Pp
|
||||
Applications may call
|
||||
.Xr ioctl 2
|
||||
@ -70,7 +74,8 @@ Advanced BASIC 2.0. The
|
||||
and
|
||||
.Li X
|
||||
primitives of PLAY are not
|
||||
useful in a timesharing environment and are omitted. The `octave-tracking'
|
||||
useful in a timesharing environment and are omitted.
|
||||
The `octave-tracking'
|
||||
feature and the slur mark are new.
|
||||
.Pp
|
||||
There are 84 accessible notes numbered 1-84 in 7 octaves, each running from
|
||||
@ -79,7 +84,8 @@ with middle C. By default, the play function emits half-second notes with the
|
||||
last 1/16th second being `rest time'.
|
||||
.Pp
|
||||
Play strings are interpreted left to right as a series of play command groups;
|
||||
letter case is ignored. Play command groups are as follows:
|
||||
letter case is ignored.
|
||||
Play command groups are as follows:
|
||||
.Bl -tag -width CDEFGABxx
|
||||
.It Li CDEFGAB
|
||||
Letters A through G cause the corresponding note to be played in the
|
||||
@ -101,7 +107,8 @@ or
|
||||
to enable or disable octave-tracking (it is disabled by default).
|
||||
When octave-tracking is on, interpretation of a pair of letter notes
|
||||
will change octaves if necessary in order to make the smallest
|
||||
possible jump between notes. Thus ``olbc'' will be played as
|
||||
possible jump between notes.
|
||||
Thus ``olbc'' will be played as
|
||||
``olb>c'', and ``olcb'' as ``olc<b''. Octave locking is disabled for
|
||||
one letter note following >, < and O[0123456]. (The octave-locking
|
||||
feature is not supported in
|
||||
@ -120,7 +127,8 @@ May be followed by sustain dots.
|
||||
.It Ns Li L Sy n
|
||||
Sets the current time value for notes. The default is
|
||||
.Li L4 ,
|
||||
quarter or crotchet notes. The lowest possible value is 1; values up
|
||||
quarter or crotchet notes.
|
||||
The lowest possible value is 1; values up
|
||||
to 64 are accepted.
|
||||
.Li L1
|
||||
sets whole notes,
|
||||
@ -164,7 +172,8 @@ Set articulation.
|
||||
.Li MN
|
||||
.Ns No ( Li N
|
||||
for normal) is the default; the last 1/8th of
|
||||
the note's value is rest time. You can set
|
||||
the note's value is rest time.
|
||||
You can set
|
||||
.Li ML
|
||||
for legato (no rest space) or
|
||||
.Li MS
|
||||
@ -176,8 +185,10 @@ Notes (that is,
|
||||
or
|
||||
.Li N
|
||||
command character groups) may be followed by
|
||||
sustain dots. Each dot causes the note's value to be lengthened by one-half
|
||||
for each one. Thus, a note dotted once is held for 3/2 of its undotted value;
|
||||
sustain dots.
|
||||
Each dot causes the note's value to be lengthened by one-half
|
||||
for each one.
|
||||
Thus, a note dotted once is held for 3/2 of its undotted value;
|
||||
dotted twice, it is held 9/4, and three times would give 27/8.
|
||||
.Pp
|
||||
A note and its sustain dots may also be followed by a slur mark (underscore).
|
||||
@ -191,7 +202,8 @@ melody sections.
|
||||
.Sh BUGS
|
||||
Due to roundoff in the pitch tables and slop in the tone-generation and timer
|
||||
hardware (neither of which was designed for precision), neither pitch accuracy
|
||||
nor timings will be mathematically exact. There is no volume control.
|
||||
nor timings will be mathematically exact.
|
||||
There is no volume control.
|
||||
.Pp
|
||||
The action of two or more sustain dots does not reflect standard musical
|
||||
notation, in which each dot adds half the value of the previous dot
|
||||
|
@ -49,8 +49,10 @@ that is based on the HD64570 chip.
|
||||
.Pp
|
||||
The standard
|
||||
.Tn FreeBSD
|
||||
sppp code is used for the link level layer. The
|
||||
default protocol used is PPP. The Cisco HDLC protocol can be used by
|
||||
sppp code is used for the link level layer.
|
||||
The
|
||||
default protocol used is PPP.
|
||||
The Cisco HDLC protocol can be used by
|
||||
adding
|
||||
.Em link2
|
||||
to
|
||||
@ -62,7 +64,8 @@ Alternately, the driver can be compiled to support
|
||||
.Pp
|
||||
The
|
||||
.Em flags
|
||||
field is optional. If it isn't specified, the driver will
|
||||
field is optional.
|
||||
If it isn't specified, the driver will
|
||||
assume the following:
|
||||
.Pp
|
||||
.Bl -hang -offset indent
|
||||
@ -111,7 +114,8 @@ prepended, e.g.,
|
||||
.Sh DIAGNOSTICS
|
||||
.Bl -diag
|
||||
.It "sr%d: Warning illegal interrupt %d."
|
||||
The card cannot use the specified interrupt. Choose a different one.
|
||||
The card cannot use the specified interrupt.
|
||||
Choose a different one.
|
||||
.El
|
||||
.Sh FILES
|
||||
.Bl -tag -width /sys/i386/isa/ic/hd64570.h -compact
|
||||
@ -122,7 +126,8 @@ The card cannot use the specified interrupt. Choose a different one.
|
||||
.It Pa /sys/pci/if_sr_p.c
|
||||
.El
|
||||
.Sh BUGS
|
||||
At the moment only the X.21 interface is tested. The others
|
||||
At the moment only the X.21 interface is tested.
|
||||
The others
|
||||
may need tweaks to the clock selection code.
|
||||
.Pp
|
||||
The code can probably stand some optimizing.
|
||||
|
@ -93,17 +93,21 @@ PCI-SCSI controllers.
|
||||
.Pp
|
||||
Driver features include support for wide SCSI busses, fast10, fast20,
|
||||
fast40 and fast80-dt synchronous data transfers depending on controller
|
||||
capabilities. It also provides generic SCSI features as tagged command
|
||||
queuing and auto-request sense. This driver is configured by default
|
||||
capabilities.
|
||||
It also provides generic SCSI features as tagged command
|
||||
queuing and auto-request sense.
|
||||
This driver is configured by default
|
||||
for a maximum of 446 outstanding commands per bus, 8 LUNs per target
|
||||
and 64 tagged tasks per LUN. These numbers are not so limited by design,
|
||||
and 64 tagged tasks per LUN.
|
||||
These numbers are not so limited by design,
|
||||
as have been considered reasonable values for current SCSI technology.
|
||||
These values can be increased by changing appropriate
|
||||
constants in driver header files (not recommended).
|
||||
.Pp
|
||||
This driver requires the PCI-SCSI chip to implement LOAD/STORE SCRIPTS
|
||||
instructions and therefore it does not provide support for 53C810 revid < 16,
|
||||
53C825 revid < 16 and all 53C815 revisions. The generic
|
||||
53C825 revid < 16 and all 53C815 revisions.
|
||||
The generic
|
||||
.Nm ncr
|
||||
driver can be used to support these early chips.
|
||||
.Pp
|
||||
@ -116,7 +120,8 @@ drivers are configured, the
|
||||
driver takes precedence over the
|
||||
.Nm ncr
|
||||
driver for all chips that are supported by
|
||||
both drivers. As result, the
|
||||
both drivers.
|
||||
As result, the
|
||||
.Nm ncr
|
||||
driver does only attach the 53C8XX
|
||||
chips that donnot support LOAD/STORE (i.e.: 53C810, 53C815 and 53C825).
|
||||
@ -143,13 +148,16 @@ driver will only
|
||||
attach the 53C1010 Ultra-3 controllers.
|
||||
.Pp
|
||||
HVD/LVD capable controllers (895, 895A, 896, 897 and 1010) report
|
||||
the actual bus mode from the STEST4 chip IO registers. This feature
|
||||
the actual bus mode from the STEST4 chip IO registers.
|
||||
This feature
|
||||
allows to safely probe against bus mode and to set up the chip
|
||||
accordingly. By default the driver only supports HVD for these chips.
|
||||
accordingly.
|
||||
By default the driver only supports HVD for these chips.
|
||||
For other chips that can support HVD but not LVD, the driver has to probe
|
||||
implementation dependent registers (GPIO) in order to detect HVD bus mode.
|
||||
Only HVD implementations that conform with Symbios Logic recommendation can
|
||||
be detected by the driver. When the
|
||||
be detected by the driver.
|
||||
When the
|
||||
.Ar SYM_SETUP_SCSI_DIFF
|
||||
kernel is provided
|
||||
as value 1, the driver will also probe against HVD for 825a, 875, 876 and
|
||||
@ -158,21 +166,27 @@ as value 1, the driver will also probe against HVD for 825a, 875, 876 and
|
||||
When supplied as 0, the
|
||||
.Ar SYM_SETUP_PCI_PARITY
|
||||
kernel configuration option
|
||||
indicates the driver not to enable PCI parity checking. PCI parity
|
||||
indicates the driver not to enable PCI parity checking.
|
||||
PCI parity
|
||||
checking should not be an option for PCI-SCSI controllers, but some
|
||||
systems have been reported to fail using 53C8XX chips due to spurious or
|
||||
permanent PCI parity errors detected. This option is supplied for
|
||||
permanent PCI parity errors detected.
|
||||
This option is supplied for
|
||||
convenience but it is not recommended nor supported.
|
||||
.Pp
|
||||
This driver offers other options that are not currently exported to user.
|
||||
They are defined and documented in the sym_conf.h driver file. It is not
|
||||
recommended to change these options unless absolute need. Some of these
|
||||
They are defined and documented in the sym_conf.h driver file.
|
||||
It is not
|
||||
recommended to change these options unless absolute need.
|
||||
Some of these
|
||||
options are planned to be exported through SYSCTL or equivalent mechanism
|
||||
in a further driver release and therefore, no compatibility is guaranteed.
|
||||
.Pp
|
||||
At initialization, the driver tries to detect and read user settings from
|
||||
controller NVRAM. The Symbios/Logic NVRAM layout and the Tekram NVRAM
|
||||
layout are currently supported. If the reading of the NVRAM succeeds, the
|
||||
controller NVRAM.
|
||||
The Symbios/Logic NVRAM layout and the Tekram NVRAM
|
||||
layout are currently supported.
|
||||
If the reading of the NVRAM succeeds, the
|
||||
following settings are taken into account and reported to CAM:
|
||||
.Pp
|
||||
.Bl -column "SCSI parity checking " "Symbios " "Tekram"
|
||||
@ -196,7 +210,8 @@ Scan LUN Y N
|
||||
.El
|
||||
.Pp
|
||||
Devices that are configured as disabled for 'scan' in the NVRAM are not
|
||||
reported to CAM at system start-up. They can be discovered later using
|
||||
reported to CAM at system start-up.
|
||||
They can be discovered later using
|
||||
the
|
||||
.Nm camcontrol rescan
|
||||
command.
|
||||
|
@ -66,14 +66,18 @@ The old ``ifconfig tx0 linkN'' method of configuration is not supported.
|
||||
.Sh DIAGNOSTICS
|
||||
.Bl -diag
|
||||
.It "tx%d: device timeout %d packets"
|
||||
The device stops responding. Device and driver reset follows this error.
|
||||
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.
|
||||
Parity Error or Address Parity Error.
|
||||
Device and driver reset follows this error.
|
||||
.It "tx%d: WARNING! no link established"
|
||||
No media connected. Displayed at startup only.
|
||||
No media connected.
|
||||
Displayed at startup only.
|
||||
.It "tx%d: cannot allocate mbuf header/cluster"
|
||||
Cannot allocate memory for received packet. Packet thrown away.
|
||||
Cannot allocate memory for received packet.
|
||||
Packet thrown away.
|
||||
.It "tx%d: can't stop %s DMA"
|
||||
While reseting, driver failed to stop device correctly.
|
||||
.El
|
||||
|
@ -39,7 +39,8 @@ Generic WD100x/IDE disk controller driver
|
||||
.Cd "device wd1 at wdc0 drive 1" Op flags Ar flags
|
||||
.Sh DESCRIPTION
|
||||
This driver provides access to disks connected to controllers that emulate
|
||||
the Western Digital WD100x series. This range of controllers includes WD1003
|
||||
the Western Digital WD100x series.
|
||||
This range of controllers includes WD1003
|
||||
type ST412 controllers, WD1007 ESDI controllers and also the generic IDE
|
||||
controllers found on most motherboards.
|
||||
.Pp
|
||||
|
@ -49,7 +49,8 @@ In general the interfaces are similar to those described by
|
||||
.Pp
|
||||
As the IDE controllers are probed during boot, the
|
||||
.Em IDE
|
||||
buses are scanned for devices. Any devices found which answered as
|
||||
buses are scanned for devices.
|
||||
Any devices found which answered as
|
||||
.Sq Em Floppy
|
||||
and
|
||||
.Sq Em removable
|
||||
|
@ -111,7 +111,8 @@ sender MAC address.
|
||||
There are two sysctls that change how it filters packets. Both are on
|
||||
by default.
|
||||
.It machdep.wl_wlcache_mcastonly <0 | 1>
|
||||
By default this switch is on. It forces the cache to filter out
|
||||
By default this switch is on.
|
||||
It forces the cache to filter out
|
||||
unicast packets. Only broadcast or multicast packets are accepted.
|
||||
.It machdep.wl_wlcache_iponly <0 | 1>
|
||||
By default this switch is on. It forces the driver to discard non-IP
|
||||
|
@ -118,7 +118,8 @@ ppb->ppb_avm field contains the available modes of the chipset.
|
||||
.Xr ppbus 4 ,
|
||||
.Xr ppi 4
|
||||
.Sh BUGS
|
||||
The chipset detection process may corrupt your chipset configuration. You may
|
||||
The chipset detection process may corrupt your chipset configuration.
|
||||
You may
|
||||
disable chipset specific detection by using the above flags.
|
||||
.Sh HISTORY
|
||||
The
|
||||
|
@ -22,12 +22,15 @@ Only one process may have this device open at any given time;
|
||||
.Xr open 2
|
||||
and
|
||||
.Xr close 2
|
||||
are used to lock and relinquish it. An attempt to open when
|
||||
are used to lock and relinquish it.
|
||||
An attempt to open when
|
||||
another process has the device locked will return -1 with an
|
||||
.Er EBUSY
|
||||
error
|
||||
indication. Writes to the device are interpreted as `play strings' in a
|
||||
simple ASCII melody notation. An
|
||||
indication.
|
||||
Writes to the device are interpreted as `play strings' in a
|
||||
simple ASCII melody notation.
|
||||
An
|
||||
.Xr ioctl 2
|
||||
request
|
||||
for tone generation at arbitrary
|
||||
@ -35,7 +38,8 @@ frequencies is also supported.
|
||||
.Pp
|
||||
Sound-generation does not monopolize the processor; in fact, the driver
|
||||
spends most of its time sleeping while the PC hardware is emitting
|
||||
tones. Other processes may emit beeps while the driver is running.
|
||||
tones.
|
||||
Other processes may emit beeps while the driver is running.
|
||||
.Pp
|
||||
Applications may call
|
||||
.Xr ioctl 2
|
||||
@ -70,7 +74,8 @@ Advanced BASIC 2.0. The
|
||||
and
|
||||
.Li X
|
||||
primitives of PLAY are not
|
||||
useful in a timesharing environment and are omitted. The `octave-tracking'
|
||||
useful in a timesharing environment and are omitted.
|
||||
The `octave-tracking'
|
||||
feature and the slur mark are new.
|
||||
.Pp
|
||||
There are 84 accessible notes numbered 1-84 in 7 octaves, each running from
|
||||
@ -79,7 +84,8 @@ with middle C. By default, the play function emits half-second notes with the
|
||||
last 1/16th second being `rest time'.
|
||||
.Pp
|
||||
Play strings are interpreted left to right as a series of play command groups;
|
||||
letter case is ignored. Play command groups are as follows:
|
||||
letter case is ignored.
|
||||
Play command groups are as follows:
|
||||
.Bl -tag -width CDEFGABxx
|
||||
.It Li CDEFGAB
|
||||
Letters A through G cause the corresponding note to be played in the
|
||||
@ -101,7 +107,8 @@ or
|
||||
to enable or disable octave-tracking (it is disabled by default).
|
||||
When octave-tracking is on, interpretation of a pair of letter notes
|
||||
will change octaves if necessary in order to make the smallest
|
||||
possible jump between notes. Thus ``olbc'' will be played as
|
||||
possible jump between notes.
|
||||
Thus ``olbc'' will be played as
|
||||
``olb>c'', and ``olcb'' as ``olc<b''. Octave locking is disabled for
|
||||
one letter note following >, < and O[0123456]. (The octave-locking
|
||||
feature is not supported in
|
||||
@ -120,7 +127,8 @@ May be followed by sustain dots.
|
||||
.It Ns Li L Sy n
|
||||
Sets the current time value for notes. The default is
|
||||
.Li L4 ,
|
||||
quarter or crotchet notes. The lowest possible value is 1; values up
|
||||
quarter or crotchet notes.
|
||||
The lowest possible value is 1; values up
|
||||
to 64 are accepted.
|
||||
.Li L1
|
||||
sets whole notes,
|
||||
@ -164,7 +172,8 @@ Set articulation.
|
||||
.Li MN
|
||||
.Ns No ( Li N
|
||||
for normal) is the default; the last 1/8th of
|
||||
the note's value is rest time. You can set
|
||||
the note's value is rest time.
|
||||
You can set
|
||||
.Li ML
|
||||
for legato (no rest space) or
|
||||
.Li MS
|
||||
@ -176,8 +185,10 @@ Notes (that is,
|
||||
or
|
||||
.Li N
|
||||
command character groups) may be followed by
|
||||
sustain dots. Each dot causes the note's value to be lengthened by one-half
|
||||
for each one. Thus, a note dotted once is held for 3/2 of its undotted value;
|
||||
sustain dots.
|
||||
Each dot causes the note's value to be lengthened by one-half
|
||||
for each one.
|
||||
Thus, a note dotted once is held for 3/2 of its undotted value;
|
||||
dotted twice, it is held 9/4, and three times would give 27/8.
|
||||
.Pp
|
||||
A note and its sustain dots may also be followed by a slur mark (underscore).
|
||||
@ -191,7 +202,8 @@ melody sections.
|
||||
.Sh BUGS
|
||||
Due to roundoff in the pitch tables and slop in the tone-generation and timer
|
||||
hardware (neither of which was designed for precision), neither pitch accuracy
|
||||
nor timings will be mathematically exact. There is no volume control.
|
||||
nor timings will be mathematically exact.
|
||||
There is no volume control.
|
||||
.Pp
|
||||
The action of two or more sustain dots does not reflect standard musical
|
||||
notation, in which each dot adds half the value of the previous dot
|
||||
|
@ -93,17 +93,21 @@ PCI-SCSI controllers.
|
||||
.Pp
|
||||
Driver features include support for wide SCSI busses, fast10, fast20,
|
||||
fast40 and fast80-dt synchronous data transfers depending on controller
|
||||
capabilities. It also provides generic SCSI features as tagged command
|
||||
queuing and auto-request sense. This driver is configured by default
|
||||
capabilities.
|
||||
It also provides generic SCSI features as tagged command
|
||||
queuing and auto-request sense.
|
||||
This driver is configured by default
|
||||
for a maximum of 446 outstanding commands per bus, 8 LUNs per target
|
||||
and 64 tagged tasks per LUN. These numbers are not so limited by design,
|
||||
and 64 tagged tasks per LUN.
|
||||
These numbers are not so limited by design,
|
||||
as have been considered reasonable values for current SCSI technology.
|
||||
These values can be increased by changing appropriate
|
||||
constants in driver header files (not recommended).
|
||||
.Pp
|
||||
This driver requires the PCI-SCSI chip to implement LOAD/STORE SCRIPTS
|
||||
instructions and therefore it does not provide support for 53C810 revid < 16,
|
||||
53C825 revid < 16 and all 53C815 revisions. The generic
|
||||
53C825 revid < 16 and all 53C815 revisions.
|
||||
The generic
|
||||
.Nm ncr
|
||||
driver can be used to support these early chips.
|
||||
.Pp
|
||||
@ -116,7 +120,8 @@ drivers are configured, the
|
||||
driver takes precedence over the
|
||||
.Nm ncr
|
||||
driver for all chips that are supported by
|
||||
both drivers. As result, the
|
||||
both drivers.
|
||||
As result, the
|
||||
.Nm ncr
|
||||
driver does only attach the 53C8XX
|
||||
chips that donnot support LOAD/STORE (i.e.: 53C810, 53C815 and 53C825).
|
||||
@ -143,13 +148,16 @@ driver will only
|
||||
attach the 53C1010 Ultra-3 controllers.
|
||||
.Pp
|
||||
HVD/LVD capable controllers (895, 895A, 896, 897 and 1010) report
|
||||
the actual bus mode from the STEST4 chip IO registers. This feature
|
||||
the actual bus mode from the STEST4 chip IO registers.
|
||||
This feature
|
||||
allows to safely probe against bus mode and to set up the chip
|
||||
accordingly. By default the driver only supports HVD for these chips.
|
||||
accordingly.
|
||||
By default the driver only supports HVD for these chips.
|
||||
For other chips that can support HVD but not LVD, the driver has to probe
|
||||
implementation dependent registers (GPIO) in order to detect HVD bus mode.
|
||||
Only HVD implementations that conform with Symbios Logic recommendation can
|
||||
be detected by the driver. When the
|
||||
be detected by the driver.
|
||||
When the
|
||||
.Ar SYM_SETUP_SCSI_DIFF
|
||||
kernel is provided
|
||||
as value 1, the driver will also probe against HVD for 825a, 875, 876 and
|
||||
@ -158,21 +166,27 @@ as value 1, the driver will also probe against HVD for 825a, 875, 876 and
|
||||
When supplied as 0, the
|
||||
.Ar SYM_SETUP_PCI_PARITY
|
||||
kernel configuration option
|
||||
indicates the driver not to enable PCI parity checking. PCI parity
|
||||
indicates the driver not to enable PCI parity checking.
|
||||
PCI parity
|
||||
checking should not be an option for PCI-SCSI controllers, but some
|
||||
systems have been reported to fail using 53C8XX chips due to spurious or
|
||||
permanent PCI parity errors detected. This option is supplied for
|
||||
permanent PCI parity errors detected.
|
||||
This option is supplied for
|
||||
convenience but it is not recommended nor supported.
|
||||
.Pp
|
||||
This driver offers other options that are not currently exported to user.
|
||||
They are defined and documented in the sym_conf.h driver file. It is not
|
||||
recommended to change these options unless absolute need. Some of these
|
||||
They are defined and documented in the sym_conf.h driver file.
|
||||
It is not
|
||||
recommended to change these options unless absolute need.
|
||||
Some of these
|
||||
options are planned to be exported through SYSCTL or equivalent mechanism
|
||||
in a further driver release and therefore, no compatibility is guaranteed.
|
||||
.Pp
|
||||
At initialization, the driver tries to detect and read user settings from
|
||||
controller NVRAM. The Symbios/Logic NVRAM layout and the Tekram NVRAM
|
||||
layout are currently supported. If the reading of the NVRAM succeeds, the
|
||||
controller NVRAM.
|
||||
The Symbios/Logic NVRAM layout and the Tekram NVRAM
|
||||
layout are currently supported.
|
||||
If the reading of the NVRAM succeeds, the
|
||||
following settings are taken into account and reported to CAM:
|
||||
.Pp
|
||||
.Bl -column "SCSI parity checking " "Symbios " "Tekram"
|
||||
@ -196,7 +210,8 @@ Scan LUN Y N
|
||||
.El
|
||||
.Pp
|
||||
Devices that are configured as disabled for 'scan' in the NVRAM are not
|
||||
reported to CAM at system start-up. They can be discovered later using
|
||||
reported to CAM at system start-up.
|
||||
They can be discovered later using
|
||||
the
|
||||
.Nm camcontrol rescan
|
||||
command.
|
||||
|
@ -66,14 +66,18 @@ The old ``ifconfig tx0 linkN'' method of configuration is not supported.
|
||||
.Sh DIAGNOSTICS
|
||||
.Bl -diag
|
||||
.It "tx%d: device timeout %d packets"
|
||||
The device stops responding. Device and driver reset follows this error.
|
||||
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.
|
||||
Parity Error or Address Parity Error.
|
||||
Device and driver reset follows this error.
|
||||
.It "tx%d: WARNING! no link established"
|
||||
No media connected. Displayed at startup only.
|
||||
No media connected.
|
||||
Displayed at startup only.
|
||||
.It "tx%d: cannot allocate mbuf header/cluster"
|
||||
Cannot allocate memory for received packet. Packet thrown away.
|
||||
Cannot allocate memory for received packet.
|
||||
Packet thrown away.
|
||||
.It "tx%d: can't stop %s DMA"
|
||||
While reseting, driver failed to stop device correctly.
|
||||
.El
|
||||
|
@ -45,16 +45,20 @@ The
|
||||
.Nm
|
||||
driver provides support for PCI ethernet adapters and embedded
|
||||
controllers based on the Winbond W89C840F fast ethernet controller
|
||||
chip. This includes the Trendware TE100-PCIE and various other cheap
|
||||
boards. The 840F should not be confused with the 940F, which is
|
||||
chip.
|
||||
This includes the Trendware TE100-PCIE and various other cheap
|
||||
boards.
|
||||
The 840F should not be confused with the 940F, which is
|
||||
an NE2000 clone and only supports 10Mbps speeds.
|
||||
.Pp
|
||||
The Winbond controller uses bus master DMA and is designed to be
|
||||
a DEC 'tulip' workalike. It differs from the standard DEC design
|
||||
a DEC 'tulip' workalike.
|
||||
It differs from the standard DEC design
|
||||
in several ways: the control and status registers are spaced 4
|
||||
bytes apart instead of 8, and the receive filter is programmed through
|
||||
registers rather than by downloading a special setup frame via
|
||||
the transmit DMA engine. Using an external PHY, the Winbond chip
|
||||
the transmit DMA engine.
|
||||
Using an external PHY, the Winbond chip
|
||||
supports both 10 and 100Mbps speeds in either full or half duplex.
|
||||
.Pp
|
||||
The
|
||||
@ -63,21 +67,25 @@ driver supports the following media types:
|
||||
.Pp
|
||||
.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
|
||||
.It autoselect
|
||||
Enable autoselection of the media type and options. This is only
|
||||
Enable autoselection of the media type and options.
|
||||
This is only
|
||||
supported if the PHY chip attached to the Winbond controller
|
||||
supports NWAY autonegotiation. The user can manually override
|
||||
supports NWAY autonegotiation.
|
||||
The user can manually override
|
||||
the autoselected mode by adding media options to the
|
||||
.Pa /etc/rc.conf
|
||||
file.
|
||||
.It 10baseT/UTP
|
||||
Set 10Mbps operation. The
|
||||
Set 10Mbps operation.
|
||||
The
|
||||
.Ar mediaopt
|
||||
option can also be used to select either
|
||||
.Ar full-duplex
|
||||
or
|
||||
.Ar half-duplex modes.
|
||||
.It 100baseTX
|
||||
Set 100Mbps (fast ethernet) operation. The
|
||||
Set 100Mbps (fast ethernet) operation.
|
||||
The
|
||||
.Ar mediaopt
|
||||
option can also be used to select either
|
||||
.Ar full-duplex
|
||||
@ -117,20 +125,25 @@ The driver failed to allocate an mbuf for the transmitter ring when
|
||||
allocating a pad buffer or collapsing an mbuf chain into a cluster.
|
||||
.It "wb%d: chip is in D3 power state -- setting to D0"
|
||||
This message applies only to adapters which support power
|
||||
management. Some operating systems place the controller in low power
|
||||
management.
|
||||
Some operating systems place the controller in low power
|
||||
mode when shutting down, and some PCI BIOSes fail to bring the chip
|
||||
out of this state before configuring it. The controller loses all of
|
||||
out of this state before configuring it.
|
||||
The controller loses all of
|
||||
its PCI configuration in the D3 state, so if the BIOS does not set
|
||||
it back to full power mode in time, it won't be able to configure it
|
||||
correctly. The driver tries to detect this condition and bring
|
||||
correctly.
|
||||
The driver tries to detect this condition and bring
|
||||
the adapter back to the D0 (full power) state, but this may not be
|
||||
enough to return the driver to a fully operational condition. If
|
||||
enough to return the driver to a fully operational condition.
|
||||
If
|
||||
you see this message at boot time and the driver fails to attach
|
||||
the device as a network interface, you will have to perform second
|
||||
warm boot to have the device properly configured.
|
||||
.Pp
|
||||
Note that this condition only occurs when warm booting from another
|
||||
operating system. If you power down your system prior to booting
|
||||
operating system.
|
||||
If you power down your system prior to booting
|
||||
.Fx ,
|
||||
the card should be configured correctly.
|
||||
.El
|
||||
@ -151,11 +164,14 @@ driver was written by
|
||||
.An Bill Paul Aq wpaul@ctr.columbia.edu .
|
||||
.Sh BUGS
|
||||
The Winbond chip seems to behave strangely in some cases when the
|
||||
link partner switches modes. If for example both sides are set to
|
||||
link partner switches modes.
|
||||
If for example both sides are set to
|
||||
10Mbps half-duplex, and the other end is changed to 100Mbps
|
||||
full-duplex, the Winbond's receiver suddenly starts writing trash
|
||||
all over the RX descriptors. The
|
||||
all over the RX descriptors.
|
||||
The
|
||||
.Nm
|
||||
driver handles this by forcing a reset of both the controller
|
||||
chip and attached PHY. This is drastic, but it appears to be the
|
||||
chip and attached PHY.
|
||||
This is drastic, but it appears to be the
|
||||
only way to recover properly from this condition.
|
||||
|
@ -64,12 +64,14 @@ driver is based around the concept of a
|
||||
which is defined as the period between the time that a tape is
|
||||
mounted, and the time when it is unmounted. Any parameters set during
|
||||
a mount session remain in effect for the remainder of the session or
|
||||
until replaced. The tape can be unmounted, bringing the session to a
|
||||
until replaced.
|
||||
The tape can be unmounted, bringing the session to a
|
||||
close in several ways. These include:
|
||||
.Bl -enum
|
||||
.It
|
||||
Closing an `unmount device',
|
||||
referred to as sub-mode 00 below. An example is
|
||||
referred to as sub-mode 00 below.
|
||||
An example is
|
||||
.Pa /dev/rwst0 .
|
||||
.It
|
||||
Using the MTOFFL
|
||||
@ -103,7 +105,8 @@ is the mode number.
|
||||
.Sh MODES AND SUB-MODES
|
||||
There are four
|
||||
.Sq operation
|
||||
modes. These are controlled by bits 2 and 3 of the minor number and
|
||||
modes.
|
||||
These are controlled by bits 2 and 3 of the minor number and
|
||||
are designed to allow users to easily read and write different formats
|
||||
of tape on devices that allow multiple formats. The parameters for
|
||||
each mode can be set individually by hand with the
|
||||
@ -132,7 +135,8 @@ No other head positioning takes place.
|
||||
Any further reads or writes will occur directly after the
|
||||
last read, or the written file mark.
|
||||
.It 10
|
||||
A close will rewind the device. If the tape has been
|
||||
A close will rewind the device.
|
||||
If the tape has been
|
||||
written, then a file mark will be written before the rewind is requested.
|
||||
On completion of the rewind an unload command will be issued.
|
||||
The device is unmounted.
|
||||
@ -167,7 +171,8 @@ written to the tape. One can never read or write
|
||||
.Em part
|
||||
of a record from tape (though you may request a larger block and read
|
||||
a smaller record); nor can one read multiple blocks. Data from a
|
||||
single write is therefore read by a single read. The block size used
|
||||
single write is therefore read by a single read.
|
||||
The block size used
|
||||
may be any value supported by the device, the
|
||||
.Tn IDE
|
||||
controller and the system (usually between 1 byte and 64 Kbytes,
|
||||
@ -175,13 +180,15 @@ sometimes more).
|
||||
.Pp
|
||||
When reading a variable record/block from the tape, the head is
|
||||
logically considered to be immediately after the last item read,
|
||||
and before the next item after that. If the next item is a file mark,
|
||||
and before the next item after that.
|
||||
If the next item is a file mark,
|
||||
but it was never read, then the next
|
||||
process to read will immediately hit the file mark and receive an end-of-file notification.
|
||||
.It Fixed block-size
|
||||
Data written by the user is passed to the tape as a succession of
|
||||
fixed size blocks. It may be contiguous in memory, but it is
|
||||
considered to be a series of independent blocks. One may never write
|
||||
considered to be a series of independent blocks.
|
||||
One may never write
|
||||
an amount of data that is not an exact multiple of the blocksize. One
|
||||
may read and write the same data as a different set of records, In
|
||||
other words, blocks that were written together may be read separately,
|
||||
@ -194,7 +201,8 @@ returning that data. The next read will return immediately with an
|
||||
EOF. (As above, if the file mark is never read, it remains for the next process to read if in no-rewind mode.)
|
||||
.El
|
||||
.Sh FILE MARK HANDLING
|
||||
The handling of file marks on write is automatic. If the user has
|
||||
The handling of file marks on write is automatic.
|
||||
If the user has
|
||||
written to the tape, and has not done a read since the last write,
|
||||
then a file mark will be written to the tape when the device is
|
||||
closed. If a rewind is requested after a write, then the driver
|
||||
|
@ -116,7 +116,8 @@ returns a few flags:
|
||||
.It Dv EX_DYNAMIC
|
||||
indicates that the executable requires the services of the run-time link editor.
|
||||
.It Dv EX_PIC
|
||||
indicates that the object contains position independent code. This flag is
|
||||
indicates that the object contains position independent code.
|
||||
This flag is
|
||||
set by
|
||||
.Xr as 1
|
||||
when given the
|
||||
@ -280,7 +281,8 @@ If set, the symbol, as identified by the
|
||||
field, is to be relocated to an offset into the Procedure Linkage Table.
|
||||
.It Fa r_relative
|
||||
If set, this relocation is relative to the (run-time) load address of the
|
||||
image this object file is going to be a part of. This type of relocation
|
||||
image this object file is going to be a part of.
|
||||
This type of relocation
|
||||
only occurs in shared objects.
|
||||
.It Fa r_copy
|
||||
If set, this relocation record identifies a symbol whose contents should
|
||||
@ -392,7 +394,8 @@ the values are described in
|
||||
This field provides information on the nature of the symbol independent of
|
||||
the symbol's location in terms of segments as determined by the
|
||||
.Fa n_type
|
||||
field. Currently, the lower 4 bits of the
|
||||
field.
|
||||
Currently, the lower 4 bits of the
|
||||
.Fa n_other
|
||||
field hold one of two values:
|
||||
.Dv AUX_FUNC
|
||||
|
@ -45,7 +45,8 @@
|
||||
The kernel maintains the following
|
||||
.Fa acct
|
||||
information structure for all
|
||||
processes. If a process terminates, and accounting is enabled,
|
||||
processes.
|
||||
If a process terminates, and accounting is enabled,
|
||||
the kernel calls the
|
||||
.Xr acct 2
|
||||
function call to prepare and append the record
|
||||
|
@ -40,7 +40,8 @@
|
||||
The
|
||||
.Nm ethers
|
||||
database contains information regarding known 48-bit ethernet addresses
|
||||
of hosts on an Internetwork. The data is stored in a file called
|
||||
of hosts on an Internetwork.
|
||||
The data is stored in a file called
|
||||
.Pa /etc/ethers
|
||||
in the following format:
|
||||
.Bd -unfilled -offset indent
|
||||
@ -48,8 +49,10 @@ in the following format:
|
||||
.Ed
|
||||
.Pp
|
||||
Items are separated by any number of blanks and/or
|
||||
tab characters. A ``#'' at the start of a line indicates the
|
||||
beginning of a comment that extends to the end of the line. A ``+'' at
|
||||
tab characters.
|
||||
A ``#'' at the start of a line indicates the
|
||||
beginning of a comment that extends to the end of the line.
|
||||
A ``+'' at
|
||||
the start of a line will cause the
|
||||
.Xr ethers 3
|
||||
library functions to use data stored in the
|
||||
@ -65,8 +68,10 @@ An ethernet address is expressed in
|
||||
.Tn ASCII
|
||||
form as "x:x:x:x:x:x" where
|
||||
.Ar x
|
||||
is a hexadecimal value between 0x00 and 0xFF. The address values
|
||||
should be in network order. Hostnames specified in the
|
||||
is a hexadecimal value between 0x00 and 0xFF.
|
||||
The address values
|
||||
should be in network order.
|
||||
Hostnames specified in the
|
||||
.Pa /etc/ethers
|
||||
database should correspond to entries in the
|
||||
.Xr hosts 5
|
||||
|
@ -236,7 +236,8 @@ assumption, so we are stuck with it).
|
||||
The
|
||||
.Fa fs_minfree
|
||||
element gives the minimum acceptable percentage of file system
|
||||
blocks that may be free. If the freelist drops below this level
|
||||
blocks that may be free.
|
||||
If the freelist drops below this level
|
||||
only the super-user may continue to allocate blocks.
|
||||
The
|
||||
.Fa fs_minfree
|
||||
@ -268,7 +269,8 @@ the file system defaults to optimizing for time.
|
||||
.Em Cylinder group related limits :
|
||||
Each cylinder keeps track of the availability of blocks at different
|
||||
rotational positions, so that sequential blocks can be laid out
|
||||
with minimum rotational latency. With the default of 8 distinguished
|
||||
with minimum rotational latency.
|
||||
With the default of 8 distinguished
|
||||
rotational positions, the resolution of the
|
||||
summary information is 2ms for a typical 3600 rpm drive.
|
||||
.Pp
|
||||
@ -338,7 +340,8 @@ is limited by the fact that the super-block is of size
|
||||
The size of these tables is
|
||||
.Em inversely
|
||||
proportional to the block
|
||||
size of the file system. The size of the tables is
|
||||
size of the file system.
|
||||
The size of the tables is
|
||||
increased when sector sizes are not powers of two,
|
||||
as this increases the number of cylinders
|
||||
included before the rotational pattern repeats
|
||||
|
@ -45,7 +45,8 @@ consists of newline separated
|
||||
.Tn ASCII
|
||||
records, one per group, containing four colon
|
||||
.Ql \&:
|
||||
separated fields. These fields are as follows:
|
||||
separated fields.
|
||||
These fields are as follows:
|
||||
.Bl -tag -width password -offset indent -compact
|
||||
.It group
|
||||
Name of the group.
|
||||
@ -60,7 +61,8 @@ Group members.
|
||||
.El
|
||||
.Pp
|
||||
Lines whose first non-whitespace character is a pound-sign (#)
|
||||
are comments, and are ignored. Blank lines that consist
|
||||
are comments, and are ignored.
|
||||
Blank lines that consist
|
||||
only of spaces, tabs or newlines are also ignored.
|
||||
.Pp
|
||||
The
|
||||
@ -133,9 +135,11 @@ the function where they occur; see section
|
||||
.Sx SEE ALSO .
|
||||
|
||||
In older implementations,
|
||||
a group cannot have more than 200 members. The maximum line length of
|
||||
a group cannot have more than 200 members.
|
||||
The maximum line length of
|
||||
.Pa /etc/group
|
||||
is 1024 characters. Longer lines will be skipped.
|
||||
is 1024 characters.
|
||||
Longer lines will be skipped.
|
||||
This limitation disappeared in
|
||||
.Fx 3.0 .
|
||||
Older binaries that are statically linked, depend on old
|
||||
|
@ -60,12 +60,14 @@ or the more verbose
|
||||
.Pp
|
||||
A
|
||||
.Dq @
|
||||
indicates a host by netgroup or user by netgroup. A single
|
||||
indicates a host by netgroup or user by netgroup.
|
||||
A single
|
||||
.Dq +
|
||||
matches all hosts or users. A host name with a leading
|
||||
.Dq -
|
||||
will reject
|
||||
all matching hosts and all their users. A user name with leading
|
||||
all matching hosts and all their users.
|
||||
A user name with leading
|
||||
.Dq -
|
||||
will reject all matching users from matching hosts.
|
||||
.Pp
|
||||
@ -137,7 +139,8 @@ file resides in
|
||||
.Xr ifconfig 8 ,
|
||||
.Xr named 8
|
||||
.Sh BUGS
|
||||
This man page is incomplete. For more information read
|
||||
This man page is incomplete.
|
||||
For more information read
|
||||
the source in
|
||||
.Pa src/lib/libc/net/rcmd.c
|
||||
or the SunOS man page.
|
||||
|
@ -118,7 +118,8 @@ defined in
|
||||
can only be written when the process is stopped.
|
||||
.It Pa rlimit
|
||||
This is a read-only file containing the process current and maximum
|
||||
limits. Each line is of the format
|
||||
limits.
|
||||
Each line is of the format
|
||||
.Ar rlimit current max
|
||||
, with -1
|
||||
indicating infinity.
|
||||
|
@ -53,14 +53,17 @@ The
|
||||
.Pa /etc/rc.conf
|
||||
file is included from the file
|
||||
.Pa /etc/defaults/rc.conf ,
|
||||
which specifies the default settings for all the available options. Options
|
||||
which specifies the default settings for all the available options.
|
||||
Options
|
||||
need only be specified in
|
||||
.Pa /etc/rc.conf
|
||||
when the system administrator wishes to override these defaults. The file
|
||||
when the system administrator wishes to override these defaults.
|
||||
The file
|
||||
.Pa /etc/rc.conf.local
|
||||
is used to override settings in
|
||||
.Pa /etc/rc.conf
|
||||
for historical reasons. See the
|
||||
for historical reasons.
|
||||
See the
|
||||
.Dq rc_conf_files
|
||||
option below.
|
||||
.Pp
|
||||
@ -202,7 +205,8 @@ as an argument.
|
||||
.It Ar tcp_extensions
|
||||
(bool) Set to
|
||||
.Ar NO
|
||||
by default. Setting this to YES enables certain TCP options as described by
|
||||
by default.
|
||||
Setting this to YES enables certain TCP options as described by
|
||||
.Rs
|
||||
.%T RFC 1323
|
||||
.Re
|
||||
@ -229,8 +233,10 @@ peer is still up and reachable.
|
||||
.Ar NO
|
||||
by default.
|
||||
Setting to YES will cause the kernel to ignore TCP frames that have both
|
||||
the SYN and FIN flags set. This prevents OS fingerprinting, but may
|
||||
break some legitimate applications. This option is only available if the
|
||||
the SYN and FIN flags set.
|
||||
This prevents OS fingerprinting, but may
|
||||
break some legitimate applications.
|
||||
This option is only available if the
|
||||
kernel was built with the TCP_DROP_SYNFIN option.
|
||||
.It Ar tcp_restrict_rst
|
||||
(bool) Set to
|
||||
@ -249,7 +255,8 @@ Setting to YES will cause the kernel to ignore ICMP REDIRECT packets.
|
||||
(bool) Set to
|
||||
.Ar NO
|
||||
by default.
|
||||
Setting to YES will cause the kernel to log ICMP REDIRECT packets. Note that
|
||||
Setting to YES will cause the kernel to log ICMP REDIRECT packets.
|
||||
Note that
|
||||
the log messages are not rate-limited, so this option should only be used
|
||||
for troubleshooting your own network.
|
||||
.It Ar network_interfaces
|
||||
@ -314,7 +321,8 @@ See the manual for a full description.
|
||||
.It Ar ppp_nat
|
||||
(bool) If set to
|
||||
.Ar YES ,
|
||||
enables packet aliasing. Used in conjunction with
|
||||
enables packet aliasing.
|
||||
Used in conjunction with
|
||||
.Ar gateway_enable
|
||||
allows hosts on private network addresses access to the Internet using
|
||||
this host as a network address translating router.
|
||||
@ -326,7 +334,8 @@ this host as a network address translating router.
|
||||
the settings in
|
||||
.Pa /etc/defaults/rc.conf .
|
||||
The files will be read in the order in which they are specified and should
|
||||
include the full path to the file. By default, the files specified are
|
||||
include the full path to the file.
|
||||
By default, the files specified are
|
||||
.Pa /etc/rc.conf
|
||||
and
|
||||
.Pa /etc/rc.conf.local
|
||||
@ -475,7 +484,8 @@ is set, start
|
||||
.Xr mountd 8 ,
|
||||
but not
|
||||
.Xr nfsd 8
|
||||
daemon. It is commonly needed to run CFS without real NFS used.
|
||||
daemon.
|
||||
It is commonly needed to run CFS without real NFS used.
|
||||
.It Ar weak_mountd_authentication
|
||||
(bool) If set to
|
||||
.Ar YES ,
|
||||
@ -996,7 +1006,8 @@ versapad Interlink VersaPad (serial)
|
||||
|
||||
.Ed
|
||||
Even if your mouse is not in the above list, it may be compatible
|
||||
with one in the list. Refer to the man page for
|
||||
with one in the list.
|
||||
Refer to the man page for
|
||||
.Xr moused 8
|
||||
for compatibility information.
|
||||
.Pp
|
||||
@ -1009,7 +1020,8 @@ mouse data is converted to this single canonical format when
|
||||
using
|
||||
.Xr moused 8 .
|
||||
If the client program does not support the sysmouse type,
|
||||
specify the mousesystems type. It is the second prefered type.
|
||||
specify the mousesystems type.
|
||||
It is the second prefered type.
|
||||
.It Ar moused_port
|
||||
(str) If
|
||||
.Ar moused_enable
|
||||
|
@ -106,9 +106,12 @@ The search list is currently limited to six domains
|
||||
with a total of 256 characters.
|
||||
.It Sy sortlist
|
||||
Sortlist allows addresses returned by gethostbyname to be sorted.
|
||||
A sortlist is specified by IP address netmask pairs. The netmask is
|
||||
optional and defaults to the natural netmask of the net. The IP address
|
||||
and optional network pairs are separated by slashes. Up to 10 pairs may
|
||||
A sortlist is specified by IP address netmask pairs.
|
||||
The netmask is
|
||||
optional and defaults to the natural netmask of the net.
|
||||
The IP address
|
||||
and optional network pairs are separated by slashes.
|
||||
Up to 10 pairs may
|
||||
be specified.
|
||||
.Pp
|
||||
e.g. sortlist 130.155.160.0/255.255.240.0 130.155.0.0
|
||||
@ -134,7 +137,8 @@ sets a threshold for the number of dots which must appear in a name given to
|
||||
.Xr resolver 3 )
|
||||
before an
|
||||
.Em initial absolute query
|
||||
will be made. The default for
|
||||
will be made.
|
||||
The default for
|
||||
.Em n
|
||||
is
|
||||
.Dq 1 ,
|
||||
|
@ -38,7 +38,8 @@
|
||||
.Nm intro
|
||||
.Nd "introduction to games"
|
||||
.Sh DESCRIPTION
|
||||
This section contains information about games. The games
|
||||
This section contains information about games.
|
||||
The games
|
||||
are located in
|
||||
.Pa /usr/games
|
||||
if installed.
|
||||
|
@ -164,7 +164,8 @@ is not specified it is taken to be the prevailing indent.
|
||||
.It ".IR" Op Ar words
|
||||
join
|
||||
.Ar words
|
||||
alternating italic and roman faces. Does not cause a line break. If no
|
||||
alternating italic and roman faces.
|
||||
Does not cause a line break. If no
|
||||
arguments are given the next text line is processed.
|
||||
.It ".LP"
|
||||
begin a left-aligned paragraph. The prevailing indent is set to the
|
||||
@ -291,7 +292,8 @@ section is "what does it do?" or "what is it for?".
|
||||
.Pp
|
||||
Literal text, filenames and references to items that appear elsewhere
|
||||
in the reference manuals should be presented using a constant width
|
||||
face. Arguments should be presented using an italic face.
|
||||
face.
|
||||
Arguments should be presented using an italic face.
|
||||
.It ".SH OPTIONS"
|
||||
The list of options together with a description of how each affects
|
||||
the commands operation.
|
||||
|
@ -193,7 +193,8 @@ is used.
|
||||
End-display (matches \&.Bd).
|
||||
.It Li \&.Bl
|
||||
Begin-list.
|
||||
Create lists or columns. Options:
|
||||
Create lists or columns.
|
||||
Options:
|
||||
.Bl -tag -width flag -compact
|
||||
.It Ar List-types
|
||||
.Bl -column xbullet -compact
|
||||
|
@ -1583,7 +1583,8 @@ than
|
||||
.Xr nroff .
|
||||
If formatted with
|
||||
.Xr nroff ,
|
||||
a quoted literal is always quoted. If formatted with
|
||||
a quoted literal is always quoted.
|
||||
If formatted with
|
||||
troff, an item is only quoted if the width
|
||||
of the item is less than three constant width characters.
|
||||
This is to make short strings more visible where the font change
|
||||
|
@ -115,7 +115,8 @@ the multicast routing daemon.
|
||||
.Pp
|
||||
.Nm Rc.firewall
|
||||
is used to configure rules for the kernel based firewall
|
||||
service. It has several possible options:
|
||||
service.
|
||||
It has several possible options:
|
||||
.Pp
|
||||
.Bl -tag -width "fBfilename" -compact -offset indent
|
||||
.It open
|
||||
|
@ -43,7 +43,8 @@ A special file mode, called the
|
||||
.Em sticky bit
|
||||
(mode S_ISVTX),
|
||||
is used to indicate special treatment
|
||||
for directories. It is ignored for regular files.
|
||||
for directories.
|
||||
It is ignored for regular files.
|
||||
See
|
||||
.Xr chmod 2
|
||||
or
|
||||
|
@ -68,7 +68,8 @@ flag is set in
|
||||
then the filesystem should update its internal state from the value of
|
||||
.Fa mp->mnt_flag .
|
||||
This can be used, for instance, to convert a read-only filesystem to
|
||||
read-write. It is also used by
|
||||
read-write.
|
||||
It is also used by
|
||||
.Xr mountd 8
|
||||
to update the NFS export information for the filesystem.
|
||||
.Pp
|
||||
|
@ -49,7 +49,8 @@ the system (ISA, PCI etc.) will be attached directly to
|
||||
.Dv root_bus
|
||||
and other devices will be added as children of their relevant bus.
|
||||
.Pp
|
||||
The devices in a system form a tree. All devices except
|
||||
The devices in a system form a tree.
|
||||
All devices except
|
||||
.Dv root_bus
|
||||
have a parent (see
|
||||
.Xr device_get_parent 9 ).
|
||||
|
@ -49,10 +49,12 @@
|
||||
.Pp
|
||||
Manipulate the verbose description of a device. This description (if
|
||||
present) is printed as part of the message when it is attached during
|
||||
autoconfiguration. The variation
|
||||
autoconfiguration.
|
||||
The variation
|
||||
.Xr device_set_desc_copy 9
|
||||
is used to set the description if the string passed is a temporary
|
||||
buffer which will be overwritten. In this case, the system will copy
|
||||
buffer which will be overwritten.
|
||||
In this case, the system will copy
|
||||
the string, otherwise the pointer passed will be used directly.
|
||||
.Sh SEE ALSO
|
||||
.Xr device 9
|
||||
|
@ -74,7 +74,8 @@ checks addresses in the kernel address space, while
|
||||
.Fn useracc
|
||||
considers
|
||||
.Fa addr
|
||||
to represent an user space address. The process context to use for this
|
||||
to represent an user space address.
|
||||
The process context to use for this
|
||||
operation is taken from the global variable
|
||||
.Va curproc .
|
||||
.Pp
|
||||
@ -82,7 +83,8 @@ operation is taken from the global variable
|
||||
Both functions return boolean true if the type of access specified
|
||||
by
|
||||
.Fa rw
|
||||
is permitted. Otherwise boolean false is returned.
|
||||
is permitted.
|
||||
Otherwise boolean false is returned.
|
||||
.Pp
|
||||
.Sh BUGS
|
||||
The process pointer should be passed in as an argument to
|
||||
|
@ -199,7 +199,8 @@ such things as writing outside the allocated area and imbalanced calls to the
|
||||
.Fn malloc
|
||||
and
|
||||
.Fn free
|
||||
functions. Failing consistency checks will cause a panic or a system console
|
||||
functions.
|
||||
Failing consistency checks will cause a panic or a system console
|
||||
message:
|
||||
.Bl -bullet -offset indent -compact
|
||||
.Pp
|
||||
|
@ -54,7 +54,8 @@
|
||||
The
|
||||
.Fn mi_switch
|
||||
function implements the machine independent prelude to a process context
|
||||
switch. It is called from only a few distinguished places in the kernel
|
||||
switch.
|
||||
It is called from only a few distinguished places in the kernel
|
||||
code as a result of the principle of non-preemtable kernel mode execution.
|
||||
The three major uses of
|
||||
.Nm
|
||||
@ -70,10 +71,12 @@ available.
|
||||
.It
|
||||
after handling a trap
|
||||
.Pq e.g. a system call, device interrupt
|
||||
when the kernel prepares a return to user-mode execution. This case is
|
||||
when the kernel prepares a return to user-mode execution.
|
||||
This case is
|
||||
typically handled by machine dependent trap-handling code after detection
|
||||
of a change in the signal disposition of the current process, or when a
|
||||
higher priority process might be available to run. The latter event is
|
||||
higher priority process might be available to run.
|
||||
The latter event is
|
||||
communicated by the machine independent scheduling routines by calling
|
||||
the machine defined
|
||||
.Fn need_resched .
|
||||
@ -101,7 +104,8 @@ which will perform the actual process context switch.
|
||||
.Pp
|
||||
.Fn cpu_switch
|
||||
will make a choice amongst the processes which are ready to run from a
|
||||
priority queue data-structure. The priority queue consists of an array
|
||||
priority queue data-structure.
|
||||
The priority queue consists of an array
|
||||
.Va qs[NQS]
|
||||
of queue header structures each of which identifies a list of runnable
|
||||
processes of equal priority
|
||||
@ -122,8 +126,10 @@ If no processes are available on the run queues,
|
||||
.Fn cpu_switch
|
||||
shall go into an
|
||||
.Dq idle
|
||||
loop. The idle loop must allow interrupts to be taken that will eventually
|
||||
cause processes to appear again on the run queues. The variable
|
||||
loop.
|
||||
The idle loop must allow interrupts to be taken that will eventually
|
||||
cause processes to appear again on the run queues.
|
||||
The variable
|
||||
.Va curproc
|
||||
should be
|
||||
.Dv NULL
|
||||
|
@ -64,12 +64,14 @@ instead.
|
||||
and
|
||||
.Fn nanotime
|
||||
always query the timecounter to return the current time as precisely as
|
||||
possible. Whereas
|
||||
possible.
|
||||
Whereas
|
||||
.Fn getmicrotime
|
||||
and
|
||||
.Fn getnanotime
|
||||
functions are abstractions which can alternately return a less precise, but
|
||||
faster to obtain, time. This behaviour can be toggled via the
|
||||
faster to obtain, time.
|
||||
This behaviour can be toggled via the
|
||||
kern.timecounter.method sysctl variable:
|
||||
.Bl -tag -width ABC
|
||||
.It Dv 0
|
||||
|
@ -64,12 +64,14 @@ instead.
|
||||
and
|
||||
.Fn nanouptime
|
||||
always query the timecounter to return the current time as precisely as
|
||||
possible. Whereas
|
||||
possible.
|
||||
Whereas
|
||||
.Fn getmicrouptime
|
||||
and
|
||||
.Fn getnanouptime
|
||||
functions are abstractions which can alternately return a less precise, but
|
||||
faster to obtain, time. This behaviour can be toggled via the
|
||||
faster to obtain, time.
|
||||
This behaviour can be toggled via the
|
||||
kern.timecounter.method sysctl variable:
|
||||
.Bl -tag -width ABC
|
||||
.It Dv 0
|
||||
|
@ -53,7 +53,8 @@
|
||||
The
|
||||
.Fn physio
|
||||
is a helper function typically called from character device read and write
|
||||
routines to start I/O on a user process buffer. It calls back on the
|
||||
routines to start I/O on a user process buffer.
|
||||
It calls back on the
|
||||
provided
|
||||
.Fa strategy
|
||||
routine one or more times to complete the transfer described by
|
||||
@ -62,7 +63,8 @@ The maximum amount of data to transfer with each call to
|
||||
.Fa strategy
|
||||
is determined by the
|
||||
.Fa minphys
|
||||
routine. Since
|
||||
routine.
|
||||
Since
|
||||
.Fa uio
|
||||
normally describes user space addresses,
|
||||
.Fn physio
|
||||
@ -71,7 +73,8 @@ needs to lock the process into memory. This is done by setting the
|
||||
flag on the process.
|
||||
.Fn physio
|
||||
always awaits the completion of the entire requested transfer before
|
||||
returning, unless an error condition is detected earlier. In all cases,
|
||||
returning, unless an error condition is detected earlier.
|
||||
In all cases,
|
||||
the buffer passed in
|
||||
.Fa bp
|
||||
is locked (marked as
|
||||
@ -84,11 +87,13 @@ A break-down of the arguments follows:
|
||||
The device strategy routine to call for each chunk of data to initiate
|
||||
device I/O.
|
||||
.It Fa bp
|
||||
The buffer to use with the strategy routine. The buffer flags will have
|
||||
The buffer to use with the strategy routine.
|
||||
The buffer flags will have
|
||||
.Dv B_BUSY ,
|
||||
and
|
||||
.Dv B_PHYS
|
||||
set when passed to the strategy routine. If
|
||||
set when passed to the strategy routine.
|
||||
If
|
||||
.Dv NULL ,
|
||||
a buffer is allocated from a system pool.
|
||||
.It Fa dev
|
||||
@ -126,7 +131,8 @@ by examining the
|
||||
.Dv B_ERROR
|
||||
buffer flag and the
|
||||
.Va b_error
|
||||
field. Note that the actual transfer size may be less than requested by
|
||||
field.
|
||||
Note that the actual transfer size may be less than requested by
|
||||
.Fa uio
|
||||
if the device signals an
|
||||
.Dq end of file
|
||||
|
@ -53,7 +53,8 @@
|
||||
.Ft void
|
||||
.Fn gsignal "int pgid" "int signum"
|
||||
.Sh DESCRIPTION
|
||||
These functions post a signal to one or more processes. The argument
|
||||
These functions post a signal to one or more processes.
|
||||
The argument
|
||||
.Fa signum
|
||||
common to all three functions should be in the range
|
||||
.Bq 1- Ns Dv NSIG .
|
||||
@ -66,14 +67,16 @@ to the process represented by the process structure
|
||||
.Fa p .
|
||||
With a few exceptions noted below, the target process signal disposition is
|
||||
updated and is marked as runnable, so further handling of the signal is done
|
||||
in the context of the target process after a context switch. Note that
|
||||
in the context of the target process after a context switch.
|
||||
Note that
|
||||
.Fn psignal
|
||||
does not by itself cause a context switch to happen.
|
||||
.Pp
|
||||
The target process is not marked as runnable in the following cases:
|
||||
.Bl -bullet -offset indent
|
||||
.It
|
||||
The target process is sleeping uninterruptibly. The signal will be
|
||||
The target process is sleeping uninterruptibly.
|
||||
The signal will be
|
||||
noticed when the process returns from the system call or trap.
|
||||
.It
|
||||
The target process is currently ignoring the signal.
|
||||
@ -114,7 +117,8 @@ pointed at by
|
||||
.Fa pgrp
|
||||
and calling
|
||||
.Fn psignal
|
||||
as appropriate. If
|
||||
as appropriate.
|
||||
If
|
||||
.Fa pgrp
|
||||
is
|
||||
.Dv NULL
|
||||
@ -133,7 +137,8 @@ then invokes
|
||||
.Fn pgsignal
|
||||
with the argument
|
||||
.Fa checkctty
|
||||
set to zero. If
|
||||
set to zero.
|
||||
If
|
||||
.Fa pgid
|
||||
is zero no action is taken.
|
||||
.Sh SEE ALSO
|
||||
|
Loading…
x
Reference in New Issue
Block a user