diff options
Diffstat (limited to 'share/man/man4/man4.i386')
31 files changed, 244 insertions, 244 deletions
diff --git a/share/man/man4/man4.i386/aic.4 b/share/man/man4/man4.i386/aic.4 index 2d4de95..c48d005 100644 --- a/share/man/man4/man4.i386/aic.4 +++ b/share/man/man4/man4.i386/aic.4 @@ -9,7 +9,7 @@ .\" notice, this list of conditions and the following disclaimer. .\" 2. The name of the author may not be used to endorse or promote products .\" derived from this software without specific prior written permission -.\" +.\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. @@ -42,7 +42,7 @@ Many systems that use these controller chips do not have a boot ROM and therefore cannot be booted from. .Sh SEE ALSO .Xr cd 4 , -.Xr ch 4 , +.Xr ch 4 , .Xr da 4 , .Xr intro 4 , .Xr sa 4 diff --git a/share/man/man4/man4.i386/alpm.4 b/share/man/man4/man4.i386/alpm.4 index 9c54d13..aceee0d 100644 --- a/share/man/man4/man4.i386/alpm.4 +++ b/share/man/man4/man4.i386/alpm.4 @@ -36,7 +36,7 @@ .Sh DESCRIPTION This driver provides access to the .Tn Aladdin 15x3 Power Management Unit . -Currently, only smbus controller +Currently, only smbus controller function is implemented. .Pp The embedded SMBus controller of the Aladdin chipset may give you access @@ -51,7 +51,7 @@ monitoring chip of your mainboard. .Sh HISTORY The .Nm -manual page example first appeared in +manual page example first appeared in .Fx 4.0 . .Sh AUTHORS This diff --git a/share/man/man4/man4.i386/apm.4 b/share/man/man4/man4.i386/apm.4 index b301a2f..a19cb7f 100644 --- a/share/man/man4/man4.i386/apm.4 +++ b/share/man/man4/man4.i386/apm.4 @@ -1,12 +1,12 @@ .\" LP (Laptop Package) -.\" +.\" .\" Copyright (c) 1994 by HOSOKAWA, Tatsumi <hosokawa@mt.cs.keio.ac.jp> -.\" +.\" .\" This software may be used, modified, copied, and distributed, in .\" both source and binary form provided that the above copyright and -.\" these terms are retained. Under no circumstances is the author -.\" responsible for the proper functioning of this software, nor does -.\" the author assume any responsibility for damages incurred with its +.\" these terms are retained. Under no circumstances is the author +.\" responsible for the proper functioning of this software, nor does +.\" the author assume any responsibility for damages incurred with its .\" use. .\" .\" $FreeBSD$ @@ -28,19 +28,19 @@ on laptop PCs. provides the following power management functions. .Bl -enum -offset indent .It -When the system wakes up from suspended mode, +When the system wakes up from suspended mode, .Nm adjusts the system clock to RTC. -.It -When the system wakes up from suspended mode, +.It +When the system wakes up from suspended mode, .Nm -passes a message to +passes a message to .Xr syslogd 8 comprising of system wakeup time and elapsed time during suspended mode. .It .Nm -slows CPU clock when there are no system activities (runnable processes, -interrupts, etc.). This function is available only on systems whose APM +slows CPU clock when there are no system activities (runnable processes, +interrupts, etc.). This function is available only on systems whose APM supports CPU idling. .It .Nm @@ -63,33 +63,33 @@ Control execution of HLT in the kernel context switch routine. .It Sy APMIO_GETPWSTATUS Get per battery information. .Pp -Some APM implementations execute the HLT +Some APM implementations execute the HLT .Pq Halt CPU until an interrupt occurs instruction in the .Dq Em Idle CPU call, while others do not. Thus enabling this may result in redundant HLT executions because .Dq Em Idle CPU -is called from the kernel context switch routine that inherently executes -HLT. This may reduce peak system performance. +is called from the kernel context switch routine that inherently executes +HLT. This may reduce peak system performance. .Pp -Also the system hangs up if HLT instruction is disabled in the kernel -context switch routine, and if the APM implementation of the machine +Also the system hangs up if HLT instruction is disabled in the kernel +context switch routine, and if the APM implementation of the machine does not execute HLT in .Dq Em Idle CPU . -On some implementations that do not support CPU clock slowdown, APM +On some implementations that do not support CPU clock slowdown, APM might not execute HLT. .Nm disables .Sy APMIO_NOTHALTCPU -operation on such machines. +operation on such machines. .Pp The current version of .Nm does not call .Dq Em Idle CPU -from the kernel context switch routine if clock slowdown is not supported, -and it executes HLT instruction by default. Therefore, there is +from the kernel context switch routine if clock slowdown is not supported, +and it executes HLT instruction by default. Therefore, there is no need to use these two operations in most cases. .El .Pp @@ -98,7 +98,7 @@ These interfaces are used by .It .Nm polls APM events and handles the following events. -.Bl -column PMEV_POWERSTATECHANGEXXX "suspend system xxxxx" +.Bl -column PMEV_POWERSTATECHANGEXXX "suspend system xxxxx" .It Sy "Name " "Action " "Description" .It Dv "PMEV_STANDBYREQ " No "suspend system " "standby request" .It Dv "PMEV_SUSPENDREQ " No "suspend system " "suspend request" @@ -110,7 +110,7 @@ polls APM events and handles the following events. .It Dv "PMEV_BATTERYLOW " No "notify message " "battery low" .It Dv "PMEV_UPDATETIME " No "adjust clock " "update time" .El -.El +.El .Sh BUGS WARNING! Many, if not most, of the implementations of APM-bios in laptops today are buggy. You may be putting your LCD-display and batteries at @@ -122,23 +122,23 @@ power and batteries ASAP, if not immediately, and disable this code. We are very interested in getting this code working, so please send you observations of any anomalous behavior to us. .Pp -When +When .Nm -is active, calling the BIOS setup routine by using hot-keys, +is active, calling the BIOS setup routine by using hot-keys, may cause serious trouble when resuming the system. BIOS setup programs should be called during bootstrap, or from DOS. .Pp -Some APM implementations cannot handle events such as pushing the -power button or closing the cover. On such implementations, the system +Some APM implementations cannot handle events such as pushing the +power button or closing the cover. On such implementations, the system .Ar must be suspended .Ar only -by using +by using .Xr apm 8 -or +or .Xr zzz 8 . .Pp -Disk spin-down, LCD backlight control, and power on demand have not +Disk spin-down, LCD backlight control, and power on demand have not been supported on the current version. .Sh SEE ALSO .Xr apm 8 , diff --git a/share/man/man4/man4.i386/asc.4 b/share/man/man4/man4.i386/asc.4 index fdfa15a..2c8c66d 100644 --- a/share/man/man4/man4.i386/asc.4 +++ b/share/man/man4/man4.i386/asc.4 @@ -44,7 +44,7 @@ The character device driver currently handles the .Tn GI1904 Ns -based hand scanner (e.g. Trust Amiscan Grey). -It uses DMA and interrupts. +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 @@ -89,7 +89,7 @@ Get current resolution in dots per inch (dpi). Get current width of the bitmap in pixels. .It Dv ASC_SHEIGHT .Pq Li int -Set the height of the bitmap in +Set the height of the bitmap in .Xr pbm 5 mode. This is actually a limit on the amount of lines scannable after the first read @@ -116,10 +116,10 @@ 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 +timeout is reached the read operation will fail with .Er EBUSY . Note that -the timeout timer starts anew for each buffer to be read and thus +the timeout timer starts anew for each buffer to be read and thus reducing it does not result in faster scans for longer images. .It Dv ASC_GBTIME .Pq Li int @@ -132,13 +132,13 @@ requests that modify a parameter except .Dv ASC_SBTIME do not have an effect on an ongoing scan process. The user must close the device and open it again for the new selections to take effect. -Consequently, the selections are +Consequently, the selections are .Em not reset when the device is opened or closed. .Pp Similarly, requests that read a value do not report the value that is used for the ongoing scan process. The values needed during the scan -process are saved when it starts and thus are not accessed by +process are saved when it starts and thus are not accessed by .Fn ioctl requests. .Pp diff --git a/share/man/man4/man4.i386/asr.4 b/share/man/man4/man4.i386/asr.4 index 258b97f..889338d 100644 --- a/share/man/man4/man4.i386/asr.4 +++ b/share/man/man4/man4.i386/asr.4 @@ -89,7 +89,7 @@ and was ported over to the CAM layer represented in 4.0. The .Nm driver was kindly donated by Adaptec -and is maintained by +and is maintained by .An Mark Salyzyn Aq mark_salyzyn@adaptec.com . This manual page was written by .An Mark Salyzyn diff --git a/share/man/man4/man4.i386/cs.4 b/share/man/man4/man4.i386/cs.4 index 6604175..95657c2 100644 --- a/share/man/man4/man4.i386/cs.4 +++ b/share/man/man4/man4.i386/cs.4 @@ -37,13 +37,13 @@ .Sh DESCRIPTION The .Nm -driver provides support for ISA ethernet adapters based on the +driver provides support for ISA ethernet adapters based on the .Tn Crystal Semiconductor CS8900 and .Tn CS8920 -NICs. These devices are used on the -.Tn IBM EtherJet ISA -adapters and in many embedded applications where the high integration, small +NICs. These devices are used on the +.Tn IBM EtherJet ISA +adapters and in many embedded applications where the high integration, small size and low cost of the CS89x0 family compensate for their drawbacks. .Pp The @@ -52,10 +52,10 @@ driver will obtain configuration parameters either from the configuration entry or from the card. Parameters specified in the configuration entry will be used if present; the card may be soft-configured so these may be any valid value. Adapters based on the CS8920 normally offer PnP configuration and the driver -will detect the -.Tn IBM EtherJet -and the -.Tn CSC6040 +will detect the +.Tn IBM EtherJet +and the +.Tn CSC6040 adapters automatically. .Pp Note that the CS8900 is limited to 4 IRQ values; these are normally implemented @@ -97,16 +97,16 @@ In particular, NFS operations should be limited to 1k read/write transactions in order to avoid overruns. .Sh SEE ALSO .Xr arp 4 , -.Xr netintro 4 , +.Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh AUTHORS .An -nosplit The .Nm -device driver was written by -.An Maxim Bolotin -and +device driver was written by +.An Maxim Bolotin +and .An Oleg Sharoiko . This manpage was written by .An Michael Smith . diff --git a/share/man/man4/man4.i386/dgb.4 b/share/man/man4/man4.i386/dgb.4 index c62b40c..4782d27 100644 --- a/share/man/man4/man4.i386/dgb.4 +++ b/share/man/man4/man4.i386/dgb.4 @@ -60,7 +60,7 @@ default = number_of_described_DigiBoard_cards * 16 .Ed .Pp -If it is less than the actual number of ports +If it is less than the actual number of ports the system will be able to use only the first .Dv NDGBPORTS @@ -111,10 +111,10 @@ This is practical because the DigiBoard cards have large input and output buffers (more than 1Kbyte per port) and hardware that allows efficiently finding the port that needs attention. -The only problem seen with this policy is slower +The only problem seen with this policy is slower SLIP and PPP response. .Pp -Each line in the kernel configuration file describes one card, not one port +Each line in the kernel configuration file describes one card, not one port as in the .Xr sio 4 driver. @@ -135,7 +135,7 @@ needed. The .Cm port value must be the same -as the +as the port set on the card by jumpers. For PC/Xi cards the same rule is applicable to the @@ -151,7 +151,7 @@ In fact there are no jumpers to do it. Just write the address you want as the .Cm iomem -value in kernel config file and the card will be programmed +value in kernel config file and the card will be programmed to use this address. .Pp The same range of memory addresses may be used @@ -289,7 +289,7 @@ start of the source file The memory address for the PC/Xe's 8K window is misaligned (it should be on an 8K boundary) or outside of the first megabyte. .It dgb\fIX\fP: 1st reset failed -Problems with accessing I/O port of the card, probably +Problems with accessing I/O port of the card, probably the wrong .Cm port value is specified in the kernel config file. @@ -309,11 +309,11 @@ Problems with the on-board BIOS. Probably the memory addresses of the DigiBoard overlap with some other device or with RAM. .It dgb\fIX\fP: FEP code download failed -Problems with downloading of the Front-End Processor's micro-OS. +Problems with downloading of the Front-End Processor's micro-OS. Probably the memory addresses of the DigiBoard overlap with some other device or with RAM. .It dgb\fIX\fP: FEP/OS start failed -Problems with starting of the Front-End Processor's micro-OS. +Problems with starting of the Front-End Processor's micro-OS. Probably the memory addresses of the DigiBoard overlap with some other device or with RAM. .It dgb\fIX\fP: too many ports @@ -336,7 +336,7 @@ Internal problems in the polling logic of driver. .It dgb\fIX\fP: event queue's head or tail is wrong! Internal problems in the driver or hardware. .It dgb\fIX\fP: port \fIY\fP: got event on nonexisting port -Some status changed on a port that is physically present but is +Some status changed on a port that is physically present but is unusable due to misconfiguration. .It dgb\fIX\fP: port \fIY\fP: event \fIN\fP mstat \fIM\fP lstat \fIK\fP The driver got a strange event from card. @@ -362,8 +362,8 @@ The .Nm driver is derived from the .Xr sio 4 -driver and the DigiBoard driver from -.Tn Linux +driver and the DigiBoard driver from +.Tn Linux and is .Ud .Sh BUGS @@ -374,7 +374,7 @@ is broken. of fixed length of 1/4 s is sent anyway. .Pp -There was a bug in implementation of +There was a bug in implementation of .Xr select 2 . It is fixed now but not widely tested yet. .Pp diff --git a/share/man/man4/man4.i386/el.4 b/share/man/man4/man4.i386/el.4 index 092f944..caf3f1d 100644 --- a/share/man/man4/man4.i386/el.4 +++ b/share/man/man4/man4.i386/el.4 @@ -9,7 +9,7 @@ .\" notice, this list of conditions and the following disclaimer. .\" 2. The name of the author may not be used to endorse or promote products .\" derived from this software without specific prior written permission -.\" +.\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. diff --git a/share/man/man4/man4.i386/ex.4 b/share/man/man4/man4.i386/ex.4 index dda2c7f..f999309 100644 --- a/share/man/man4/man4.i386/ex.4 +++ b/share/man/man4/man4.i386/ex.4 @@ -49,7 +49,7 @@ cards the Plug-N-Play support should be disabled. The device probe found an installed card, and was able to correctly install the device driver. .It "ex%d: WARNING: board's EEPROM is configured for IRQ %d, using %d" -The device probe detected that the board is configured for a different +The device probe detected that the board is configured for a different interrupt than the one specified in the kernel configuration file. .It "ex%d: invalid IRQ." The device probe detected an invalid IRQ setting. diff --git a/share/man/man4/man4.i386/fe.4 b/share/man/man4/man4.i386/fe.4 index de674d4..866b297 100644 --- a/share/man/man4/man4.i386/fe.4 +++ b/share/man/man4/man4.i386/fe.4 @@ -204,7 +204,7 @@ The driver will generate a warning message, if the IRQ setting specified in the kernel config file does not match one stored in EEPROM. Then, it will use the value specified in the config file. -(This behavior has been changed from the previous releases.) +(This behavior has been changed from the previous releases.) .Ss Allied-Telesis AT1700 series and RE2000 series adapters Automatic I/O port address detection is available with Allied-Telesis AT1700 series and RE2000 series, @@ -263,7 +263,7 @@ The unnecessarily allocated clusters are freed within short lifetime, and it will not affect long term kernel memory usage. .Pp Although XNS and IPX supports are included in the driver, -they are never be tested and must have a lot of bugs. +they are never be tested and must have a lot of bugs. .Sh AUTHORS, COPYRIGHT AND DISCLAIMER The .Nm diff --git a/share/man/man4/man4.i386/gsc.4 b/share/man/man4/man4.i386/gsc.4 index c73188a..6b6b5d7 100644 --- a/share/man/man4/man4.i386/gsc.4 +++ b/share/man/man4/man4.i386/gsc.4 @@ -71,7 +71,7 @@ I had neither enough documentation nor experience in writing interrupt driven device drivers. .Pp -The device can operate at four different +The device can operate at four different .Em resolutions : 100, 200, 300 and 400dpi. @@ -86,24 +86,24 @@ Thus the scans can easily processed by any graphic package around .Xr xpaint 1 , .Xr xv 1 , .Xr xli 1 -only to name some of them ...). In +only to name some of them ...). In .Em raw mode a bit which is set means a black pixel because the scanner detects black points on white paper. On the other hand, because pnm format describes -intensities of electron beams in video screens a set bit in +intensities of electron beams in video screens a set bit in .Em pbm mode means a white pixel. .Pp -The +The .Em width of the output bitmap is fixed as given by the resolution value. -However, the +However, the .Em height of the bitmap must be -supplied in +supplied in .Em pnm mode since the driver must know at what time the .Sq end-of-file @@ -113,11 +113,11 @@ directly copy the scanner output into a pbm file with .Xr cat . Of course you can obtain a similar effect by using .Xr dd 1 -with the driver in +with the driver in .Em raw mode. .Pp -The +The .Em graymap output mode is not yet implemented into the driver. It is even questionable if external programs would not do this job @@ -150,7 +150,7 @@ open though untouched state otherwise the request will fail and is set to .Er EBUSY . .It GSC_SWIDTH int -Set the +Set the .Em width of the bitmap. Actually, this is an alternative @@ -177,7 +177,7 @@ width .El .Pp Values which are not reported in the above table will cause the ioctl -call to fail with +call to fail with .Xr errno 2 set to .Er EINVAL . @@ -194,9 +194,9 @@ the right part that is exceeding the standard line. .It GSC_GWIDTH int Get current width of the bitmap in pixels. .It GSC_SHEIGHT int -Set the +Set the .Em height -of the bitmap in +of the bitmap in .Em pnm mode. This is actually @@ -217,7 +217,7 @@ This upper limit is checked before it overwrites the current value and pases an .Er ENOMEM in the -.Xr errno 2 +.Xr errno 2 variable. However, since the bitmap width can change after a buffer length was selected a read request may fail with @@ -269,37 +269,37 @@ starts scanning. It can then be set to a short amount to react Note that the user should be left time to at least fill one buffer without having to haste. .Pp -Note that the +Note that the .Em pbm -versus +versus .Em raw mode selection is done by the minor number not by ioctl requests. -In +In .Em raw mode the selected height of the bitmap will have no effect. .Sh FILES .Bl -tag -width /dev/gsc0pd .It Pa /dev/gsc0 -device node for +device node for .Em raw output, has minor number 0. .It Pa /dev/gsc0d -device node for +device node for .Em raw -output emitting +output emitting .Em debug messages if the GSCDEBUG option was given at compile time, has minor number 32. .It Pa /dev/gsc0p -device node for output in +device node for output in .Em pbm file format, has minor number 8. .It Pa /dev/gsc0pd -device node for +device node for .Em pbm -and +and .Em debug mode, has minor number 40. .El diff --git a/share/man/man4/man4.i386/ie.4 b/share/man/man4/man4.i386/ie.4 index 01f35a7..b19625e 100644 --- a/share/man/man4/man4.i386/ie.4 +++ b/share/man/man4/man4.i386/ie.4 @@ -17,8 +17,8 @@ The .Nm 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 EN100, the Intel EtherExpress 16, the 3COM 3C507 and the RACAL Interlan +It supports the AT&T Starlan 10 and Starlan Fiber, +the EN100, the Intel EtherExpress 16, the 3COM 3C507 and the RACAL Interlan NI5210. .Sh DIAGNOSTICS .Bl -diag @@ -34,7 +34,7 @@ The device probe could not access the shared memory to determine its size. The device probe found a different size for the shared memory than the one specified in the kernel configuration file. .It "ie%d: kernel configured irq %d doesn't match board configured irq %d" -The device probe detected that the board is configured for a different +The device probe detected that the board is configured for a different interrupt than the one specified in the kernel configuration file. .It "ie%d: reset" The Intel i82586 had to be reset by the driver. @@ -52,11 +52,11 @@ 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 +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 -test. +test. .It "ie%d: multicast address setup command failed" The card could not be put into multicast mode. .It "ie%d: configure command failed" @@ -65,11 +65,11 @@ The card refused to respond correctly during configuration. The programming of the Ethernet (MAC) address failed. .El .Sh CAVEATS -The Racal Interlan NI5210 comes in variants with 8 and 16 kbytes of +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. +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. +RAM chip. .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , @@ -83,8 +83,8 @@ device driver was written by .An Garrett A. Wollman , based on code by .An William F. Jolitz -and Lawrence Berkeley Laboratories. -.Tn 3C507 +and Lawrence Berkeley Laboratories. +.Tn 3C507 support was written by .An Charles M. Hannum . This manual page was written by diff --git a/share/man/man4/man4.i386/le.4 b/share/man/man4/man4.i386/le.4 index 5b8a1f5..c5f1588 100644 --- a/share/man/man4/man4.i386/le.4 +++ b/share/man/man4/man4.i386/le.4 @@ -36,7 +36,7 @@ .Sh DESCRIPTION The .Nm -driver provides support for the later Digital Equipment EtherWORKS II +driver provides support for the later Digital Equipment EtherWORKS II (DE200, DE201, DE202, DE422), and the DEC EtherWORKS III NICs (DE203, DE204, and DE205) NICs. .Pp @@ -83,7 +83,7 @@ the EtherWORKS card. .Sh HISTORY The .Nm -device driver was present in +device driver was present in .Fx 2.0 . .Sh AUTHORS .An -nosplit diff --git a/share/man/man4/man4.i386/lnc.4 b/share/man/man4/man4.i386/lnc.4 index 3324032..bcc5326 100644 --- a/share/man/man4/man4.i386/lnc.4 +++ b/share/man/man4/man4.i386/lnc.4 @@ -116,7 +116,7 @@ Ethernet device drivers. .Sh HISTORY The .Nm -device driver first appeared in +device driver first appeared in .Fx 2.2 . .Sh AUTHORS .An -nosplit diff --git a/share/man/man4/man4.i386/matcd.4 b/share/man/man4/man4.i386/matcd.4 index 530c4eb..b31cf53 100644 --- a/share/man/man4/man4.i386/matcd.4 +++ b/share/man/man4/man4.i386/matcd.4 @@ -2,7 +2,7 @@ .\"Authored by Frank Durda IV .\" .\"Program and Documentation are Copyright 1994, 1995 Frank Durda IV. -.\"All rights reserved. +.\"All rights reserved. .\" "FDIV" is a trademark of Frank Durda IV. .\" .\" @@ -40,18 +40,18 @@ .\" conditions even if it is unsupported, not a complete system .\" and/or does not contain compiled code. .\"8. These conditions will be in force for the full life of the -.\" copyright. +.\" copyright. .\"9. If all the above conditions are met, modifications to other .\" parts of this file may be freely made, although any person .\" or persons making changes do not receive the right to add their .\" name or names to the copyright strings and notices in this .\" software. Persons making changes are encouraged to insert edit .\" history in matcd.c and to put your name and details of the -.\" change there. +.\" change there. .\"10. You must have prior written permission from the author to .\" deviate from these terms. .\" -.\"Vendors who produce product(s) containing this code are encouraged +.\"Vendors who produce product(s) containing this code are encouraged .\"(but not required) to provide copies of the finished product(s) to .\"the author and to correspond with the author about development .\"activity relating to this code. Donations of development hardware @@ -105,7 +105,7 @@ been included in computers made by Tandy, AST, Packard Bell and many others. .Pp These drives connect to the PC ISA bus through a proprietary host interface. This interface can exist as a stand-alone ISA card, or can be included on -a sound card. +a sound card. .Sh DRIVER CONFIGURATION The .Nm @@ -116,7 +116,7 @@ read operations are limited to one drive per host interface at any instant. To support multiple host interfaces, it is necessary to modify the entries in the kernel configuration file. Normally your system comes with the file \fI/usr/src/sys/i386/conf/GENERIC\fR. You should make -a copy of this file and give it the name of your system. +a copy of this file and give it the name of your system. You can then edit the new file to include devices you want the system to support and delete the device entries that you don't want. .Pp @@ -135,7 +135,7 @@ device matcd1 at isa? port ? additional entries). .Pp Note that the kernel configuration does not need to be modified to support -up to four drives on a single host interface. It is also not necessary to +up to four drives on a single host interface. It is also not necessary to have four drives on a single interface before adding a second interface. .Pp By default, @@ -143,7 +143,7 @@ By default, searches for the CD-ROM host interface adapters by using a table of known I/O ports on Creative host adapters (see \fIoptions.h\fR). Although this is very flexible, it can cause problems when your system has other devices -that are located at the I/O ports that +that are located at the I/O ports that .Nm is checking for CD-ROM host interfaces. In addition, checking multiple locations can cause the boot process to take longer than it could. @@ -187,14 +187,14 @@ Matsushita CR-562-x Matsushita CR-563-x .El Most resellers leave these original markings on the drives since the label -also has the FCC, VDE, CSA and RU certification marks. +also has the FCC, VDE, CSA and RU certification marks. .Pp Both of these drive models have motorized trays. There is also a custom version of these drives that does not have the volume control or headphone jack (seen on some Tandy computers), but this drive also works with .Nm . .Pp -The Matsushita CR-522-x and CR-523-x CD-ROM drive is not usable with +The Matsushita CR-522-x and CR-523-x CD-ROM drive is not usable with .Nm . The CR-522 and CR-523 can also be identified from the front as it requires a CD-caddy. @@ -202,8 +202,8 @@ requires a CD-caddy. Drives with IDE interfaces must use an IDE driver. .Pp The TEAC CD-55 4X CD-ROM drive also uses the Creative/Panasonic interface -but the TEAC drive is \fInot\fR compatible with the Matsushita CR-56x drives. -The TEAC drive cannot be used with +but the TEAC drive is \fInot\fR compatible with the Matsushita CR-56x drives. +The TEAC drive cannot be used with .Nm . .Pp The most common source of host interface adapters for the Panasonic drives @@ -218,7 +218,7 @@ driver: .Bl -tag -width LONGNAME -compact -offset indent .It Creative Sound Blaster Pro (SBPRO) (CT1330A) -.It Creative +.It Creative Sound Blaster 16 (CT1730) .It Creative Sound Blaster 16 - cost-reduced (CT1740) @@ -247,7 +247,7 @@ interface release new versions of their adapters all the time. In addition to Creative Labs adapters, adapters that are compatible with Media Vision, IBM and Lasermate adapters are also supported. However, these adapters use a wide range of I/O port addresses, so the driver -must be reconfigured to locate these adapters. +must be reconfigured to locate these adapters. .Pp It is important to understand that some manufacturers have a different host interface implementation. If you have a board that won't communicate @@ -263,15 +263,15 @@ driver supports block and character access. Partition "a" returns "c" cannot be "mounted" with cd9660 or other filesystem emulators.) No other partitions are supported. .Pp -The +The .Nm matcdl devices work the same as the normal .Nm devices except that the drive trays are locked and remain locked until all of the devs on that drive are closed. .Pp -.Nm Matcd -accepts numerous +.Nm Matcd +accepts numerous .Fn ioctl commands, including disk and functions related to CD-ROM audio and tray control features. The commands are: @@ -342,17 +342,17 @@ The .Fn ioctl commands defined above are the only ones that the .Nm -driver supports. +driver supports. .Sh FILES .Bl -tag -width /dev/(r)matcd0a_/dev/(r)matcdl0a -compact .It Pa /dev/[r]matcd0a /dev/[r]matcdl0a is used to access 2048-byte blocks of data on a CD-ROM disc -that is recorded in the Mode 1 Form 1 format. +that is recorded in the Mode 1 Form 1 format. .It Pa /dev/[r]matcd0c /dev/[r]matcdl0c is used to access 2352-byte frames on a CD-ROM disc recorded in any format. .It Pa /usr/src/sys/i386/isa/matcd/* -Source code and compilation options for +Source code and compilation options for .Nm . .El .Pp @@ -387,8 +387,8 @@ numbers are always contiguous. The driver and documentation was written by .An Frank Durda IV . .Pp -Program and Documentation are Copyright 1994, 1995, -All rights reserved. +Program and Documentation are Copyright 1994, 1995, +All rights reserved. .Sh HISTORY The .Nm diff --git a/share/man/man4/man4.i386/meteor.4 b/share/man/man4/man4.i386/meteor.4 index b4d2ed8..14616cd 100644 --- a/share/man/man4/man4.i386/meteor.4 +++ b/share/man/man4/man4.i386/meteor.4 @@ -15,7 +15,7 @@ The driver provides support for a PCI .Em video capture. -It allows the capture of 24 bit RGB, 16 bit RGB and 16 bit YUV +It allows the capture of 24 bit RGB, 16 bit RGB and 16 bit YUV output formats. .Pp .Ss Meteor Driver Installation @@ -206,7 +206,7 @@ memory into the user process space, and issues either the single-capture or the continuous capture call (see: .Dv METEORCAPTUR .Xr ioctl 2 -call) to load the data into the memory mapped buffer. +call) to load the data into the memory mapped buffer. .Pp As explained in the .Dv METEORCAPTUR @@ -263,20 +263,20 @@ main() exit(1); } - mmbuf=(char *)mmap((caddr_t)0, SIZE, PROT_READ, + mmbuf=(char *)mmap((caddr_t)0, SIZE, PROT_READ, MAP_SHARED, i, (off_t)0); #ifdef SINGLE_MODE /* single frame capture */ c = METEOR_CAP_SINGLE ; ioctl(i, METEORCAPTUR, &c); /* wait for the frame */ - + /* directly access the frame buffer array data in mmbuf */ #else /* continuous frame capture */ c = METEOR_CAP_CONTINOUS ; ioctl(i, METEORCAPTUR, &c); /* returns immediately */ - + /* directly access the frame buffer array data in mmbuf */ c = METEOR_CAP_STOP_CONT ; @@ -293,7 +293,7 @@ Memory mapped, multi-frame ring buffer synchronize capture. This continuous capture mode is synchronized with the application that processes up to 32 frames. This gives the advantages of both single and -continuous capture modes. +continuous capture modes. .Pp The kernel notifies the application of a new data by raising an application defined signal. @@ -409,7 +409,7 @@ usr2_catcher() /* add frame processing here */ /* deactivate frame */ common_mem->active &= ~(1 << (sig_cnt % 16)); - common_mem->num_active_bufs--; + common_mem->num_active_bufs--; /* process next frame on next interrupt */ sig_cnt = ((sig_cnt+1) % FRAME_MAX); @@ -601,7 +601,7 @@ will also attempt to reallocate a new contiguous 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. +the existing buffer is used. .Pp If .Dv METEORSETGEO @@ -849,7 +849,7 @@ and and .Dv METEORGCHCV are used to set and get the chrominance -gain control and effects the UV output amplitude. +gain control and effects the UV output amplitude. .Pp If .Dv METEORSCHCV @@ -899,7 +899,7 @@ invalid signed char pointer. requests .Dv METEORSCOUNT and -.Dv METEORGCOUNT +.Dv METEORGCOUNT .Pp .Dv METEORGCOUNT is used to get the count of frame errors, DMA errors and diff --git a/share/man/man4/man4.i386/mse.4 b/share/man/man4/man4.i386/mse.4 index bde26bb..3dc8cb0 100644 --- a/share/man/man4/man4.i386/mse.4 +++ b/share/man/man4/man4.i386/mse.4 @@ -31,7 +31,7 @@ The interface circuit may come on an integrated I/O card or as an option on video cards. .Pp The bus and InPort mice have two or three buttons, -and a D-sub 9-pin male connector or a round DIN 9-pin +and a D-sub 9-pin male connector or a round DIN 9-pin male connector. .Pp The primary port address of the bus and InPort mouse interface cards @@ -51,22 +51,22 @@ It may be 15, 30, 60 or 120Hz. The difference between the two types of the mice is not in mouse devices (in fact they are exactly the same). But in the circuit on the interface cards. -This means that the device from a bus mouse package can be +This means that the device from a bus mouse package can be connected to the interface card from an InPort mouse package, or vice versa, provided that their connectors match. .Ss Operation Levels The .Nm -driver has two levels of operation. +driver has two levels of operation. The current operation level can be set via an ioctl call. .Pp At the level zero the basic support is provided; the device driver will report -horizontal and vertical movement of the attached device +horizontal and vertical movement of the attached device and state of up to three buttons in the format described below. It is a subset of the MouseSystems protocol. .Pp .Bl -tag -width Byte_1 -compact -.It Byte 1 +.It Byte 1 .Bl -tag -width bit_7 -compact .It bit 7 Always one. @@ -91,23 +91,23 @@ Always zero. Always zero. .El .Pp -This is the default level of operation and the driver is initially +This is the default level of operation and the driver is initially at this level when opened by the user program. .Pp At the operation level one (extended level), a data packet is encoded in the standard format -.Dv MOUSE_PROTO_SYSMOUSE +.Dv MOUSE_PROTO_SYSMOUSE as defined in .Xr mouse 4 . .Ss Acceleration The .Nm driver can somewhat `accelerate' the movement of the pointing device. -The faster you move the device, the further the pointer -travels on the screen. -The driver has an internal variable which governs the effect of +The faster you move the device, the further the pointer +travels on the screen. +The driver has an internal variable which governs the effect of the acceleration. -Its value can be modified via the driver flag +Its value can be modified via the driver flag or via an ioctl call. .Ss Device Number The minor device number of the @@ -118,9 +118,9 @@ minor = (`unit' << 1) | `non-blocking' .Ed .Pp where `unit' is the device number (usually 0) and the `non-blocking' bit -is set to indicate ``don't block waiting for mouse input, +is set to indicate ``don't block waiting for mouse input, return immediately''. -The `non-blocking' bit should be set for \fIXFree86\fP, +The `non-blocking' bit should be set for \fIXFree86\fP, therefore the minor device number usually used for \fIXFree86\fP is 1. See .Sx FILES @@ -131,26 +131,26 @@ for device node names. The .Nm driver accepts the following driver flag. -Set it in the -kernel configuration file +Set it in the +kernel configuration file .Pq see Xr config 8 or in the User Configuration Menu at -the boot time +the boot time .Pq see Xr boot 8 . .Pp .Bl -tag -width MOUSE .It bit 4..7 ACCELERATION This flag controls the amount of acceleration effect. -The smaller the value of this flag is, more sensitive the movement becomes. -The minimum value allowed, thus the value for the most sensitive setting, +The smaller the value of this flag is, more sensitive the movement becomes. +The minimum value allowed, thus the value for the most sensitive setting, is one. Setting this flag to zero will completely disables the -acceleration effect. +acceleration effect. .El .Sh IOCTLS -There are a few +There are a few .Xr ioctl 2 -commands for mouse drivers. +commands for mouse drivers. These commands and related structures and constants are defined in .Ao Pa sys/mouse.h Ac . General description of the commands is given in @@ -167,7 +167,7 @@ These commands manipulate the operation level of the driver. .Pp .It Dv MOUSE_GETHWINFO Ar mousehw_t *hw -Returns the hardware information of the attached device in the following +Returns the hardware information of the attached device in the following structure. Only the .Dv iftype @@ -192,7 +192,7 @@ field holds the number of buttons on the device. The .Dv iftype is either -.Dv MOUSE_IF_BUS +.Dv MOUSE_IF_BUS or .Dv MOUSE_IF_INPORT . .Pp @@ -211,9 +211,9 @@ The is always .Dv MOUSE_MODEL_GENERIC at the operation level 0. -It may be +It may be .Dv MOUSE_MODEL_GENERIC -or one of +or one of .Dv MOUSE_MODEL_XXX constants at higher operation levels. .Pp @@ -248,9 +248,9 @@ at the operation level one. .Pp The .Dv rate -is the status report rate (reports/sec) at which the device will send +is the status report rate (reports/sec) at which the device will send movement report to the host computer. -As there is no standard to detect the current setting, +As there is no standard to detect the current setting, this field is always set to -1. .Pp The @@ -259,7 +259,7 @@ is always set to -1. .Pp The .Dv accelfactor -field holds a value to control acceleration feature +field holds a value to control acceleration feature .Pq see Sx Acceleration . It is zero or greater. If it is zero, acceleration is disabled. @@ -290,8 +290,8 @@ Note that this detection method is not 100% reliable, thus, should be taken only as an advisory measure. .Pp Only -.Dv level -and +.Dv level +and .Dv accelfactor are modifiable by the .Dv MOUSE_SETMODE @@ -303,8 +303,8 @@ The command changes the current operation parameters of the mouse driver as specified in .Ar mode . Only -.Dv level -and +.Dv level +and .Dv accelfactor may be modifiable. Setting values in the other field does not generate @@ -323,7 +323,7 @@ These commands are not supported by the driver. .Pp .It Dv MOUSE_GETSTATUS Ar mousestatus_t *status -The command returns the current state of buttons and +The command returns the current state of buttons and movement counts as described in .Xr mouse 4 . .El @@ -341,18 +341,18 @@ movement counts as described in .Sh EXAMPLES .Dl "device mse0 at isa? port 0x23c irq 5" .Pp -Add the +Add the .Nm driver at the primary port address with the IRQ 5. .Pp .Dl "device mse1 at isa? port 0x238 flags 0x30 irq 4" .Pp -Define the +Define the .Nm driver at the secondary port address with the IRQ 4 and the acceleration factor of 3. .Sh CAVEAT -Some bus mouse interface cards generate interrupts at the fixed report rate +Some bus mouse interface cards generate interrupts at the fixed report rate when enabled, whether or not the mouse state is changing. The others generate interrupts only when the state is changing. .Sh SEE ALSO diff --git a/share/man/man4/man4.i386/npx.4 b/share/man/man4/man4.i386/npx.4 index e2504ae..4ad4041 100644 --- a/share/man/man4/man4.i386/npx.4 +++ b/share/man/man4/man4.i386/npx.4 @@ -64,7 +64,7 @@ of whether or not a NPX is present. .Pp If there is no NPX present in the system, the MATH_EMULATE or GPL_MATH_EMULATE option must be defined in the kernel configuration -file. +file. It will provide support for the instructions normally executed by the NPX. If there is no NPX in the system and the kernel is not built with math @@ -92,7 +92,7 @@ support a system with normal workload unless care is taken to compile the whole system (including third-party packages) with compiler options that avoid the use of the non-emulated instructions. .Sh BUGS -There are lots of them, especially on old cheap motherboards. +There are lots of them, especially on old cheap motherboards. In particular, some motherboards do not have the interrupt lines from the NPX to the CPU wired properly. If this is the case, the emulator must be used if consistent system diff --git a/share/man/man4/man4.i386/pcf.4 b/share/man/man4/man4.i386/pcf.4 index b1d33e2..ed61869 100644 --- a/share/man/man4/man4.i386/pcf.4 +++ b/share/man/man4/man4.i386/pcf.4 @@ -43,9 +43,9 @@ driver provides support to the Philips PCF8584 I2C controller for the system. .Pp The PCF8584 is an integrated circuit designed in CMOS technology which serves -as an interface between most standard parallel-bus +as an interface between most standard parallel-bus microcontrollers/microprocessors and the serial I2C-bus. -The PCF8584 +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. diff --git a/share/man/man4/man4.i386/perfmon.4 b/share/man/man4/man4.i386/perfmon.4 index c1fccbd..d4f15f9 100644 --- a/share/man/man4/man4.i386/perfmon.4 +++ b/share/man/man4/man4.i386/perfmon.4 @@ -12,7 +12,7 @@ .\" no representations about the suitability of this software for any .\" purpose. It is provided "as is" without express or implied .\" warranty. -.\" +.\" .\" THIS SOFTWARE IS PROVIDED BY M.I.T. ``AS IS''. M.I.T. DISCLAIMS .\" ALL EXPRESS OR IMPLIED WARRANTIES WITH REGARD TO THIS SOFTWARE, .\" INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF diff --git a/share/man/man4/man4.i386/pnp.4 b/share/man/man4/man4.i386/pnp.4 index 8e32dfa..5f3997d 100644 --- a/share/man/man4/man4.i386/pnp.4 +++ b/share/man/man4/man4.i386/pnp.4 @@ -97,7 +97,7 @@ another device with a different CSN/LDN pair. Sets the value of a 32-bit flags entry which is passed to the device driver. This can be used to set special operation modes (e.g. SB vs. WSS -emulation on some sound cards, etc.). +emulation on some sound cards, etc.). .El .Pp The current content of the table can be printed using the @@ -115,7 +115,7 @@ command. PnP devices are automatically recognized and configured by the kernel. A PnP device is identified by the following data structure: .Bd -literal -struct pnp_device { +struct pnp_device { char *pd_name; char *(*pd_probe ) (u_long csn, u_long vendor_id); void (*pd_attach ) (u_long csn, u_long vend_id, char * name, diff --git a/share/man/man4/man4.i386/ray.4 b/share/man/man4/man4.i386/ray.4 index 4994a4f..68df8f5 100644 --- a/share/man/man4/man4.i386/ray.4 +++ b/share/man/man4/man4.i386/ray.4 @@ -192,7 +192,7 @@ of the output from .Pp The following messages are enabled using the .Cm debug -option of +option of .Xr ifconfig 8 . .Bl -diag .It "ray?: cannot transmit - not running" @@ -316,7 +316,7 @@ The NIC has generated an interrupt with an incorrect control block. .It "ray?: unexpected SHUTDOWN" .It "ray?: unexpected DUMP_MEM" .It "ray?: unexpected START_TIMER" -The NIC has generated an interrupt signalling that +The NIC has generated an interrupt signalling that the indicated command has completed. At present these commands are never issued by the driver, so they represent firmware/hardware/driver bugs. @@ -341,7 +341,7 @@ Benign warning that may occur when the NIC is ejected. .El .Sh SEE ALSO .Xr arp 4 , -.Xr netintro 4 , +.Xr netintro 4 , .Xr ifconfig 8 , .Xr pccardd 8 , .Xr raycontrol 8 @@ -360,7 +360,7 @@ driver by .An "Christian E. Hopps" . The driver was re-structured by -.An Duncan Barclay Aq dmlb@FreeBSD.org , +.An Duncan Barclay Aq dmlb@FreeBSD.org , so that .Xr dhclient 8 would work. diff --git a/share/man/man4/man4.i386/sb.4 b/share/man/man4/man4.i386/sb.4 index 8fc9a4b..b1b9c7f 100644 --- a/share/man/man4/man4.i386/sb.4 +++ b/share/man/man4/man4.i386/sb.4 @@ -5,10 +5,10 @@ .\" This documentation is public domain, and is provided without warranty. .\" Alex Zepeda, the "author" of this page is not responsible for any .\" consequences of any sort of manipulation of this document. -.\" +.\" .\" SoundBlaster and any phrases including it's name are copyright .\" Creative Labs, not me. -.\" +.\" .\" alex!@bigfoot.com .\" $FreeBSD$ .\" @@ -65,11 +65,11 @@ the device. Support for this feature may be implemented in a future version of this driver. .Sh SEE ALSO -.Xr cdcontrol 1 , +.Xr cdcontrol 1 , .Xr mixer 8 .Sh AUTHORS .An -nosplit -The original SoundBlaster DSP and SoundBlaster 16 MIDI, and Yamaha OPL-3 +The original SoundBlaster DSP and SoundBlaster 16 MIDI, and Yamaha OPL-3 drivers were written by .An Hannu Savolainen . The SoundBlaster 16 DSP code was written by diff --git a/share/man/man4/man4.i386/spkr.4 b/share/man/man4/man4.i386/spkr.4 index b2775fd..6cd8c557 100644 --- a/share/man/man4/man4.i386/spkr.4 +++ b/share/man/man4/man4.i386/spkr.4 @@ -149,22 +149,22 @@ Sets the number of quarter notes per minute; default is 120. Musical names for common tempi are: .Bd -literal -offset indent Tempo Beats Per Minute -very slow Larghissimo +very slow Larghissimo Largo 40-60 Larghetto 60-66 - Grave - Lento + Grave + Lento Adagio 66-76 -slow Adagietto +slow Adagietto Andante 76-108 -medium Andantino +medium Andantino Moderato 108-120 -fast Allegretto +fast Allegretto Allegro 120-168 - Vivace - Veloce + Vivace + Veloce Presto 168-208 -very fast Prestissimo +very fast Prestissimo .Ed .It Li M[LNS] Set articulation. diff --git a/share/man/man4/man4.i386/streams.4 b/share/man/man4/man4.i386/streams.4 index 6860ad0..0530342 100644 --- a/share/man/man4/man4.i386/streams.4 +++ b/share/man/man4/man4.i386/streams.4 @@ -47,27 +47,27 @@ for userland applications. .Pp Internally, .Nm -provides STREAMS handles by using socket creation kernel routines, and +provides STREAMS handles by using socket creation kernel routines, and adding state-tracking information to the socket to permit manipulation by STREAMS emulation code in .Xr svr4 4 . -Hence, opening a stream device produces a result similar to what would be +Hence, opening a stream device produces a result similar to what would be obtained by calling .Xr socket 2 . .Pp Applications should never use this interface directly: STREAMS emulation is only provided as a service to support ABI requirements in -the SVR4 environment which +the SVR4 environment which .Xr svr4 4 -needs to present to client binaries. +needs to present to client binaries. .Sh BUGS This whole interface is a crude hack to produce STREAMS semantics -through emulation over sockes. +through emulation over sockes. .Pp -Programmers who hope to be able to use this interface to provide +Programmers who hope to be able to use this interface to provide SVR4 STREAMS services to BSD applications will be sorely disappointed. .Sh SEE ALSO -.Xr svr4 4 +.Xr svr4 4 .Sh HISTORY System V Release 4 ABI support first appeared in .Fx 4.0 . diff --git a/share/man/man4/man4.i386/svr4.4 b/share/man/man4/man4.i386/svr4.4 index a9d9d85..08a04fb 100644 --- a/share/man/man4/man4.i386/svr4.4 +++ b/share/man/man4/man4.i386/svr4.4 @@ -74,25 +74,25 @@ implementation is provided. .Sh LIMITATIONS Because the provided ABI has been developed in ignorance of actual SVR4 source code, there are bound to be unforseen interactions between SVR4 -client applications and the emulated ABI which cause applications to -malfunction. +client applications and the emulated ABI which cause applications to +malfunction. .Pp Additionally, some SVR4 operating systems do not adhere to the SVR4 ELF standard. In particular, Solaris does not set the ELF interpreter field in the -ELF header to a value which would allow the kernel to correctly +ELF header to a value which would allow the kernel to correctly identify a client executable as an SVR4 application. -Thus, in certain instances it is necessary to use the +Thus, in certain instances it is necessary to use the .Xr brandelf 1 utility to explicitly brand the executable, or to set the kern.fallback_elf_brand .Xr sysctl 8 -variable to define a "default" ABI for unbranded executables. +variable to define a "default" ABI for unbranded executables. Value ELFOSABI_SOLARIS represents Solaris; ELFOSABI_SYSV represents other SysVR4 operating systems. -See +See .Pa /usr/include/sys/elf_common.h -for ELFOSABI branding definitions, and +for ELFOSABI branding definitions, and .Xr brandelf 1 for information on branding executables. .Pp @@ -131,22 +131,22 @@ regardless of whether the module is statically linked into the kernel or loaded as a module. .Pp -STREAMS emulation is limited but (largely) functional. +STREAMS emulation is limited but (largely) functional. Assuming the .Xr streams 4 -module is loaded, a STREAMS handle can be obtained by opening one of the +module is loaded, a STREAMS handle can be obtained by opening one of the relevent files in .Pa /dev -or +or .Pa /compat/svr4/dev . -Internally, the +Internally, the .Xr streams 4 driver produces a socket descriptor and "tags" it with additional STREAMS -state information before returning it to the client application. +state information before returning it to the client application. The .Nm -environment uses the additional state information to recognize and -manipulate emulated STREAMS handles when STREAMS-specific +environment uses the additional state information to recognize and +manipulate emulated STREAMS handles when STREAMS-specific .Xr ioctl 2 calls are executed. .Pp @@ -160,7 +160,7 @@ Emulated connectionless STREAMS fail to receive data from the network in some circumstances (but succeed in others -- probably due to particular ways of initializing them which the .Xr streams 4 -module is mishandling, and interaction between STREAMS and +module is mishandling, and interaction between STREAMS and .Xr poll 2 ) . Connection-oriented STREAMS appear to be functional. .Pp @@ -168,7 +168,7 @@ Ironically, this SVR4 emulator does not (yet) support SVR4 semaphores or shared memory. .Pp .Xr ports 7 -to automatically create the +to automatically create the .Pa /compat/svr4 environment do not exist. .Xr tar 1 @@ -178,9 +178,9 @@ archives containing pre-populated trees can be obtained from Extensive testing has only really been carried out with Solaris 2.x binaries, with anecdotal reports of limited success coming from testers with early-revision SCO media. In theory, the basic SVR4 ABI should be constant -across the set of vendors who produce SVR4 operating systems, but in -practice that's probably not the case. If necessary, future work can -either implement additional +across the set of vendors who produce SVR4 operating systems, but in +practice that's probably not the case. If necessary, future work can +either implement additional .Xr kld 4 modules which produce functionality which contains OS-dependent departures from the behaviour which has been implemented in this @@ -194,7 +194,7 @@ client applications. .It Pa /compat/svr4 minimal SVR4 run-time environment .It Pa /sys/compat/svr4/syscalls.master -mappings between SVR4 syscalls and +mappings between SVR4 syscalls and .Nm module entrypoints. .El diff --git a/share/man/man4/man4.i386/tx.4 b/share/man/man4/man4.i386/tx.4 index 8a37970..2b8438b 100644 --- a/share/man/man4/man4.i386/tx.4 +++ b/share/man/man4/man4.i386/tx.4 @@ -81,7 +81,7 @@ Device and driver reset follows this error. 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. +While reseting, driver failed to stop device correctly. .El .Sh BUGS The multicast packets filtering is not supported. diff --git a/share/man/man4/man4.i386/vx.4 b/share/man/man4/man4.i386/vx.4 index db0978c..c43cf64 100644 --- a/share/man/man4/man4.i386/vx.4 +++ b/share/man/man4/man4.i386/vx.4 @@ -72,7 +72,7 @@ a test for it based on the information supplied by 3Com, but the test resulted mostly in spurious warnings. .Pp 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 +only polled-mode I/O and does not make use of the bus-mastering capability of the cards. .Sh BUGS The diff --git a/share/man/man4/man4.i386/wd.4 b/share/man/man4/man4.i386/wd.4 index 8d67a12..e9e64ab 100644 --- a/share/man/man4/man4.i386/wd.4 +++ b/share/man/man4/man4.i386/wd.4 @@ -40,10 +40,10 @@ This driver provides access to disks connected to controllers that emulate the Western Digital WD100x series. This range of controllers includes WD1003 -type ST412 controllers, WD1007 ESDI controllers and also the generic IDE +type ST412 controllers, WD1007 ESDI controllers and also the generic IDE controllers found on most motherboards. .Pp -Your controller documentation is usually quick to point out any WD100x +Your controller documentation is usually quick to point out any WD100x compatibility. .Pp You can convey a number of hints and instructions to the driver using @@ -56,7 +56,7 @@ For each drive there are six bit-fields encoded in a 16 bit integer: .It 0x8000 Test and use the 32bit transfer capability of the drive. .It 0x4000 -If drive looks like it's coming out of sleep mode, assume it's +If drive looks like it's coming out of sleep mode, assume it's confused and reinitialize it. .It 0x2000 Probe for and use the bus-mastering DMA capabilities of modern diff --git a/share/man/man4/man4.i386/wl.4 b/share/man/man4/man4.i386/wl.4 index 982084b..320ba8a 100644 --- a/share/man/man4/man4.i386/wl.4 +++ b/share/man/man4/man4.i386/wl.4 @@ -47,29 +47,29 @@ about 400 feet (indoors, more outdoors) can be covered in circumference. This card can talk to the companion (wlp0) pccard. Speeds vary from 1 megabit to theoretically 2 megabits (roughly T1 in speed). .Pp -The card has three fundamental hardware +The card has three fundamental hardware units, a so-called PSA or programmable storage area, a radio modem, -and a ethernet lan controller. The latter component is the +and a ethernet lan controller. The latter component is the ancient (and not very honorable) Intel 82586 ethernet chip. Fundamentally it appears to the operating system as an ethernet system, and speaks IEEE MAC addresses. The radio modem simply translates ethernet packets to/from radio packets, that are either at 2.4 Ghz or 915 mhz depending on the radio modem. It supports a collision avoidance scheme. The lan controller -supports promiscuous mode, broadcast, and multicasting +supports promiscuous mode, broadcast, and multicasting (although there is a glitch -in the latter). "It thinks it is ethernet". -.Pp +in the latter). "It thinks it is ethernet". +.Pp How it is used depends on the kind of antennae deployed with it. Point to point applications are possible as are ethernet-like lan use. The vendor -ships an omni-directional antennae that works in the +ships an omni-directional antennae that works in the vicinity of 400 feet (indoors). Point to point antennae can be purchased that will go miles. .Sh SETUP The card can either be initialized with the vendor supplied DOS setup software. Typically minimally an IRQ, port, and Network ID must be supplied. -Michael Smith's +Michael Smith's .Xr wlconfig 8 utility can now be used to do this work from the UNIX side. The card is "not" plug and play. @@ -79,7 +79,7 @@ by the radio modem. .Sh CONTROL In addition to the config utility, there are several sysctl switches that can be used to modify runtime parameters. -The +The .Xr sysctl 8 variables are as follows: .Bl -diag @@ -94,9 +94,9 @@ This switch defaults to 0; i.e., the nwid is not ignored. It can be set to 1 to cause the nwid to not be used. This may be useful when the device is in promiscuous mode as one can watch for all packets and ignore nwid differences. -.It machdep.wl_xmit_watch <milliseconds> +.It machdep.wl_xmit_watch <milliseconds> This switch is not currently useful. -.It machdep.wl_gather_snr <milliseconds> +.It machdep.wl_gather_snr <milliseconds> This switch is not currently useful. .Pp There is also a signal strength cache in the driver. It may be interrogated @@ -105,12 +105,12 @@ with Incoming packets are checked for certain hardware radio-modem values including signal strength, silence, and quality, which range fro 0..63, 0..63, and 0..15 -respectively. Thus one can read out signal strenth values to see -how close/far peer nodes are. The signal strength cache is indexed by +respectively. Thus one can read out signal strenth values to see +how close/far peer nodes are. The signal strength cache is indexed by 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> +.It machdep.wl_wlcache_mcastonly <0 | 1> By default this switch is on. It forces the cache to filter out unicast packets. Only broadcast or multicast packets are accepted. diff --git a/share/man/man4/man4.i386/wt.4 b/share/man/man4/man4.i386/wt.4 index 8e726a2..dbe8391 100644 --- a/share/man/man4/man4.i386/wt.4 +++ b/share/man/man4/man4.i386/wt.4 @@ -9,7 +9,7 @@ .\" notice, this list of conditions and the following disclaimer. .\" 2. The name of the author may not be used to endorse or promote products .\" derived from this software without specific prior written permission -.\" +.\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. @@ -25,7 +25,7 @@ .\" .Dd July 10, 1995 .Dt WT 4 i386 -.Os +.Os .Sh NAME .Nm wt .Nd Archive/Wangtek cartridge tape driver @@ -38,9 +38,9 @@ driver provides support for the following Archive and Wangtek boards: .Pp .Bl -item -offset indent -compact .It -QIC-02 +QIC-02 .It -QIC-36 +QIC-36 .El .Sh SEE ALSO .Xr intro 4 |
