d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Sort sections.

Browse Source
This commit is contained in:
Ruslan Ermilov 2005-01-21 08:36:40 +00:00
parent fc2586c322
commit 9cbda59000
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=140561
150 changed files with 1167 additions and 1167 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
share/examples/scsi_target/scsi_target.8
View File

@ -119,6 +119,13 @@ All options default to the minimal functionality of SCSI-1.
To be safe,
.Nm
checks the SIM for the requested capability before enabling target mode.
.Sh FILES
.Bl -tag -width ".Pa /usr/share/examples/scsi_target" -compact
.It Pa /dev/targ*
Control devices.
.It Pa /usr/share/examples/scsi_target
Source directory.
.El
.Sh EXAMPLES
Create a 5 megabyte backing store file.
.Pp
@ -134,13 +141,6 @@ Debugging information will be output.
16-bit wide transfers will be used if the SIM supports them.
.Pp
.Dl "scsi_target -d -s 1000 -W 16 0:1:0 vol"
.Sh FILES
.Bl -tag -width ".Pa /usr/share/examples/scsi_target" -compact
.It Pa /dev/targ*
Control devices.
.It Pa /usr/share/examples/scsi_target
Source directory.
.El
.Sh SEE ALSO
.Xr scsi 4 ,
.Xr targ 4

10
share/man/man3/pthread_attr_get_np.3
View File

@ -68,6 +68,11 @@ The
.Fn pthread_attr_get_np
function will always return a pointer to the thread's real stack address,
regardless of its value in the original attributes structure.
.Sh RETURN VALUES
If successful,
.Fn pthread_attr_get_np
function returns 0.
Otherwise, an error number is returned to indicate the error.
.Sh EXAMPLES
.Bd -literal
size_t
@ -83,11 +88,6 @@ my_thread_stack_size(pthread_t pid)
return(size);
}
.Ed
.Sh RETURN VALUES
If successful,
.Fn pthread_attr_get_np
function returns 0.
Otherwise, an error number is returned to indicate the error.
.Sh ERRORS
The
.Fn pthread_attr_get_np

18
share/man/man3/pthread_barrier_destroy.3
View File

@ -75,6 +75,15 @@ any of them will be released is determined by the
argument to
.Fn pthread_barrier_init .
Once the threads have been released the barrier will be reset.
.Sh IMPLEMENTATION NOTES
In both
.Lb libpthread
and
.Lb libthr
the
.Dv PTHREAD_BARRIER_SERIAL_THREAD
return value will
always be returned by the last thread to reach the barrier.
.Sh RETURN VALUES
If successful,
both
@ -92,15 +101,6 @@ Otherwise, an error number will be returned to indicate the error.
.Pp
None of these functions will return
.Er EINTR .
.Sh IMPLEMENTATION NOTES
In both
.Lb libpthread
and
.Lb libthr
the
.Dv PTHREAD_BARRIER_SERIAL_THREAD
return value will
always be returned by the last thread to reach the barrier.
.Sh ERRORS
The
.Fn pthread_barrier_destroy

14
share/man/man3/pthread_rwlock_destroy.3
View File

@ -49,13 +49,6 @@ If successful, the
function will return zero.
Otherwise an error number will be returned
to indicate the error.
.Sh SEE ALSO
.Xr pthread_rwlock_init 3
.Sh STANDARDS
The
.Fn pthread_rwlock_destroy
function is expected to conform to
.St -susv2 .
.Sh ERRORS
The
.Fn pthread_rwlock_destroy
@ -78,6 +71,13 @@ The value specified by
.Fa lock
is invalid.
.El
.Sh SEE ALSO
.Xr pthread_rwlock_init 3
.Sh STANDARDS
The
.Fn pthread_rwlock_destroy
function is expected to conform to
.St -susv2 .
.Sh HISTORY
The
.Fn pthread_rwlock_destroy

18
share/man/man3/pthread_rwlock_init.3
View File

@ -57,15 +57,6 @@ If successful, the
function will return zero.
Otherwise an error number will be returned
to indicate the error.
.Sh SEE ALSO
.Xr pthread_rwlockattr_init 3 ,
.Xr pthread_rwlockattr_setpshared 3 ,
.Xr pthread_rwlock_destroy 3
.Sh STANDARDS
The
.Fn pthread_rwlock_init
function is expected to conform to
.St -susv2 .
.Sh ERRORS
The
.Fn pthread_rwlock_init
@ -95,6 +86,15 @@ The value specified by
.Fa attr
is invalid.
.El
.Sh SEE ALSO
.Xr pthread_rwlockattr_init 3 ,
.Xr pthread_rwlockattr_setpshared 3 ,
.Xr pthread_rwlock_destroy 3
.Sh STANDARDS
The
.Fn pthread_rwlock_init
function is expected to conform to
.St -susv2 .
.Sh HISTORY
The
.Fn pthread_rwlock_init

24
share/man/man3/pthread_rwlock_rdlock.3
View File

@ -77,18 +77,6 @@ and
functions will return zero.
Otherwise an error number will be returned
to indicate the error.
.Sh SEE ALSO
.Xr pthread_rwlock_init 3 ,
.Xr pthread_rwlock_trywrlock 3 ,
.Xr pthread_rwlock_unlock 3 ,
.Xr pthread_rwlock_wrlock 3
.Sh STANDARDS
The
.Fn pthread_rwlock_rdlock
and
.Fn pthread_rwlock_tryrdlock
functions are expected to conform to
.St -susv2 .
.Sh ERRORS
The
.Fn pthread_rwlock_tryrdlock
@ -122,6 +110,18 @@ is invalid.
Insufficient memory exists to initialize the lock (applies to
statically initialized locks only).
.El
.Sh SEE ALSO
.Xr pthread_rwlock_init 3 ,
.Xr pthread_rwlock_trywrlock 3 ,
.Xr pthread_rwlock_unlock 3 ,
.Xr pthread_rwlock_wrlock 3
.Sh STANDARDS
The
.Fn pthread_rwlock_rdlock
and
.Fn pthread_rwlock_tryrdlock
functions are expected to conform to
.St -susv2 .
.Sh HISTORY
The
.Fn pthread_rwlock_rdlock

16
share/man/man3/pthread_rwlock_unlock.3
View File

@ -57,14 +57,6 @@ to indicate the error.
The results are undefined if
.Fa lock
is not held by the calling thread.
.Sh SEE ALSO
.Xr pthread_rwlock_rdlock 3 ,
.Xr pthread_rwlock_wrlock 3
.Sh STANDARDS
The
.Fn pthread_rwlock_unlock
function is expected to conform to
.St -susv2 .
.Sh ERRORS
The
.Fn pthread_rwlock_unlock
@ -77,6 +69,14 @@ is invalid.
.It Bq Er EPERM
The current thread does not own the read/write lock.
.El
.Sh SEE ALSO
.Xr pthread_rwlock_rdlock 3 ,
.Xr pthread_rwlock_wrlock 3
.Sh STANDARDS
The
.Fn pthread_rwlock_unlock
function is expected to conform to
.St -susv2 .
.Sh HISTORY
The
.Fn pthread_rwlock_unlock

24
share/man/man3/pthread_rwlock_wrlock.3
View File

@ -63,18 +63,6 @@ and
functions will return zero.
Otherwise an error number will be returned
to indicate the error.
.Sh SEE ALSO
.Xr pthread_rwlock_init 3 ,
.Xr pthread_rwlock_rdlock 3 ,
.Xr pthread_rwlock_tryrdlock 3 ,
.Xr pthread_rwlock_unlock 3
.Sh STANDARDS
The
.Fn pthread_rwlock_wrlock
and
.Fn pthread_rwlock_trywrlock
functions are expected to conform to
.St -susv2 .
.Sh ERRORS
The
.Fn pthread_rwlock_trywrlock
@ -101,6 +89,18 @@ is invalid.
Insufficient memory exists to initialize the lock (applies to
statically initialized locks only).
.El
.Sh SEE ALSO
.Xr pthread_rwlock_init 3 ,
.Xr pthread_rwlock_rdlock 3 ,
.Xr pthread_rwlock_tryrdlock 3 ,
.Xr pthread_rwlock_unlock 3
.Sh STANDARDS
The
.Fn pthread_rwlock_wrlock
and
.Fn pthread_rwlock_trywrlock
functions are expected to conform to
.St -susv2 .
.Sh HISTORY
The
.Fn pthread_rwlock_wrlock

14
share/man/man3/pthread_rwlockattr_destroy.3
View File

@ -50,13 +50,6 @@ If successful, the
function will return zero.
Otherwise an error number will be returned
to indicate the error.
.Sh SEE ALSO
.Xr pthread_rwlockattr_init 3
.Sh STANDARDS
The
.Fn pthread_rwlockattr_destroy
function is expected to conform to
.St -susv2 .
.Sh ERRORS
The
.Fn pthread_rwlockattr_destroy
@ -67,6 +60,13 @@ The value specified by
.Fa attr
is invalid.
.El
.Sh SEE ALSO
.Xr pthread_rwlockattr_init 3
.Sh STANDARDS
The
.Fn pthread_rwlockattr_destroy
function is expected to conform to
.St -susv2 .
.Sh HISTORY
The
.Fn pthread_rwlockattr_destroy

18
share/man/man3/pthread_rwlockattr_getpshared.3
View File

@ -62,15 +62,6 @@ If successful, the
function will return zero.
Otherwise an error number will be returned
to indicate the error.
.Sh SEE ALSO
.Xr pthread_rwlockattr_init 3 ,
.Xr pthread_rwlockattr_setpshared 3 ,
.Xr pthread_rwlock_init 3
.Sh STANDARDS
The
.Fn pthread_rwlockattr_getpshared
function is expected to conform to
.St -susv2 .
.Sh ERRORS
The
.Fn pthread_rwlockattr_getpshared
@ -81,6 +72,15 @@ The value specified by
.Fa attr
is invalid.
.El
.Sh SEE ALSO
.Xr pthread_rwlockattr_init 3 ,
.Xr pthread_rwlockattr_setpshared 3 ,
.Xr pthread_rwlock_init 3
.Sh STANDARDS
The
.Fn pthread_rwlockattr_getpshared
function is expected to conform to
.St -susv2 .
.Sh HISTORY
The
.Fn pthread_rwlockattr_getpshared

16
share/man/man3/pthread_rwlockattr_init.3
View File

@ -48,6 +48,14 @@ If successful, the
function will return zero.
Otherwise an error number will be returned
to indicate the error.
.Sh ERRORS
The
.Fn pthread_rwlockattr_init
function will fail if:
.Bl -tag -width Er
.It Bq Er ENOMEM
Insufficient memory exists to initialize the attribute object.
.El
.Sh SEE ALSO
.Xr pthread_rwlockattr_destroy 3 ,
.Xr pthread_rwlockattr_getpshared 3 ,
@ -58,14 +66,6 @@ The
.Fn pthread_rwlockattr_init
function is expected to conform to
.St -susv2 .
.Sh ERRORS
The
.Fn pthread_rwlockattr_init
function will fail if:
.Bl -tag -width Er
.It Bq Er ENOMEM
Insufficient memory exists to initialize the attribute object.
.El
.Sh HISTORY
The
.Fn pthread_rwlockattr_init

18
share/man/man3/pthread_rwlockattr_setpshared.3
View File

@ -64,15 +64,6 @@ If successful, the
function will return zero.
Otherwise an error number will be returned
to indicate the error.
.Sh SEE ALSO
.Xr pthread_rwlockattr_getpshared 3 ,
.Xr pthread_rwlockattr_init 3 ,
.Xr pthread_rwlock_init 3
.Sh STANDARDS
The
.Fn pthread_rwlockattr_setpshared
function is expected to conform to
.St -susv2 .
.Sh ERRORS
The
.Fn pthread_rwlockattr_setpshared
@ -85,6 +76,15 @@ or
.Fa pshared
is invalid.
.El
.Sh SEE ALSO
.Xr pthread_rwlockattr_getpshared 3 ,
.Xr pthread_rwlockattr_init 3 ,
.Xr pthread_rwlock_init 3
.Sh STANDARDS
The
.Fn pthread_rwlockattr_setpshared
function is expected to conform to
.St -susv2 .
.Sh HISTORY
The
.Fn pthread_rwlockattr_setpshared

14
share/man/man3/stdarg.3
View File

@ -196,6 +196,13 @@ void foo(char *fmt, ...)
va_end(ap);
}
.Ed
.Sh COMPATIBILITY
These macros are
.Em not
compatible with the historic macros they replace.
A backward compatible version can be found in the include
file
.In varargs.h .
.Sh STANDARDS
The
.Fn va_start ,
@ -205,13 +212,6 @@ and
.Fn va_end
macros conform to
.St -isoC-99 .
.Sh COMPATIBILITY
These macros are
.Em not
compatible with the historic macros they replace.
A backward compatible version can be found in the include
file
.In varargs.h .
.Sh BUGS
Unlike the
.Em varargs

10
share/man/man4/adv.4
View File

@ -224,6 +224,11 @@ RATOC REX-PCI30 (PC-98)
.Xr da 4 ,
.Xr sa 4 ,
.Xr scsi 4
.Sh HISTORY
The
.Nm
driver appeared in
.Fx 3.0 .
.Sh AUTHORS
.An -nosplit
The
@ -237,8 +242,3 @@ of Advanced System Products, Inc.
Many thanks to AdvanSys for providing the original driver under a suitable
license for use in
.Fx .
.Sh HISTORY
The
.Nm
driver appeared in
.Fx 3.0 .

10
share/man/man4/adw.4
View File

@ -82,6 +82,11 @@ AdvanSys ABP3950U2W
.Xr da 4 ,
.Xr sa 4 ,
.Xr scsi 4
.Sh HISTORY
The
.Nm
driver appeared in
.Fx 3.0 .
.Sh AUTHORS
.An -nosplit
The
@ -94,8 +99,3 @@ of Advanced System Products, Inc.
Many thanks to AdvanSys for providing the original driver
under a suitable license for use in
.Fx .
.Sh HISTORY
The
.Nm
driver appeared in
.Fx 3.0 .

24
share/man/man4/aha.4
View File

@ -89,18 +89,6 @@ DTC 3290 SCSI controller in 1542 emulation mode
.It
Tekram SCSI controllers in 154x emulation mode
.El
.Sh BUGS
The AHA-154xA card does not support residuals on data transfers.
As a result, this card is no longer supported.
.Pp
There have been some reports that the AHA-154xB does not work well
under heavy load.
.Pp
The AHA-154xCP is a plug and play controller.
However, its resources are set using the on-board BIOS and cannot be
moved.
Failures to attached for this card are often caused when the resources
set in the BIOS conflict.
.Sh SEE ALSO
.Xr ahb 4 ,
.Xr ahc 4 ,
@ -122,3 +110,15 @@ from the
.Nm bt
driver written by
.An Justin T. Gibbs .
.Sh BUGS
The AHA-154xA card does not support residuals on data transfers.
As a result, this card is no longer supported.
.Pp
There have been some reports that the AHA-154xB does not work well
under heavy load.
.Pp
The AHA-154xCP is a plug and play controller.
However, its resources are set using the on-board BIOS and cannot be
moved.
Failures to attached for this card are often caused when the resources
set in the BIOS conflict.

40
share/man/man4/ahc.4
View File

@ -388,6 +388,26 @@ Since the
local SCB space serves as a cache for disconnected transactions, the
more SCB space available, the less host bus traffic consumed saving
and restoring SCB data.
.Sh SEE ALSO
.Xr aha 4 ,
.Xr ahb 4 ,
.Xr cd 4 ,
.Xr da 4 ,
.Xr sa 4 ,
.Xr scsi 4
.Sh HISTORY
The
.Nm
driver appeared in
.Fx 2.0 .
.Sh AUTHORS
The
.Nm
driver, the
.Tn AIC7xxx
sequencer-code assembler,
and the firmware running on the aic7xxx chips was written by
.An Justin T. Gibbs .
.Sh BUGS
Some Quantum drives (at least the Empire 2100 and 1080s) will not run on an
.Tn AIC7870
@ -412,23 +432,3 @@ voltage differential boards as shipped by Adaptec.
Information on
how to modify HVD board to work correctly in target mode is available
from Adaptec.
.Sh SEE ALSO
.Xr aha 4 ,
.Xr ahb 4 ,
.Xr cd 4 ,
.Xr da 4 ,
.Xr sa 4 ,
.Xr scsi 4
.Sh AUTHORS
The
.Nm
driver, the
.Tn AIC7xxx
sequencer-code assembler,
and the firmware running on the aic7xxx chips was written by
.An Justin T. Gibbs .
.Sh HISTORY
The
.Nm
driver appeared in
.Fx 2.0 .

18
share/man/man4/ahd.4
View File

@ -153,16 +153,17 @@ Many motherboards with on-board
.Tn SCSI
support
.El
.Sh BUGS
The current generation of 79xx chips do not support target mode in Ultra320
mode.
Target mode in general has not been well tested in this driver.
.Sh SEE ALSO
.Xr ahc 4 ,
.Xr cd 4 ,
.Xr da 4 ,
.Xr sa 4 ,
.Xr scsi 4
.Sh HISTORY
The
.Nm
driver first appeared in
.Fx 4.7 .
.Sh AUTHORS
The
.Nm
@ -174,8 +175,7 @@ and the firmware running on the aic79xx chips was written by
This manual page is based on the
.Xr ahc 4
manual page.
.Sh HISTORY
The
.Nm
driver first appeared in
.Fx 4.7 .
.Sh BUGS
The current generation of 79xx chips do not support target mode in Ultra320
mode.
Target mode in general has not been well tested in this driver.

20
share/man/man4/bktr.4
View File

@ -189,16 +189,6 @@ Video Highway XTreme
.It
VideoLogic Captivator PCI
.El
.Sh AUTHORS
.An -nosplit
This driver is based on the work of
.An Jim Lowe Aq james@miller.cs.uwm.edu ,
.An Mark Tinguely Aq tinguely@plains.nodak.edu ,
.An Amancio Hasty Aq hasty@star-gate.com ,
.An Roger Hardiman Aq roger@FreeBSD.org
and a bunch of other people.
Support for Pinnacle PCTV Rave cards was added by
.An Branko Lankester Aq branko@euro.net .
.Sh FILES
.Bl -tag -width /usr/share/examples/meteor -compact
.It Pa /usr/share/examples/meteor
@ -234,3 +224,13 @@ The
.Nm
driver first appeared in
.Fx 2.2 .
.Sh AUTHORS
.An -nosplit
This driver is based on the work of
.An Jim Lowe Aq james@miller.cs.uwm.edu ,
.An Mark Tinguely Aq tinguely@plains.nodak.edu ,
.An Amancio Hasty Aq hasty@star-gate.com ,
.An Roger Hardiman Aq roger@FreeBSD.org
and a bunch of other people.
Support for Pinnacle PCTV Rave cards was added by
.An Branko Lankester Aq branko@euro.net .

4
share/man/man4/blackhole.4
View File

@ -73,11 +73,11 @@ It should be used together with other security mechanisms.
.Xr udp 4 ,
.Xr ipfw 8 ,
.Xr sysctl 8
.Sh AUTHORS
.An Geoffrey M. Rehmet
.Sh HISTORY
The TCP and UDP
.Nm
MIBs
first appeared in
.Fx 4.0 .
.Sh AUTHORS
.An Geoffrey M. Rehmet

54
share/man/man4/bpf.4
View File

@ -605,6 +605,11 @@ array initializers:
.Fn BPF_STMT opcode operand
and
.Fn BPF_JUMP opcode operand true_offset false_offset .
.Sh FILES
.Bl -tag -compact -width /dev/bpfXXX
.It Pa /dev/bpf Ns Sy n
the packet filter device
.El
.Sh EXAMPLES
The following filter is taken from the Reverse ARP Daemon.
It accepts only Reverse ARP requests.
@ -673,33 +678,6 @@ struct bpf_insn insns[] = {
.%A Jacobson V.
.%T "An efficient, extensible, and portable network monitor"
.Re
.Sh FILES
.Bl -tag -compact -width /dev/bpfXXX
.It Pa /dev/bpf Ns Sy n
the packet filter device
.El
.Sh BUGS
The read buffer must be of a fixed size (returned by the
.Dv BIOCGBLEN
ioctl).
.Pp
A file that does not request promiscuous mode may receive promiscuously
received packets as a side effect of another file requesting this
mode on the same hardware interface.
This could be fixed in the kernel with additional processing overhead.
However, we favor the model where
all files must assume that the interface is promiscuous, and if
so desired, must utilize a filter to reject foreign packets.
.Pp
Data link protocols with variable length headers are not currently supported.
.Pp
The
.Dv SEESENT
flag has been observed to work incorrectly on some interface
types, including those with hardware loopback rather than software loopback,
and point-to-point interfaces.
It appears to function correctly on a
broad range of Ethernet-style interfaces.
.Sh HISTORY
The Enet packet filter was created in 1980 by Mike Accetta and
Rick Rashid at Carnegie-Mellon University.
@ -724,3 +702,25 @@ of Lawrence Berkeley Laboratory, implemented BPF in
Summer 1990.
Much of the design is due to
.An Van Jacobson .
.Sh BUGS
The read buffer must be of a fixed size (returned by the
.Dv BIOCGBLEN
ioctl).
.Pp
A file that does not request promiscuous mode may receive promiscuously
received packets as a side effect of another file requesting this
mode on the same hardware interface.
This could be fixed in the kernel with additional processing overhead.
However, we favor the model where
all files must assume that the interface is promiscuous, and if
so desired, must utilize a filter to reject foreign packets.
.Pp
Data link protocols with variable length headers are not currently supported.
.Pp
The
.Dv SEESENT
flag has been observed to work incorrectly on some interface
types, including those with hardware loopback rather than software loopback,
and point-to-point interfaces.
It appears to function correctly on a
broad range of Ethernet-style interfaces.

36
share/man/man4/bridge.4
View File

@ -140,6 +140,12 @@ do not support this functionality.
Also, bridging is not compatible with interfaces which
use hardware loopback, because there is no way to tell locally
generated packets from externally generated ones.
.Sh FILES
.Bl -tag -width ".Pa /boot/kernel/bridge.ko" -compact
.It Pa /boot/kernel/bridge.ko
.Nm
loadable module.
.El
.Sh EXAMPLES
A simple
.Nm
@ -200,6 +206,18 @@ is performed by the
devices.
When using VLAN devices, care must be taken by not creating loops
between these devices and their parent interfaces.
.Sh SEE ALSO
.Xr ip 4 ,
.Xr ng_bridge 4 ,
.Xr vlan 4 ,
.Xr ipf 8 ,
.Xr ipfw 8 ,
.Xr sysctl 8
.Sh HISTORY
Bridging was introduced in
.Fx 2.2.8
by
.An Luigi Rizzo Aq luigi@iet.unipi.it .
.Sh BUGS
Care must be taken not to construct loops in the
.Nm
@ -232,21 +250,3 @@ It might be useful to have a rule of the form
.Pp
near the beginning of your ruleset to implement specific rulesets
for bridged packets.
.Sh FILES
.Bl -tag -width ".Pa /boot/kernel/bridge.ko" -compact
.It Pa /boot/kernel/bridge.ko
.Nm
loadable module.
.El
.Sh SEE ALSO
.Xr ip 4 ,
.Xr ng_bridge 4 ,
.Xr vlan 4 ,
.Xr ipf 8 ,
.Xr ipfw 8 ,
.Xr sysctl 8
.Sh HISTORY
Bridging was introduced in
.Fx 2.2.8
by
.An Luigi Rizzo Aq luigi@iet.unipi.it .

38
share/man/man4/bt.4
View File

@ -168,11 +168,30 @@ AMI FastDisk Host Adapters that are true BusLogic MultiMaster clones
are also supported by the
.Nm
driver.
.Sh FILES
.Bl -tag -width /usr/share/man0/template.doc -compact
.It Pa sys/dev/buslogic/bt.c
Core Driver Implementation
.It Pa sys/dev/buslogic/btreg.h
MultiMaster Register Set and Core Driver Data Structures
.It Pa sys/pci/bt_pci.c
PCI Bus Driver Attachment
.It Pa sys/i386/eisa/bt_eisa.c
EISA Bus Driver Attachment
.It Pa sys/i386/isa/bt_isa.c
ISA/VL Bus Driver Attachment
.El
.Sh SEE ALSO
.Xr cd 4 ,
.Xr da 4 ,
.Xr sa 4 ,
.Xr scsi 4
.Sh HISTORY
The
.Nm
driver first appeared in the
.Bx 386
patch kit.
.Sh AUTHORS
.An -nosplit
.An Julian Elischer
@ -191,22 +210,3 @@ driver for Linux.
Support in this driver for the wide range of MultiMaster
controllers and firmware revisions, with their otherwise undocumented quirks,
would not have been possible without his efforts.
.Sh FILES
.Bl -tag -width /usr/share/man0/template.doc -compact
.It Pa sys/dev/buslogic/bt.c
Core Driver Implementation
.It Pa sys/dev/buslogic/btreg.h
MultiMaster Register Set and Core Driver Data Structures
.It Pa sys/pci/bt_pci.c
PCI Bus Driver Attachment
.It Pa sys/i386/eisa/bt_eisa.c
EISA Bus Driver Attachment
.It Pa sys/i386/isa/bt_isa.c
ISA/VL Bus Driver Attachment
.El
.Sh HISTORY
The
.Nm
driver first appeared in the
.Bx 386
patch kit.

6
share/man/man4/ccd.4
View File

@ -198,9 +198,6 @@ disk usually destroys whatever data previously existed on that disk.
.Nm
device special files
.El
.Sh HISTORY
The concatenated disk driver was originally written at the University of
Utah.
.Sh SEE ALSO
.Xr dd 1 ,
.Xr ccdconfig 8 ,
@ -210,3 +207,6 @@ Utah.
.Xr mount 8 ,
.Xr newfs 8 ,
.Xr vinum 8
.Sh HISTORY
The concatenated disk driver was originally written at the University of
Utah.

24
share/man/man4/cd.4
View File

@ -481,6 +481,18 @@ None.
.Xr disklabel 5 ,
.Xr disklabel 8 ,
.Xr cd 9
.Sh HISTORY
This
.Nm
driver is based upon the
.Nm
driver written by Julian Elischer, which appeared in
.Bx 386 0.1 .
The
CAM version of the
.Nm
driver was written by Kenneth Merry and first appeared in
.Fx 3.0 .
.Sh BUGS
The names of the structures used for the third argument to
.Fn ioctl
@ -506,15 +518,3 @@ require modification of
to support the two timeouts when hardwiring
.Nm
devices.
.Sh HISTORY
This
.Nm
driver is based upon the
.Nm
driver written by Julian Elischer, which appeared in
.Bx 386 0.1 .
The
CAM version of the
.Nm
driver was written by Kenneth Merry and first appeared in
.Fx 3.0 .

30
share/man/man4/ch.4
View File

@ -316,21 +316,6 @@ driver supports are not thoroughly tested due to the fact that the
devices available for testing do not support the necessary commands.
This is true for alternate volume tags, media flipping, import/export
element handling, multiple picker operation and other things.
.Sh AUTHORS
.An -nosplit
The
.Nm
driver was written by
.An Jason R. Thorpe Aq thorpej@and.com
for And Communications,
.Pa http://www.and.com/ .
It was added to the system by
.An Stefan Grefen Aq grefen@goofy.zdv.uni-mainz.de
who apparently had such a device.
It was ported to CAM by
.An Kenneth Merry Aq ken@FreeBSD.org .
It was updated to support volume tags by
.An Hans Huebner Aq hans@artcom.de .
.Sh FILES
.Bl -tag -width /dev/ch[0-9] -compact
.It Pa /dev/ch[0-9]
@ -351,3 +336,18 @@ The
.Nm
driver appeared in
.Bx 386 0.1 .
.Sh AUTHORS
.An -nosplit
The
.Nm
driver was written by
.An Jason R. Thorpe Aq thorpej@and.com
for And Communications,
.Pa http://www.and.com/ .
It was added to the system by
.An Stefan Grefen Aq grefen@goofy.zdv.uni-mainz.de
who apparently had such a device.
It was ported to CAM by
.An Kenneth Merry Aq ken@FreeBSD.org .
It was updated to support volume tags by
.An Hans Huebner Aq hans@artcom.de .

10
share/man/man4/dcons.4
View File

@ -52,6 +52,11 @@ for interaction.
The buffer consists of 4 channels.
There are 2 ports, one for the console TTY and another is GDB port,
then each port has an input channel and an output channel.
.Sh FILES
.Bl -tag -width indent -compact
.It Pa /dev/dcons
.It Pa /etc/ttys
.El
.Sh EXAMPLES
If you want to run
.Xr getty 8
@ -80,11 +85,6 @@ application.
See
.Xr dconschat 8
for more details.
.Sh FILES
.Bl -tag -width indent -compact
.It Pa /dev/dcons
.It Pa /etc/ttys
.El
.Sh SEE ALSO
.Xr dcons_crom 4 ,
.Xr ddb 4 ,

6
share/man/man4/divert.4
View File

@ -164,6 +164,9 @@ that was not associated with any interface.
.Xr sendto 2 ,
.Xr socket 2 ,
.Xr ipfw 8
.Sh AUTHORS
.An Archie Cobbs Aq archie@FreeBSD.org ,
Whistle Communications Corp.
.Sh BUGS
This is an attempt to provide a clean way for user mode processes
to implement various IP tricks like address translation, but it
@ -177,6 +180,3 @@ packet destined for another machine don't get routed through the
local machine, the packet is lost.
This should probably be
a settable socket option in any case.
.Sh AUTHORS
.An Archie Cobbs Aq archie@FreeBSD.org ,
Whistle Communications Corp.

10
share/man/man4/dpt.4
View File

@ -94,6 +94,11 @@ EISA Bus Driver Attachment
.Xr da 4 ,
.Xr sa 4 ,
.Xr scsi 4
.Sh HISTORY
The
.Nm
driver first appeared in
.Fx 2.2.6 .
.Sh AUTHORS
.An -nosplit
The
@ -102,8 +107,3 @@ driver was written by
.An Simon Shapiro
and ported to the CAM SCSI system by
.An Justin T. Gibbs .
.Sh HISTORY
The
.Nm
driver first appeared in
.Fx 2.2.6 .

14
share/man/man4/ed.4
View File

@ -323,13 +323,6 @@ work in 8bit mode, much higher performance can be achieved by specifying
In addition, you should also specify
.Cd "iosiz 16384"
to take advantage of the extra 8K of shared memory that 16bit mode provides.
.Sh BUGS
The
.Nm
driver is a bit too aggressive about resetting the card whenever any bad
packets are received.
As a result, it may throw out some good packets which
have been received but not yet transferred from the card to main memory.
.Sh SEE ALSO
.Xr arp 4 ,
.Xr miibus 4 ,
@ -346,3 +339,10 @@ The
.Nm
device driver and this manual page were written by
.An David Greenman .
.Sh BUGS
The
.Nm
driver is a bit too aggressive about resetting the card whenever any bad
packets are received.
As a result, it may throw out some good packets which
have been received but not yet transferred from the card to main memory.

26
share/man/man4/fast_ipsec.4
View File

@ -80,19 +80,6 @@ To selectively enable/disable protocols, use
.Xr sysctl 8 .
.Sh DIAGNOSTICS
To be added.
.Sh BUGS
There is presently no support for IPv6.
.Pp
The
.Tn IPcomp
protocol support does not work.
.Pp
Certain legacy authentication algorithms are not supported because of
issues with the
.Xr crypto 4
subsystem.
.Pp
This documentation is incomplete.
.Sh SEE ALSO
.Xr crypto 4 ,
.Xr ipsec 4 ,
@ -114,3 +101,16 @@ The
.Nm
protocols first appeared in
.Fx 5.0 .
.Sh BUGS
There is presently no support for IPv6.
.Pp
The
.Tn IPcomp
protocol support does not work.
.Pp
Certain legacy authentication algorithms are not supported because of
issues with the
.Xr crypto 4
subsystem.
.Pp
This documentation is incomplete.

4
share/man/man4/fatm.4
View File

@ -102,6 +102,8 @@ fatm0: <FORE PCA200E> mem 0xd5800000-0xd59fffff irq 9 at device 9.0 on pci0
.Xr natm 4 ,
.Xr natmip 4 ,
.Xr utopia 4
.Sh AUTHORS
.An Harti Brandt Aq harti@FreeBSD.org
.Sh BUGS
These cards can CBR shape a single VCC only.
It is currently possible to
@ -111,5 +113,3 @@ wrong.
See
.Xr hatm 4
for a better card.
.Sh AUTHORS
.An Harti Brandt Aq harti@FreeBSD.org

20
share/man/man4/fwe.4
View File

@ -61,16 +61,6 @@ This driver supports
as well if it is compiled with the
.Dv DEVICE_POLLING
option.
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 5.0 .
.Sh BUGS
This driver emulates Ethernet in a very adhoc way and it does not reserve a
stream channel using an isochronous manager.
Note that this driver uses a protocol which is very different from RFC 2734
(IPv4 over IEEE 1394).
.Sh SEE ALSO
.Xr arp 4 ,
.Xr firewire 4 ,
@ -82,8 +72,18 @@ Note that this driver uses a protocol which is very different from RFC 2734
.Xr ifconfig 8 ,
.Xr kldload 8 ,
.Xr sysctl 8
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 5.0 .
.Sh AUTHORS
The
.Nm
driver and this manual page were written by
.An Hidetoshi Shimokawa .
.Sh BUGS
This driver emulates Ethernet in a very adhoc way and it does not reserve a
stream channel using an isochronous manager.
Note that this driver uses a protocol which is very different from RFC 2734
(IPv4 over IEEE 1394).

20
share/man/man4/fwip.4
View File

@ -57,16 +57,6 @@ This driver supports
as well if it is compiled with the
.Dv DEVICE_POLLING
option.
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 5.3 .
.Sh BUGS
This driver currently does not support the MCAP protocol for multicast
IP over FireWire.
Multicast packets are treated as broadcast packets which is sufficient
for most trivial uses of multicast.
.Sh SEE ALSO
.Xr arp 4 ,
.Xr firewire 4 ,
@ -77,6 +67,11 @@ for most trivial uses of multicast.
.Xr ifconfig 8 ,
.Xr kldload 8 ,
.Xr sysctl 8
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 5.3 .
.Sh AUTHORS
.An -nosplit
The
@ -85,3 +80,8 @@ driver and this manual page were written by
.An Doug Rabson ,
based on earlier work by
.An Hidetoshi Shimokawa .
.Sh BUGS
This driver currently does not support the MCAP protocol for multicast
IP over FireWire.
Multicast packets are treated as broadcast packets which is sufficient
for most trivial uses of multicast.

6
share/man/man4/gdb.4
View File

@ -576,9 +576,6 @@ This command is that answer.
It does nothing else except to print a warning
message to remind you to remove it again.
.El
.Sh AUTHORS
This man page was written by
.An "Greg Lehey" Aq grog@FreeBSD.org .
.Sh SEE ALSO
.Xr gdb 1 ,
.Xr ps 1 ,
@ -588,6 +585,9 @@ This man page was written by
.Xr dmesg 8 ,
.Xr fwcontrol 8 ,
.Xr kldload 8
.Sh AUTHORS
This man page was written by
.An "Greg Lehey" Aq grog@FreeBSD.org .
.Sh BUGS
The
.Xr gdb 1

10
share/man/man4/hatm.4
View File

@ -129,11 +129,6 @@ and
.Cm unassigned
(see
.Xr utopia 4 ) .
.Sh DIAGNOSTICS
.Bd -literal
hatm0: <FORE HE> mem 0xd2600000-0xd26fffff irq 9 at device 15.0 on pci2
hatm0: ForeRunnerHE 622, Rev. D, S/N 2949834, MAC=00:20:48:2d:02:ca
.Ed
.Sh ENVIRONMENT
When attaching to a device the driver checks the kernel environment
(see
@ -272,6 +267,11 @@ and
arguments the
.Nx
function has.
.Sh DIAGNOSTICS
.Bd -literal
hatm0: <FORE HE> mem 0xd2600000-0xd26fffff irq 9 at device 15.0 on pci2
hatm0: ForeRunnerHE 622, Rev. D, S/N 2949834, MAC=00:20:48:2d:02:ca
.Ed
.Sh SEE ALSO
.Xr natm 4 ,
.Xr natmip 4 ,

14
share/man/man4/hifn.4
View File

@ -94,13 +94,6 @@ See
.Pa http://www.soekris.com/ .
Contains a 7955 and supports symmetric and random number operations.
.El
.Sh BUGS
The 7751 chip starts out at initialization by only supporting compression.
A proprietary algorithm, which has been reverse engineered, is required to
unlock the cryptographic functionality of the chip.
It is possible for vendors to make boards which have a lock ID not known
to the driver, but all vendors currently just use the obvious ID which is
13 bytes of 0.
.Sh SEE ALSO
.Xr crypt 3 ,
.Xr crypto 4 ,
@ -126,3 +119,10 @@ The
.Nm
device driver was imported to
.Fx 5.0 .
.Sh BUGS
The 7751 chip starts out at initialization by only supporting compression.
A proprietary algorithm, which has been reverse engineered, is required to
unlock the cryptographic functionality of the chip.
It is possible for vendors to make boards which have a lock ID not known
to the driver, but all vendors currently just use the obvious ID which is
13 bytes of 0.

10
share/man/man4/hptmv.4
View File

@ -54,11 +54,6 @@ The
.Nm
driver only works on the i386 platform as it requires a binary blob object
from the manufacturer which they only supply for the i386 platform.
.Sh BUGS
The
.Nm
driver does not support manipulating the RAID from the OS, RAIDs need
to be set up from the on-board BIOS.
.Sh SEE ALSO
.Xr kld 4 ,
.Xr kldload 8 ,
@ -80,3 +75,8 @@ by
.An Scott Long .
This manual page was written by
.An David E. O'Brien .
.Sh BUGS
The
.Nm
driver does not support manipulating the RAID from the OS, RAIDs need
to be set up from the on-board BIOS.

10
share/man/man4/ifmib.4
View File

@ -182,6 +182,11 @@ the structure is a
.%D August 1994
.%O RFC 1650
.Re
.Sh HISTORY
The
.Nm
interface first appeared in
.Fx 2.2 .
.Sh BUGS
Many Ethernet-like interfaces do not yet support the Ethernet MIB;
the interfaces known to support it include
@ -189,8 +194,3 @@ the interfaces known to support it include
and
.Xr de 4 .
Regardless, all interfaces automatically support the generic MIB.
.Sh HISTORY
The
.Nm
interface first appeared in
.Fx 2.2 .

20
share/man/man4/isp.4
View File

@ -172,6 +172,16 @@ This is a driver debug level- meaningful from 0 through 7.
This is a driver target mode debug level- meaningful from 0 through
5.
.El
.Sh SEE ALSO
.Xr da 4 ,
.Xr intro 4 ,
.Xr ispfw 4 ,
.Xr sa 4 ,
.Xr scsi 4
.Sh AUTHORS
The
.Nm
driver was written by Matthew Jacob for NASA/Ames Research Center.
.Sh BUGS
The driver currently ignores some NVRAM settings.
.Pp
@ -192,13 +202,3 @@ To
unwedge the system, unplug and replug the fibre channel connection,
or otherwise cause a LIP (Loop Initialization Primitive sequence)-
this will kick the f/w into getting unstuck.
.Sh SEE ALSO
.Xr da 4 ,
.Xr intro 4 ,
.Xr ispfw 4 ,
.Xr sa 4 ,
.Xr scsi 4
.Sh AUTHORS
The
.Nm
driver was written by Matthew Jacob for NASA/Ames Research Center.

4
share/man/man4/joy.4
View File

@ -101,8 +101,8 @@ Time = 24.2e-6s + 0.011e-6s * R/Ohms
.It Pa /dev/joy?
joystick device files
.El
.Sh AUTHORS
.An Jean-Marc Zucconi Aq jmz@cabri.obs-besancon.fr
.Sh HISTORY
The joystick driver appeared in
.Fx 2.0.5 .
.Sh AUTHORS
.An Jean-Marc Zucconi Aq jmz@cabri.obs-besancon.fr

32
share/man/man4/kld.4
View File

@ -131,6 +131,22 @@ example source code implementing a sample kld module
.Xr kldstat 8 ,
.Xr kldunload 8 ,
.Xr sysctl 8
.Sh HISTORY
The
.Nm
facility appeared in
.Fx 3.0
and was designed as a replacement for the
.Xr lkm 4
facility, which was similar in functionality to the loadable kernel modules
facility provided by
.Tn SunOS
4.1.3.
.Sh AUTHORS
The
.Nm
facility was originally implemented by
.An Doug Rabson Aq dfr@FreeBSD.org .
.Sh BUGS
If a module B, is dependent on another module A, but is not compiled with
module A as a dependency, then
@ -157,19 +173,3 @@ for any error encountered while loading a module.
When system internal interfaces change, old modules often cannot
detect this, and such modules when loaded will often cause crashes or
mysterious failures.
.Sh HISTORY
The
.Nm
facility appeared in
.Fx 3.0
and was designed as a replacement for the
.Xr lkm 4
facility, which was similar in functionality to the loadable kernel modules
facility provided by
.Tn SunOS
4.1.3.
.Sh AUTHORS
The
.Nm
facility was originally implemented by
.An Doug Rabson Aq dfr@FreeBSD.org .

8
share/man/man4/led.4
View File

@ -145,6 +145,10 @@ becomes
.El
.Pp
The sequence is repeated after a one second pause.
.Sh FILES
.Bl -tag -width ".Pa /dev/led/*"
.It Pa /dev/led/*
.El
.Sh EXAMPLES
A
.Sq Li d12
@ -161,10 +165,6 @@ flashes
.Bd -literal
/usr/games/morse -l "Soekris rocks" > /dev/led/error
.Ed
.Sh FILES
.Bl -tag -width ".Pa /dev/led/*"
.It Pa /dev/led/*
.El
.Sh SEE ALSO
.Xr morse 6
.Sh HISTORY

10
share/man/man4/lpt.4
View File

@ -75,6 +75,11 @@ In order to retrieve printer info from /dev/lpt0, just apply the
command to the device.
If the printer supports IEEE1284 nibble mode and has
data to send to the host, you'll get it.
.Sh FILES
.Bl -tag -width Pa -compact
.It Pa /dev/lpt0
first parallel port driver
.El
.Sh SEE ALSO
.Xr ppbus 4 ,
.Xr ppc 4 ,
@ -82,11 +87,6 @@ data to send to the host, you'll get it.
.Sh HISTORY
This driver replaces the functionality of the lpa
driver, which is now defunct.
.Sh FILES
.Bl -tag -width Pa -compact
.It Pa /dev/lpt0
first parallel port driver
.El
.Sh BUGS
There are lots of them, especially in cheap parallel port implementations.
.Pp

6
share/man/man4/man4.alpha/osf1.4
View File

@ -83,6 +83,9 @@ see
.It Pa /compat/osf1
minimal OSF1 run-time environment
.El
.Sh HISTORY
OSF/1 ABI support first appeared in
.Fx 4.0 .
.Sh BUGS
We cannot run OSF/1 applications which rely on the
.Xr pthread 3
@ -90,6 +93,3 @@ API, such as the JDK.
OSF/1's pthreads library uses Mach system calls.
Mach system calls would be very difficult to support in
.Fx .
.Sh HISTORY
OSF/1 ABI support first appeared in
.Fx 4.0 .

12
share/man/man4/man4.i386/aic.4
View File

@ -67,12 +67,6 @@ Adaptec AHA-1030B, AHA-1030P (PC98)
.It
NEC PC-9801-100 (PC98)
.El
.Sh BUGS
The driver does not work well with multiple devices on the SCSI bus.
The driver works well with devices like CDROMs and Tape drives.
The driver works not so well with disk drives.
The PC Card version appears to work better than the ISA version, but
that may be due to differing levels of testing of the devices.
.Sh SEE ALSO
.Xr aha 4 ,
.Xr ahb 4 ,
@ -82,3 +76,9 @@ that may be due to differing levels of testing of the devices.
.Xr da 4 ,
.Xr intro 4 ,
.Xr sa 4
.Sh BUGS
The driver does not work well with multiple devices on the SCSI bus.
The driver works well with devices like CDROMs and Tape drives.
The driver works not so well with disk drives.
The PC Card version appears to work better than the ISA version, but
that may be due to differing levels of testing of the devices.

10
share/man/man4/man4.i386/apm.4
View File

@ -117,6 +117,11 @@ polls APM events and handles the following events.
.It Dv "PMEV_UPDATETIME " No "adjust clock " "update time"
.El
.El
.Sh SEE ALSO
.Xr apm 8 ,
.Xr zzz 8
.Sh AUTHORS
Tatsumi Hosokawa <hosokawa@jp.FreeBSD.org>
.Sh BUGS
WARNING!
Many, if not most, of the implementations of APM-bios in laptops
@ -151,8 +156,3 @@ or
.Pp
Disk spin-down, LCD backlight control, and power on demand have not
been supported on the current version.
.Sh SEE ALSO
.Xr apm 8 ,
.Xr zzz 8
.Sh AUTHORS
Tatsumi Hosokawa <hosokawa@jp.FreeBSD.org>

30
share/man/man4/man4.i386/ar.4
View File

@ -83,12 +83,6 @@ Connecting to this hook enables the transmission of raw HDLC frames.
The node will have the same name as the device with ``sync_''
prepended, e.g.,
.Dv sync_ar0 .
.Sh DIAGNOSTICS
.Bl -diag
.It "ar%d: Warning illegal interrupt %d."
The card cannot use the specified interrupt.
Choose a different one.
.El
.Sh FILES
.Bl -tag -width /sys/i386/isa/ic/hd64570.h -compact
.It Pa /sys/i386/isa/ic/hd64570.h
@ -97,15 +91,12 @@ Choose a different one.
.It Pa /sys/i386/isa/if_ar.h
.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
may need tweaks to the clock selection code.
.Pp
The code can probably stand some optimizing.
.Pp
Please report bugs to
.Aq jhay@FreeBSD.org .
.Sh DIAGNOSTICS
.Bl -diag
.It "ar%d: Warning illegal interrupt %d."
The card cannot use the specified interrupt.
Choose a different one.
.El
.Sh SEE ALSO
.Xr cx 4 ,
.Xr netgraph 4 ,
@ -125,3 +116,12 @@ device driver was written by
.An John Hay Aq jhay@FreeBSD.org .
Netgraph support was added by
.An Julian Elischer Aq julian@FreeBSD.org .
.Sh BUGS
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.
.Pp
Please report bugs to
.Aq jhay@FreeBSD.org .

14
share/man/man4/man4.i386/el.4
View File

@ -50,13 +50,6 @@ The valid I/O ports are in the range 0x280-0x3f0.
The
.Nm
driver supports the 3Com 3c501 8bit ISA Ethernet card.
.Sh BUGS
The driver assumes the card is configured for the same IRQ as the kernel.
No probing or checking is done to determine if this is the case.
.Pp
Does not currently support DMA.
.Pp
Does not currently support multicasts.
.Sh SEE ALSO
.Xr ed 4 ,
.Xr ep 4 ,
@ -65,3 +58,10 @@ Does not currently support multicasts.
.Xr le 4 ,
.Xr ng_ether 4 ,
.Xr ifconfig 8
.Sh BUGS
The driver assumes the card is configured for the same IRQ as the kernel.
No probing or checking is done to determine if this is the case.
.Pp
Does not currently support DMA.
.Pp
Does not currently support multicasts.

6
share/man/man4/man4.i386/ep.4
View File

@ -149,9 +149,9 @@ Erase the pencil mark and reboot.
.Xr ng_ether 4 ,
.Xr vx 4 ,
.Xr ifconfig 8
.Sh BUGS
Support for the 3Com 3C1 is not working.
Support for the 3CCFEM556 Fast Ethernet cards has not been tested.
.Sh STANDARDS
are great.
There's so many to choose from.
.Sh BUGS
Support for the 3Com 3C1 is not working.
Support for the 3CCFEM556 Fast Ethernet cards has not been tested.

4
share/man/man4/man4.i386/ex.4
View File

@ -69,8 +69,6 @@ interrupt than the one specified in the kernel configuration file.
.It "ex%d: invalid IRQ."
The device probe detected an invalid IRQ setting.
.El
.Sh BUGS
Currently the driver does not support multicast.
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,
@ -89,3 +87,5 @@ device driver was written by
.An Javier Mart\('in Rueda .
This manual page was written by
.An David E. O'Brien .
.Sh BUGS
Currently the driver does not support multicast.

46
share/man/man4/man4.i386/fe.4
View File

@ -293,26 +293,11 @@ It requires the PC card (PCMCIA) support package.
.Xr ng_ether 4 ,
.Xr ifconfig 8 ,
.Xr pccardd 8
.Sh BUGS
Following are major known bugs:
.Pp
Statistics on the number of collisions maintained by the
.Sh HISTORY
The
.Nm
driver is not accurate;
the
.Fl i
option of
.Xr netstat 1
shows slightly less value than true number of collisions.
.Pp
More mbuf clusters are used than expected.
The packet receive routine has an intended violation
against the mbuf cluster allocation policy.
The unnecessarily allocated clusters are freed within short lifetime,
and it will not affect long term kernel memory usage.
.Pp
Although XNS and IPX support is included in the driver,
it has never been tested and it is expected to have a lot of bugs.
driver appeared in
.Fx 2.0.5 .
.Sh AUTHORS, COPYRIGHT AND DISCLAIMER
The
.Nm
@ -354,8 +339,23 @@ LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
DOCUMENT AND THE ASSOCIATED SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
.Sh HISTORY
The
.Sh BUGS
Following are major known bugs:
.Pp
Statistics on the number of collisions maintained by the
.Nm
driver appeared in
.Fx 2.0.5 .
driver is not accurate;
the
.Fl i
option of
.Xr netstat 1
shows slightly less value than true number of collisions.
.Pp
More mbuf clusters are used than expected.
The packet receive routine has an intended violation
against the mbuf cluster allocation policy.
The unnecessarily allocated clusters are freed within short lifetime,
and it will not affect long term kernel memory usage.
.Pp
Although XNS and IPX support is included in the driver,
it has never been tested and it is expected to have a lot of bugs.

6
share/man/man4/man4.i386/lnc.4
View File

@ -131,9 +131,6 @@ is the same one the card is configured for.
.It "lnc%d: Transmit buffer error -- Resetting"
.It "lnc%d: Transmit underflow error -- Resetting"
.El
.Sh BUGS
This driver has the potential of being the most verbose of any of the
Ethernet device drivers.
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,
@ -154,3 +151,6 @@ Support for the AMD PCHome phone-line based network added by
.An Robert Watson .
This manual page was written by
.An David E. O'Brien .
.Sh BUGS
This driver has the potential of being the most verbose of any of the
Ethernet device drivers.

6
share/man/man4/man4.i386/longrun.4
View File

@ -56,12 +56,12 @@ To set LongRun mode to performance oriented variable frequency mode
(less power savings):
.Pp
.Dl "# sysctl hw.crusoe.longrun=2"
.Sh HISTORY
The Transmeta(TM) Crusoe(TM) LongRun(TM) support first appeared in
.Fx 4.4 .
.Sh AUTHORS
.An -nosplit
LongRun support and this manual page were written by
.An Tamotsu HATTORI Aq athlete@kta.att.ne.jp
and
.An Mitsuru IWASAKI Aq iwasaki@FreeBSD.org .
.Sh HISTORY
The Transmeta(TM) Crusoe(TM) LongRun(TM) support first appeared in
.Fx 4.4 .

10
share/man/man4/man4.i386/mcd.4
View File

@ -150,6 +150,11 @@ supported, the only interrupts that the board generates are those that
aren't supported by the driver anyway.
.Sh SEE ALSO
.In sys/cdio.h
.Sh HISTORY
An
.Nm
driver appeared in
.Fx 1.0 .
.Sh AUTHORS
.An -nosplit
The driver was written by
@ -162,8 +167,3 @@ Changes were provided by
.An Andrew A. Chernov ,
and
.An Jordan K. Hubbard .
.Sh HISTORY
An
.Nm
driver appeared in
.Fx 1.0 .

12
share/man/man4/man4.i386/pnp.4
View File

@ -76,6 +76,12 @@ no provision for manual override.
.%T ``Clarifications to the Plug and Play ISA Specification, Version 1.0a''
.%D December 10, 1994
.Re
.Sh HISTORY
The
.Nm
driver first appeared in
.Fx 2.2.5 .
It has been substantially updated in subsequent versions.
.Sh AUTHORS
PnP support was originally written
for
@ -84,9 +90,3 @@ by
.An Luigi Rizzo ,
based on initial work done by
.An Sujal Patel .
.Sh HISTORY
The
.Nm
driver first appeared in
.Fx 2.2.5 .
It has been substantially updated in subsequent versions.

10
share/man/man4/man4.i386/scd.4
View File

@ -59,6 +59,11 @@ accesses the raw device.
.El
.Sh SEE ALSO
.Pa /sys/i386/isa/scd.c
.Sh HISTORY
The
.Nm
driver first appeared in
.Fx 2.0.5 .
.Sh AUTHORS
.An -nosplit
The driver was written by
@ -67,8 +72,3 @@ with code contributed by
.An Holger Veit
and
.An Brian Moore .
.Sh HISTORY
The
.Nm
driver first appeared in
.Fx 2.0.5 .

34
share/man/man4/man4.i386/spkr.4
View File

@ -209,6 +209,23 @@ BASIC.)
.Pp
Whitespace in play strings is simply skipped and may be used to separate
melody sections.
.Sh FILES
.Bl -tag -width /dev/speakerxx
.It Pa /dev/speaker
speaker device file
.El
.Sh SEE ALSO
.Xr spkrtest 8
.Sh HISTORY
The
.Nm
device appeared in
.Fx 1.0 .
.Sh AUTHORS
.An Eric S. Raymond Aq esr@snark.thyrsus.com
June 1990
.Sh "PORTED BY"
.An Andrew A. Chernov Aq ache@astral.msk.su
.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
@ -230,20 +247,3 @@ compatibility.
In play strings which are very long (longer than your system's physical I/O
blocks) note suffixes or numbers may occasionally be parsed incorrectly due
to crossing a block boundary.
.Sh FILES
.Bl -tag -width /dev/speakerxx
.It Pa /dev/speaker
speaker device file
.El
.Sh SEE ALSO
.Xr spkrtest 8
.Sh AUTHORS
.An Eric S. Raymond Aq esr@snark.thyrsus.com
June 1990
.Sh "PORTED BY"
.An Andrew A. Chernov Aq ache@astral.msk.su
.Sh HISTORY
The
.Nm
device appeared in
.Fx 1.0 .

24
share/man/man4/man4.i386/sr.4
View File

@ -122,12 +122,6 @@ Connecting to this hook enables the transmission of raw HDLC frames.
The node will have the same name as the device with ``sync_''
prepended, e.g.,
.Dv sync_sr0 .
.Sh DIAGNOSTICS
.Bl -diag
.It "sr%d: Warning illegal interrupt %d."
The card cannot use the specified interrupt.
Choose a different one.
.El
.Sh FILES
.Bl -tag -width /sys/i386/isa/ic/hd64570.h -compact
.It Pa /sys/i386/isa/ic/hd64570.h
@ -136,12 +130,12 @@ Choose a different one.
.It Pa /sys/i386/isa/if_sr.h
.It Pa /sys/pci/if_sr_p.c
.El
.Sh BUGS
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.
.Sh DIAGNOSTICS
.Bl -diag
.It "sr%d: Warning illegal interrupt %d."
The card cannot use the specified interrupt.
Choose a different one.
.El
.Sh SEE ALSO
.Xr ar 4 ,
.Xr cx 4 ,
@ -157,3 +151,9 @@ device driver was written by
.Pp
Netgraph support was added by
.An Julian Elischer Aq julian@FreeBSD.org .
.Sh BUGS
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.

16
share/man/man4/man4.i386/streams.4
View File

@ -60,14 +60,6 @@ emulation is only provided as a service to support ABI requirements in
the SVR4 environment which
.Xr svr4 4
needs to present to client binaries.
.Sh BUGS
This whole interface is a crude hack to produce STREAMS semantics
through emulation over sockets.
.Pp
Programmers who hope to be able to use this interface to provide
SVR4 STREAMS services to
.Bx
applications will be sorely disappointed.
.Sh SEE ALSO
.Xr svr4 4
.Sh HISTORY
@ -76,3 +68,11 @@ System V Release 4 ABI support first appeared in
The ABI was ported from an equivalent facility present in
.Nx 1.3
written by Christos Zoulas.
.Sh BUGS
This whole interface is a crude hack to produce STREAMS semantics
through emulation over sockets.
.Pp
Programmers who hope to be able to use this interface to provide
SVR4 STREAMS services to
.Bx
applications will be sorely disappointed.

38
share/man/man4/man4.i386/svr4.4
View File

@ -155,6 +155,25 @@ calls are executed.
The subset of STREAMS functionality which is provided is small, probably
little more than what is required to enable programs on the Solaris CD
sets to run.
.Sh FILES
.Bl -tag -width /sys/compat/svr4/syscalls.master -compact
.It Pa /compat/svr4
minimal SVR4 run-time environment
.It Pa /sys/compat/svr4/syscalls.master
mappings between SVR4 syscalls and
.Nm
module entrypoints.
.El
.Sh SEE ALSO
.Xr brandelf 1 ,
.Xr streams 4 ,
.Xr elf 5
.Sh HISTORY
System V Release 4 ABI support first appeared in
.Fx 4.0 .
The ABI was ported from an equivalent facility present in
.Nx 1.3
written by Christos Zoulas.
.Sh BUGS
Emulation of signal handlers is buggy.
.Pp
@ -195,22 +214,3 @@ variables could set the
.Dq personality
the environment should present to
client applications.
.Sh FILES
.Bl -tag -width /sys/compat/svr4/syscalls.master -compact
.It Pa /compat/svr4
minimal SVR4 run-time environment
.It Pa /sys/compat/svr4/syscalls.master
mappings between SVR4 syscalls and
.Nm
module entrypoints.
.El
.Sh SEE ALSO
.Xr brandelf 1 ,
.Xr streams 4 ,
.Xr elf 5
.Sh HISTORY
System V Release 4 ABI support first appeared in
.Fx 4.0 .
The ABI was ported from an equivalent facility present in
.Nx 1.3
written by Christos Zoulas.

20
share/man/man4/man4.i386/vx.4
View File

@ -94,16 +94,6 @@ mostly in spurious warnings.
The performance of this driver is somewhat limited by the fact that it uses
only polled-mode I/O and does not make use of the bus-mastering capability
of the cards.
.Sh BUGS
The
.Nm
driver is known not to reset the adapter correctly following a warm boot
on some systems.
.Pp
The
.Nm
driver has not been exhaustively tested with all the models of cards that it
claims to support.
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,
@ -126,3 +116,13 @@ device driver and this manual page were written by
based on the work of
.An Herb Peyerl
and with the assistance of numerous others.
.Sh BUGS
The
.Nm
driver is known not to reset the adapter correctly following a warm boot
on some systems.
.Pp
The
.Nm
driver has not been exhaustively tested with all the models of cards that it
claims to support.

12
share/man/man4/mem.4
View File

@ -186,12 +186,6 @@ base/length supplied.
An attempt to remove a range failed because the range is permanently
enabled.
.El
.Sh BUGS
Busy range attributes are not yet managed correctly.
.Pp
This device is required for all users of
.Xr kvm 3
to operate.
.Sh FILES
.Bl -tag -width /dev/kmem -compact
.It Pa /dev/mem
@ -209,3 +203,9 @@ files appeared in
.At v6 .
The ioctl interface for memory range attributes was added in
.Fx 3.2 .
.Sh BUGS
Busy range attributes are not yet managed correctly.
.Pp
This device is required for all users of
.Xr kvm 3
to operate.

6
share/man/man4/meteor.4
View File

@ -865,10 +865,10 @@ will be set to:
invalid meteor_counts structure pointer.
.El
.El
.Sh AUTHORS
.An Jim Lowe Aq james@miller.cs.uwm.edu ,
.An Mark Tinguely Aq tinguely@plains.nodak.edu
.Sh BUGS
The
.Nm
driver no longer works at all.
.Sh AUTHORS
.An Jim Lowe Aq james@miller.cs.uwm.edu ,
.An Mark Tinguely Aq tinguely@plains.nodak.edu

14
share/man/man4/mlx.4
View File

@ -221,13 +221,6 @@ or in the driver.
.El
.Sh SEE ALSO
.Xr mlxcontrol 8
.Sh BUGS
The driver does not yet support EISA adapters.
The DEC KZPSC has insufficient flash ROM to hold any reasonably recent firmware.
This has caused problems for this driver.
.Pp
The driver does not yet support the version 6.x firmware as found in the
AcceleRAID 352 and eXtremeRAID 2000 and 3000 products.
.Sh AUTHORS
.An -nosplit
The
@ -242,3 +235,10 @@ This manual page was written by
and
.An Michael Smith
.Aq msmith@FreeBSD.org .
.Sh BUGS
The driver does not yet support EISA adapters.
The DEC KZPSC has insufficient flash ROM to hold any reasonably recent firmware.
This has caused problems for this driver.
.Pp
The driver does not yet support the version 6.x firmware as found in the
AcceleRAID 352 and eXtremeRAID 2000 and 3000 products.

8
share/man/man4/mly.4
View File

@ -243,10 +243,6 @@ The driver does not attempt to name the enclosures.
.Pp
These events report controller status changes.
.El
.Sh BUGS
The driver does not yet provide an external management interface.
.Pp
Enclosures are not named or otherwise identified in event messages.
.Sh AUTHORS
.An -nosplit
The
@ -258,3 +254,7 @@ driver was written by
This manual page was written by
.An Michael Smith
.Aq msmith@FreeBSD.org .
.Sh BUGS
The driver does not yet provide an external management interface.
.Pp
Enclosures are not named or otherwise identified in event messages.

22
share/man/man4/ng_bpf.4
View File

@ -175,6 +175,17 @@ ngctl msg ${NODEPATH} setprogram { thisHook=\\"${INHOOK}\\" \\
ifNotMatch=\\"${NOTMATCHHOOK}\\" \\
${BPFPROG} } }
.Ed
.Sh SEE ALSO
.Xr bpf 4 ,
.Xr netgraph 4 ,
.Xr ngctl 8
.Sh HISTORY
The
.Nm
node type was implemented in
.Fx 4.0 .
.Sh AUTHORS
.An Archie Cobbs Aq archie@FreeBSD.org
.Sh BUGS
When built as a loadable kernel module, this module includes the file
.Pa net/bpf_filter.c .
@ -183,14 +194,3 @@ Although loading the module should fail if
already exists in the kernel, currently it does not, and the duplicate
copies of the file do not interfere.
However, this may change in the future.
.Sh HISTORY
The
.Nm
node type was implemented in
.Fx 4.0 .
.Sh SEE ALSO
.Xr bpf 4 ,
.Xr netgraph 4 ,
.Xr ngctl 8
.Sh AUTHORS
.An Archie Cobbs Aq archie@FreeBSD.org

8
share/man/man4/ng_bt3c.4
View File

@ -124,10 +124,6 @@ Download card firmware.
.El
.Sh SHUTDOWN
This node shuts down when the corresponding card is un-plugged.
.Sh BUGS
The driver is based on information obtained from
.An Jose Orlando Pereira Aq jop@di.uminho.pt
and disassembled the W2K driver.
.Sh SEE ALSO
.Xr cardbus 4 ,
.Xr netgraph 4 ,
@ -145,3 +141,7 @@ node type was implemented in
.Fx 5.0 .
.Sh AUTHORS
.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com
.Sh BUGS
The driver is based on information obtained from
.An Jose Orlando Pereira Aq jop@di.uminho.pt
and disassembled the W2K driver.

6
share/man/man4/ng_btsocket.4
View File

@ -333,9 +333,6 @@ unique) and always accept hook connection requests.
These node types support the generic control messages.
.Sh SHUTDOWN
These nodes are persistent and cannot be shut down.
.Sh BUGS
Most likely.
Please report if found.
.Sh SEE ALSO
.Xr btsockstat 1 ,
.Xr socket 2 ,
@ -352,3 +349,6 @@ module was implemented in
.Fx 5.0 .
.Sh AUTHORS
.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com
.Sh BUGS
Most likely.
Please report if found.

10
share/man/man4/ng_cisco.4
View File

@ -157,11 +157,6 @@ struct ngciscostat {
This node shuts down upon receipt of a
.Dv NGM_SHUTDOWN
control message, or when all hooks have been disconnected.
.Sh BUGS
Not all of the functionality has been implemented.
For example,
the node does not support querying the remote end for its IP address
and netmask.
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr ng_iface 4 ,
@ -182,3 +177,8 @@ node type was implemented in
.Sh AUTHORS
.An Julian Elischer Aq julian@FreeBSD.org ,
.An Archie Cobbs Aq archie@FreeBSD.org
.Sh BUGS
Not all of the functionality has been implemented.
For example,
the node does not support querying the remote end for its IP address
and netmask.

20
share/man/man4/ng_ether.4
View File

@ -204,6 +204,16 @@ tracing packet flow, statistics, etc.:
ngctl mkpeer fxp0: tee lower right
ngctl connect fxp0: lower upper left
.Ed
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netgraph 4 ,
.Xr netintro 4 ,
.Xr ifconfig 8 ,
.Xr ngctl 8 ,
.Xr nghook 8
.Sh AUTHORS
.An Julian Elischer Aq julian@FreeBSD.org
.An Archie Cobbs Aq archie@FreeBSD.org
.Sh BUGS
The automatic KLD module loading mechanism that works for most
other Netgraph node types does not work for the
@ -217,13 +227,3 @@ Therefore, if the KLD is not statically compiled into the kernel,
it is necessary to load the KLD manually in order to bring the
.Nm ether
nodes into existence.
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netgraph 4 ,
.Xr netintro 4 ,
.Xr ifconfig 8 ,
.Xr ngctl 8 ,
.Xr nghook 8
.Sh AUTHORS
.An Julian Elischer Aq julian@FreeBSD.org
.An Archie Cobbs Aq archie@FreeBSD.org

18
share/man/man4/ng_frame_relay.4
View File

@ -78,15 +78,6 @@ This node type supports only the generic control messages.
This node shuts down upon receipt of a
.Dv NGM_SHUTDOWN
control message, or when all hooks have been disconnected.
.Sh BUGS
Technically, frames on DLCI X should not be transmitted to the switch
until the LMI protocol entity on both ends has configured DLCI X as active.
The
.Nm
node type ignores this restriction, and will always pass data received
on a DLCI hook to
.Dv downstream .
Instead, it should query the LMI node first.
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr ng_lmi 4 ,
@ -98,3 +89,12 @@ node type was implemented in
.Fx 4.0 .
.Sh AUTHORS
.An Julian Elischer Aq julian@FreeBSD.org
.Sh BUGS
Technically, frames on DLCI X should not be transmitted to the switch
until the LMI protocol entity on both ends has configured DLCI X as active.
The
.Nm
node type ignores this restriction, and will always pass data received
on a DLCI hook to
.Dv downstream .
Instead, it should query the LMI node first.

10
share/man/man4/ng_h4.4
View File

@ -104,11 +104,6 @@ Reset all statistic counters to zero.
.Sh SHUTDOWN
This node shuts down when the corresponding device is closed
(or the line discipline is uninstalled on the device).
.Sh BUGS
This node still uses
.Xr spltty 9
to lock tty layer.
This is wrong.
.Sh SEE ALSO
.Xr ioctl 2 ,
.Xr netgraph 4 ,
@ -121,3 +116,8 @@ node type was implemented in
.Fx 5.0 .
.Sh AUTHORS
.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com
.Sh BUGS
This node still uses
.Xr spltty 9
to lock tty layer.
This is wrong.

6
share/man/man4/ng_hci.4
View File

@ -371,9 +371,6 @@ This node shuts down upon receipt of a
.Dv NGM_SHUTDOWN
control message, or
when all hooks have been disconnected.
.Sh BUGS
Most likely.
Please report if found.
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr hccontrol 8 ,
@ -385,3 +382,6 @@ node type was implemented in
.Fx 5.0 .
.Sh AUTHORS
.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com
.Sh BUGS
Most likely.
Please report if found.

6
share/man/man4/ng_l2cap.4
View File

@ -406,9 +406,6 @@ This node shuts down upon receipt of an
.Dv NGM_SHUTDOWN
control message, or
when all hooks have been disconnected.
.Sh BUGS
Most likely.
Please report if found.
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr l2control 8 ,
@ -421,3 +418,6 @@ node type was implemented in
.Fx 5.0 .
.Sh AUTHORS
.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com
.Sh BUGS
Most likely.
Please report if found.

10
share/man/man4/ng_mppc.4
View File

@ -160,11 +160,6 @@ These files must be obtained elsewhere and added to the kernel
sources before this node type will compile with the
.Dv NETGRAPH_MPPC_COMPRESSION
option.
.Sh BUGS
In PPP, encryption should be handled by the Encryption Control Protocol (ECP)
rather than CCP.
However, Microsoft combined both compression and encryption into their
``compression'' algorithm, which is confusing.
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr ng_ppp 4 ,
@ -192,3 +187,8 @@ However, Microsoft combined both compression and encryption into their
.Re
.Sh AUTHORS
.An Archie Cobbs Aq archie@FreeBSD.org
.Sh BUGS
In PPP, encryption should be handled by the Encryption Control Protocol (ECP)
rather than CCP.
However, Microsoft combined both compression and encryption into their
``compression'' algorithm, which is confusing.

16
share/man/man4/ng_netflow.4
View File

@ -222,14 +222,6 @@ node in this example is connected to
msg netflow:export connect inet/10.0.0.1:4444
SEQ
.Ed
.Sh BUGS
The
.Nm
node type does not fill in AS numbers.
This is due to the lack of necessary information in the kernel routing table.
However, this information can be injected into the kernel from a routing daemon
such as GNU Zebra.
This functionality may become available in future releases.
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr ng_ksocket 4 ,
@ -247,3 +239,11 @@ based on
.Nm ng_ipacct
written by
.An Roman V. Palagin Aq romanp@unshadow.net .
.Sh BUGS
The
.Nm
node type does not fill in AS numbers.
This is due to the lack of necessary information in the kernel routing table.
However, this information can be injected into the kernel from a routing daemon
such as GNU Zebra.
This functionality may become available in future releases.

6
share/man/man4/ng_one2many.4
View File

@ -245,9 +245,6 @@ With a similar setup on a peer machine (using the address
192.168.1.2), a point-to-point
Ethernet connection with four times normal bandwidth is
achieved.
.Sh BUGS
More transmit and link failure algorithms should be supported.
A good candidate is Cisco's Etherchannel.
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr ng_bridge 4 ,
@ -270,3 +267,6 @@ netgraph node (with round-robin algorithm) was written by
The all algorithm was added by
.An Rogier R. Mulhuijzen
.Aq drwilco@drwilco.net .
.Sh BUGS
More transmit and link failure algorithms should be supported.
A good candidate is Cisco's Etherchannel.

10
share/man/man4/ng_pptpgre.4
View File

@ -160,11 +160,6 @@ control message, or when both hooks have been disconnected.
.%T "Generic Routing Encapsulation over IPv4 networks"
.%O RFC 1702
.Re
.Sh BUGS
The node should not expect incoming GRE packets to have an IP header.
This behavior is inherited from the (converse) behavior of raw IP sockets.
An intermediate node that strips IP headers in one direction
should be used instead.
.Sh HISTORY
The
.Nm
@ -172,3 +167,8 @@ node type was implemented in
.Fx 4.0 .
.Sh AUTHORS
.An Archie Cobbs Aq archie@FreeBSD.org
.Sh BUGS
The node should not expect incoming GRE packets to have an IP header.
This behavior is inherited from the (converse) behavior of raw IP sockets.
An intermediate node that strips IP headers in one direction
should be used instead.

4
share/man/man4/ng_rfc1490.4
View File

@ -113,8 +113,6 @@ This command returns current encapsulation method on the node.
This node shuts down upon receipt of a
.Dv NGM_SHUTDOWN
control message, or when all hooks have been disconnected.
.Sh BUGS
Not all of RFC 1490 is implemented.
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr ng_frame_relay 4 ,
@ -140,3 +138,5 @@ node type was implemented in
.Fx 4.0 .
.Sh AUTHORS
.An Julian Elischer Aq julian@FreeBSD.org
.Sh BUGS
Not all of RFC 1490 is implemented.

16
share/man/man4/ng_socket.4
View File

@ -166,14 +166,6 @@ If the
.Dv NGM_SOCK_CMD_NOLINGER
message has been received, closure of the last hook will also initiate
a shutdown of the node.
.Sh BUGS
It is not possible to reject the connection of a hook, though any
data received on that hook can certainly be ignored.
.Pp
The controlling process is not notified of all events that an in-kernel node
would be notified of, e.g.\& a new hook, or hook removal.
Some node-initiated messages should be defined for this purpose (to be
sent up the control socket).
.Sh SEE ALSO
.Xr socket 2 ,
.Xr netgraph 3 ,
@ -187,3 +179,11 @@ node type was implemented in
.Fx 4.0 .
.Sh AUTHORS
.An Julian Elischer Aq julian@FreeBSD.org
.Sh BUGS
It is not possible to reject the connection of a hook, though any
data received on that hook can certainly be ignored.
.Pp
The controlling process is not notified of all events that an in-kernel node
would be notified of, e.g.\& a new hook, or hook removal.
Some node-initiated messages should be defined for this purpose (to be
sent up the control socket).

128
share/man/man4/ng_source.4
View File

@ -179,6 +179,70 @@ This node shuts down upon receipt of a
control message, or when the
.Dv output
hook has been disconnected.
.Sh IMPLEMENTATION NOTES
.No ( Fx 4.4
version)
.Pp
The use of
.Xr splimp 9
around the
.Dv NG_SEND_DATA
loop is important.
Without it,
the time taken by a single invocation of
.Fn ng_source_intr
becomes too
large and the packet rate drops.
Probably due to the NIC starting to
send the packets right away.
.Pp
Copying all the packets in one loop and sending them in another inside
of
.Fn ng_source_send
is done to limit how long we are at
.Xr splimp 9
and gave
minor packet rate increases (~5% at 256 byte packets).
However note
that if there are errors in the send loop, the remaining copied packets
are simply freed and discarded; thus we skip those packets, and ordering
of the input queue to the output is not maintained.
.Pp
Calling
.Xr timeout 9
at the end of
.Fn ng_source_intr
instead of near the
beginning is done to help avoid CPU starvation if
.Fn ng_source_intr
takes a long time to run.
.Pp
The use of
.Xr splnet 9
may be sub-optimal.
It is used for synchronization
within the node (e.g., data received on the
.Dv input
hook while
.Fn ng_source_send
is active) but we do not want to hold it too long and risk
starving the NIC.
.Pp
For clarity and simplicity, debugging messages and instrumentation code
has been removed.
On i386 one can include
.In machine/cpufunc.h
to have access to the
.Fn rdtsc
function to read the instruction counter at the
start and end of
.Fn ng_source_intr .
Also useful is the packet count returned by
.Fn ng_source_send .
Do not try to report such things from within
.Fn ng_source_intr ,
instead include the values in
.Va sc->stats .
.Sh EXAMPLES
Attach the node to an
.Xr ng_ether 4
@ -270,70 +334,6 @@ command:
date -r 1035305880
Tue Oct 22 12:58:00 EDT 2002
.Ed
.Sh IMPLEMENTATION NOTES
.No ( Fx 4.4
version)
.Pp
The use of
.Xr splimp 9
around the
.Dv NG_SEND_DATA
loop is important.
Without it,
the time taken by a single invocation of
.Fn ng_source_intr
becomes too
large and the packet rate drops.
Probably due to the NIC starting to
send the packets right away.
.Pp
Copying all the packets in one loop and sending them in another inside
of
.Fn ng_source_send
is done to limit how long we are at
.Xr splimp 9
and gave
minor packet rate increases (~5% at 256 byte packets).
However note
that if there are errors in the send loop, the remaining copied packets
are simply freed and discarded; thus we skip those packets, and ordering
of the input queue to the output is not maintained.
.Pp
Calling
.Xr timeout 9
at the end of
.Fn ng_source_intr
instead of near the
beginning is done to help avoid CPU starvation if
.Fn ng_source_intr
takes a long time to run.
.Pp
The use of
.Xr splnet 9
may be sub-optimal.
It is used for synchronization
within the node (e.g., data received on the
.Dv input
hook while
.Fn ng_source_send
is active) but we do not want to hold it too long and risk
starving the NIC.
.Pp
For clarity and simplicity, debugging messages and instrumentation code
has been removed.
On i386 one can include
.In machine/cpufunc.h
to have access to the
.Fn rdtsc
function to read the instruction counter at the
start and end of
.Fn ng_source_intr .
Also useful is the packet count returned by
.Fn ng_source_send .
Do not try to report such things from within
.Fn ng_source_intr ,
instead include the values in
.Va sc->stats .
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr ng_echo 4 ,

18
share/man/man4/ng_tty.4
View File

@ -118,15 +118,6 @@ The
.Dv NGM_SHUTDOWN
control message is not valid, and always returns the error
.Er EOPNOTSUPP .
.Sh BUGS
The serial driver code also has a notion of a
.Dq hot character .
Unfortunately, this value is statically defined in terms of the
line discipline and cannot be changed.
Therefore, if a hot character other than 0x7e (the default) is set for the
.Nm
node, the node has no way to convey this information to the
serial driver, and sub-optimal performance may result.
.Sh SEE ALSO
.Xr ioctl 2 ,
.Xr netgraph 4 ,
@ -140,3 +131,12 @@ node type was implemented in
.Fx 4.0 .
.Sh AUTHORS
.An Archie Cobbs Aq archie@FreeBSD.org
.Sh BUGS
The serial driver code also has a notion of a
.Dq hot character .
Unfortunately, this value is statically defined in terms of the
line discipline and cannot be changed.
Therefore, if a hot character other than 0x7e (the default) is set for the
.Nm
node, the node has no way to convey this information to the
serial driver, and sub-optimal performance may result.

8
share/man/man4/ng_ubt.4
View File

@ -105,10 +105,6 @@ Reset all statistic counters to zero.
.El
.Sh SHUTDOWN
This node shuts down when the corresponding USB device is un-plugged.
.Sh BUGS
Isochronous USB transfers are broken.
This means that the USB device will not be able to transfer SCO data (voice).
USB interrupt transfers are implemented as bulk-in transfers (not really a bug).
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr ugen 4 ,
@ -121,3 +117,7 @@ node type was implemented in
.Fx 5.0 .
.Sh AUTHORS
.An Maksim Yevmenkin Aq m_evmenkin@yahoo.com
.Sh BUGS
Isochronous USB transfers are broken.
This means that the USB device will not be able to transfer SCO data (voice).
USB interrupt transfers are implemented as bulk-in transfers (not really a bug).

12
share/man/man4/ng_uni.4
View File

@ -398,6 +398,12 @@ Note, that connections are not released.
.Xr ng_sscfu 4 ,
.Xr ng_sscop 4 ,
.Xr ngctl 8
.Sh AUTHORS
The
.Nm uni
netgraph node
and this manual page were written by
.An Harti Brandt Aq harti@FreeBSD.org
.Sh BUGS
.Bl -bullet -compact
.It
@ -411,9 +417,3 @@ PNNI not yet implemented.
.It
Need to implement connection modification and the Q.2931 amendments.
.El
.Sh AUTHORS
The
.Nm uni
netgraph node
and this manual page were written by
.An Harti Brandt Aq harti@FreeBSD.org

36
share/man/man4/ng_vjc.4
View File

@ -193,24 +193,6 @@ Failing to do this can result in corrupted TCP stream data.
This node shuts down upon receipt of a
.Dv NGM_SHUTDOWN
control message, or when all hooks have been disconnected.
.Sh BUGS
As the initialization routine in the kernel implementation of
Van Jacobson compression initializes both compression and decompression
at once, this node does not allow compression and decompression to
be enabled in separate operations.
In order to enable one when
the other is already enabled, first both must be disabled, then
both enabled.
This of course resets the node state.
This restriction may be lifted in a later version.
.Pp
When built as a loadable kernel module, this module includes the file
.Pa net/slcompress.c .
Although loading the module should fail if
.Pa net/slcompress.c
already exists in the kernel, currently it does not, and the duplicate
copies of the file do not interfere.
However, this may change in the future.
.Sh SEE ALSO
.Xr netgraph 4 ,
.Xr ng_iface 4 ,
@ -233,3 +215,21 @@ node type was implemented in
.Fx 4.0 .
.Sh AUTHORS
.An Archie Cobbs Aq archie@FreeBSD.org
.Sh BUGS
As the initialization routine in the kernel implementation of
Van Jacobson compression initializes both compression and decompression
at once, this node does not allow compression and decompression to
be enabled in separate operations.
In order to enable one when
the other is already enabled, first both must be disabled, then
both enabled.
This of course resets the node state.
This restriction may be lifted in a later version.
.Pp
When built as a loadable kernel module, this module includes the file
.Pa net/slcompress.c .
Although loading the module should fail if
.Pa net/slcompress.c
already exists in the kernel, currently it does not, and the duplicate
copies of the file do not interfere.
However, this may change in the future.

4
share/man/man4/nsp.4
View File

@ -60,8 +60,6 @@ I-O DATA CBSC16
.Xr pccard 4 ,
.Xr sa 4 ,
.Xr scsi 4
.Sh BUGS
SMIT mode is only supported under OLDCARD now.
.Sh HISTORY
The
.Nm
@ -84,3 +82,5 @@ This manual page was written by
.An Noriaki MITSUNAGA Aq non@FreeBSD.org
and
.An Hideyuki KURASHINA Aq rushani@FreeBSD.org .
.Sh BUGS
SMIT mode is only supported under OLDCARD now.

32
share/man/man4/pcm.4
View File

@ -341,9 +341,19 @@ AC97 codec is not likely to be accompanied with the sound card.
.It unsupported subdevice XX
A device node is not created properly.
.El
.Sh BUGS
Some features of your cards (e.g., global volume control) might not
be supported on all devices.
.Sh SEE ALSO
.Xr snd_csa 4 ,
.Xr snd_gusc 4 ,
.Xr snd_sbc 4 ,
.Xr devfs 5 ,
.Xr loader.conf 5 ,
.Xr dmesg 8 ,
.Xr kldload 8 ,
.Xr sysctl 8
.Rs
.%T "The OSS API"
.%O "http://www.opensound.com/pguide/oss.pdf"
.Re
.Sh HISTORY
The
.Nm
@ -360,19 +370,6 @@ by
.An Cameron Grant .
The API evolved from the VOXWARE
standard which later became OSS standard.
.Sh SEE ALSO
.Xr snd_csa 4 ,
.Xr snd_gusc 4 ,
.Xr snd_sbc 4 ,
.Xr devfs 5 ,
.Xr loader.conf 5 ,
.Xr dmesg 8 ,
.Xr kldload 8 ,
.Xr sysctl 8
.Rs
.%T "The OSS API"
.%O "http://www.opensound.com/pguide/oss.pdf"
.Re
.Sh AUTHORS
.An -nosplit
.An Luigi Rizzo Aq luigi@iet.unipi.it
@ -386,3 +383,6 @@ later revised the device driver for
revised this manual page.
It was then rewritten for
.Fx 5.2 .
.Sh BUGS
Some features of your cards (e.g., global volume control) might not
be supported on all devices.

20
share/man/man4/pcvt.4
View File

@ -696,6 +696,16 @@ driver
Documents the various compile-time options to tailor
.Nm .
.El
.Sh SEE ALSO
.Xr cursor 1 ,
.Xr loadfont 1 ,
.Xr scon 1 ,
.Xr intro 2 ,
.Xr ioctl 2 ,
.Xr atkbd 4 ,
.Xr keyboard 4 ,
.Xr config 8 ,
.Xr ispcvt 8
.Sh HISTORY
The
.Nm
@ -737,15 +747,5 @@ and
.An Don Ahn ,
and the keyboard mapping code from
.An Holger Veit Aq veit@first.gmd.de .
.Sh SEE ALSO
.Xr cursor 1 ,
.Xr loadfont 1 ,
.Xr scon 1 ,
.Xr intro 2 ,
.Xr ioctl 2 ,
.Xr atkbd 4 ,
.Xr keyboard 4 ,
.Xr config 8 ,
.Xr ispcvt 8
.Sh BUGS
At least one left.

8
share/man/man4/ppc.4
View File

@ -122,10 +122,6 @@ ppb->ppb_avm field contains the available modes of the chipset.
.Xr ppbus 4 ,
.Xr ppi 4 ,
.Xr device.hints 5
.Sh BUGS
The chipset detection process may corrupt your chipset configuration.
You may
disable chipset specific detection by using the above flags.
.Sh HISTORY
The
.Nm
@ -134,3 +130,7 @@ manual page first appeared in
.Sh AUTHORS
This manual page was written by
.An Nicolas Souchu .
.Sh BUGS
The chipset detection process may corrupt your chipset configuration.
You may
disable chipset specific detection by using the above flags.

18
share/man/man4/psm.4
View File

@ -833,15 +833,6 @@ by switching away to a virtual terminal and getting back to the X server,
unless the X server is accessing the mouse via
.Xr moused 8 .
Clicking any button without moving the mouse may also work.
.Sh BUGS
The ioctl command
.Dv MOUSEIOCREAD
has been removed.
It was never functional anyway.
.Pp
Enabling the extended support for Synaptics touchpads has been reported to
cause problems with responsivity on some (newer) models of Synaptics
hardware, particularly those with guest devices.
.Sh SEE ALSO
.Xr ioctl 2 ,
.Xr syslog 3 ,
@ -873,3 +864,12 @@ to name the few.
.Pp
This manual page was written by
.An Kazutaka Yokota Aq yokota@FreeBSD.org .
.Sh BUGS
The ioctl command
.Dv MOUSEIOCREAD
has been removed.
It was never functional anyway.
.Pp
Enabling the extended support for Synaptics touchpads has been reported to
cause problems with responsivity on some (newer) models of Synaptics
hardware, particularly those with guest devices.

40
share/man/man4/sa.4
View File

@ -197,26 +197,6 @@ Eject on close (if capable)
Control mode device (to examine state while another program is
accessing the device, e.g.).
.El
.Sh BUGS
This driver lacks many of the hacks required to deal with older devices.
Many older
.Tn SCSI-1
devices may not work properly with this driver yet.
.Pp
Additionally, certain
tapes (QIC tapes mostly) that were written under
.Fx
2.X
aren't automatically read correctly with this driver: you may need to
explicitly set variable block mode or set to the blocksize that works best
for your device in order to read tapes written under
.Fx
2.X.
.Pp
Fine grained density and compression mode support that is bound to specific
device names needs to be added.
.Pp
Support for fast indexing by use of partitions is missing.
.Sh DIAGNOSTICS
None.
.Sh SEE ALSO
@ -245,3 +225,23 @@ The current owner of record is
.An Matthew Jacob
who has suffered too many
years of breaking tape drivers.
.Sh BUGS
This driver lacks many of the hacks required to deal with older devices.
Many older
.Tn SCSI-1
devices may not work properly with this driver yet.
.Pp
Additionally, certain
tapes (QIC tapes mostly) that were written under
.Fx
2.X
aren't automatically read correctly with this driver: you may need to
explicitly set variable block mode or set to the blocksize that works best
for your device in order to read tapes written under
.Fx
2.X.
.Pp
Fine grained density and compression mode support that is bound to specific
device names needs to be added.
.Pp
Support for fast indexing by use of partitions is missing.

14
share/man/man4/sbsh.4
View File

@ -43,6 +43,13 @@ Modem-specific
parameters (master/slave mode, line rate, etc.) must be set with the
.Nm sb16config
utility before interface activation.
.Sh FILES
The sources for the driver reside in:
.Pp
.Bl -tag -compact
.It Pa /sys/dev/sbsh/if_sbsh.c
.It Pa /sys/dev/sbsh/if_sbshreg.h
.El
.Sh DIAGNOSTICS
.Bl -diag
.It "sbsh%d: couldn't map memory"
@ -64,13 +71,6 @@ Probably, a hardware error or incompatibility.
.It "sbsh%d: unable to get mbuf cluster"
The driver failed to allocate a memory buffer.
.El
.Sh FILES
The sources for the driver reside in:
.Pp
.Bl -tag -compact
.It Pa /sys/dev/sbsh/if_sbsh.c
.It Pa /sys/dev/sbsh/if_sbshreg.h
.El
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,

4
share/man/man4/snd_csa.4
View File

@ -58,12 +58,12 @@ Such configurations are not
supported by the
.Nm
driver yet.
.Sh SEE ALSO
.Xr sound 4
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 4.0 .
.Sh SEE ALSO
.Xr sound 4
.Sh AUTHORS
.An Seigo Tanimura Aq tanimura@r.dl.itc.u-tokyo.ac.jp

4
share/man/man4/snd_gusc.4
View File

@ -70,13 +70,13 @@ Gravis UltraSound PnP
.It xxx: gus pcm not attached, out of memory
There are not enough memory to drive the device.
.El
.Sh SEE ALSO
.Xr sound 4
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 4.0 .
.Sh SEE ALSO
.Xr sound 4
.Sh AUTHORS
.An Ville-Pertti Keinonen Aq will@iki.fi
.An Seigo Tanimura Aq tanimura@r.dl.itc.u-tokyo.ac.jp

4
share/man/man4/snd_ich.4
View File

@ -79,13 +79,13 @@ NVIDIA nForce3 250
.It
SiS 7012
.El
.Sh SEE ALSO
.Xr sound 4
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 4.2 .
.Sh SEE ALSO
.Xr sound 4
.Sh AUTHORS
This manual page was written by
.An Jorge Mario G. Mazo Aq jgutie11@eafit.edu.co .

6
share/man/man4/snd_maestro.4
View File

@ -54,14 +54,14 @@ ESS Technology Maestro-2
.It
ESS Technology Maestro-2E
.El
.Sh SEE ALSO
.Xr snd_maestro3 4 ,
.Xr sound 4
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 4.2 .
.Sh SEE ALSO
.Xr snd_maestro3 4 ,
.Xr sound 4
.Sh AUTHORS
This manual page was written by
.An Jorge Mario G. Mazo Aq jgutie11@eafit.edu.co .

4
share/man/man4/snd_sbc.4
View File

@ -70,12 +70,12 @@ Check the I/O port configuration.
.It bad irq XX (5/7/9/10 valid)
The IRQ given to the driver is not valid.
.El
.Sh SEE ALSO
.Xr sound 4
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 4.0 .
.Sh SEE ALSO
.Xr sound 4
.Sh AUTHORS
.An Seigo Tanimura Aq tanimura@r.dl.itc.u-tokyo.ac.jp

14
share/man/man4/snp.4
View File

@ -69,16 +69,16 @@ and detached.
.Xr sio 4 ,
.Xr kldload 8 ,
.Xr watch 8
.Sh HISTORY
The
.Nm
device first appeared in
.Fx 2.1 .
.Sh AUTHORS
.An Ugen J.S. Antsilevich Aq ugen@NetVision.net.il
.Sh BUGS
Caveat emptor!
This manual page is horribly stale and wildly inaccurate in some places.
.Pp
While in line mode, user input cannot be seen.
No signals may be sent to the observed tty.
.Sh AUTHORS
.An Ugen J.S. Antsilevich Aq ugen@NetVision.net.il
.Sh HISTORY
The
.Nm
device first appeared in
.Fx 2.1 .

4
share/man/man4/spic.4
View File

@ -49,13 +49,13 @@ respectively.
From that a program reading the Jogdial can decide what to do.
Some actions might include scrolling, mimicking mouse buttons, launching
applications, or other useful things.
.Sh SEE ALSO
.Xr moused 8
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 4.6 .
.Sh SEE ALSO
.Xr moused 8
.Sh AUTHORS
.An Nick Sayer Aq nsayer@FreeBSD.org
.An Will Andrews Aq will@FreeBSD.org

Some files were not shown because too many files have changed in this diff Show More