New sentence, new line.

This commit is contained in:
wiz 2011-04-05 08:24:43 +00:00
parent 1cd1da49e9
commit b351288a9a
10 changed files with 96 additions and 70 deletions

View File

@ -24,7 +24,7 @@
.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $NetBSD: apm.4,v 1.17 2003/06/27 18:27:58 wiz Exp $
.\" $NetBSD: apm.4,v 1.18 2011/04/05 08:24:43 wiz Exp $
.\"
.Dd May 18, 1996
.Dt APM 4 i386
@ -41,7 +41,8 @@ Advanced Power Management pseudo-device driver
The
.Nm apm
driver provides support for the Advanced Power Management features of
some i386 system BIOSes. The driver supports the Advanced Power
some i386 system BIOSes.
The driver supports the Advanced Power
Management (APM) BIOS Interface Specification (revision 1.2), published
jointly by the Intel Corporation and the Microsoft Corporation.
.Pp
@ -49,13 +50,14 @@ The APM driver's behavior may be adjusted by specifying any of the
following kernel configuration options:
.Bl -tag -width indent -compact
.It Dv APM_NO_IDLE
Do not call the BIOS CPU idle function from the system idle loop. (Some
systems will hang on certain device accesses, such as sound cards or
floppy diskette drives, without this option)
Do not call the BIOS CPU idle function from the system idle loop.
(Some systems will hang on certain device accesses, such as sound
cards or floppy diskette drives, without this option)
.It Dv APM_V10_ONLY
Use only the APM revision 1.0 specification calls. (Some systems do not
implement APM v1.1 very well, and generate weird events instead of the
expected events when the system suspend key is pressed.)
Use only the APM revision 1.0 specification calls.
(Some systems do not implement APM v1.1 very well, and generate
weird events instead of the expected events when the system suspend
key is pressed.)
.It Dv APM_NO_V12
Don't attach to the BIOS as APM v1.2 compliant device.
(In case there are problems with v1.2 support.)
@ -74,32 +76,38 @@ Enable kernel printout of every call to the APM BIOS (this is very noisy).
.It Dv APM_POWER_PRINT
Print power state on console at
.Dv APM_POWER_CHANGE
events. (Since it increases
events.
(Since it increases
.Xr syslogd 8 Ns 's
activity, it may consume increased
battery power. Some systems generate the events too frequently,
activity, it may consume increased battery power.
Some systems generate the events too frequently,
and printing the status may disturb single-user operations.)
.It Dv APM_DISABLE_INTERRUPTS
Set this to zero if you don't want the kernel to disable interrupts
before calling the BIOS. This is required for most IBM ThinkPads, and
some other newer laptops. A good indication that you need this is that
the machine hangs just after resuming from suspended state. It's
unclear if doing this has negative effects on older BIOS, therefore it
before calling the BIOS.
This is required for most IBM ThinkPads, and some other newer laptops.
A good indication that you need this is that
the machine hangs just after resuming from suspended state.
It's unclear if doing this has negative effects on older BIOS, therefore it
defaults to one (i.e interrupts are disabled).
.El
.Pp
If no processes are holding open file descriptors to the APM device, the
driver will process the APM BIOS events itself. If a process has the
driver will process the APM BIOS events itself.
If a process has the
device open for write, the driver defers all suspend and standby
processing to the user process as long as there is sufficient queue
space to store the event for the process. If the device is only open
space to store the event for the process.
If the device is only open
for read, the driver will report events but handle them itself.
.Pp
The APM device may be opened by multiple readers but only one
writer. Multiple readers may fetch the status with
writer.
Multiple readers may fetch the status with
.Xr ioctl 2
without worrying about interference, but they must cooperate to share
events as only a single event queue is provided. The device may only be
events as only a single event queue is provided.
The device may only be
.Xr select 2 Ns ed
or manipulated with
.Xr ioctl 2 ;
@ -112,12 +120,14 @@ The
calls supported are:
.Bl -tag -width indent -compact
.It Dv APM_IOC_SUSPEND
Initiate an APM suspend mode. This is a deep sleep mode which powers down
most devices. The device must be open for writing for this command to succeed.
Initiate an APM suspend mode.
This is a deep sleep mode which powers down most devices.
The device must be open for writing for this command to succeed.
.It Dv APM_IOC_STANDBY
Initiate an APM standby mode. This is a light sleep mode from which the
system can quickly restore normal operation. The device must be open
for writing for this command to succeed.
Initiate an APM standby mode.
This is a light sleep mode from which the
system can quickly restore normal operation.
The device must be open for writing for this command to succeed.
.It Dv APM_IOC_GETPOWER
Fetch the current power status into an
.Va apm_power_info
@ -166,8 +176,8 @@ is an estimated remaining lifetime (or 0 if the BIOS cannot provide an
estimate).
.Pp
.Va nbattery
is the number of batteries in the system. If the system is using APM
v1.1 or earlier, nbattery will always return 0.
is the number of batteries in the system.
If the system is using APM v1.1 or earlier, nbattery will always return 0.
.Pp
Batteries are numbered from a base of 1.
If the passed value of
@ -191,7 +201,8 @@ is always set to the passed value upon return.
.It Dv APM_IOC_NEXTEVENT
Fetch the next event from the APM BIOS into an
.Va apm_event_info
structure. If no more events are ready, this will return
structure.
If no more events are ready, this will return
.Dv EAGAIN .
.Bd -literal
struct apm_event_info {
@ -210,8 +221,8 @@ is the ordinal event sequence number.
.Xr apmd 8
.Sh REFERENCES
Advanced Power Management (APM) BIOS Interface Specification (Revision
1.1), Intel Corporation and Microsoft Corporation. Intel order number
241704-001; Microsoft part number 781-110-X01.
1.1), Intel Corporation and Microsoft Corporation.
Intel order number 241704-001; Microsoft part number 781-110-X01.
.Sh HISTORY
The
.Nm apm

View File

@ -1,4 +1,4 @@
.\" $NetBSD: autoconf.4,v 1.9 2005/06/20 13:25:24 peter Exp $
.\" $NetBSD: autoconf.4,v 1.10 2011/04/05 08:24:43 wiz Exp $
.\"
.\" Copyright (c) 1994 Christopher G. Demetriou
.\" All rights reserved.
@ -44,7 +44,8 @@ When
bootstraps it probes the innards of the machine
on which it is running
and locates controllers, drives, and other devices, printing out
what it finds on the console. This procedure is driven by a system
what it finds on the console.
This procedure is driven by a system
configuration table which is processed by
.Xr config 1
and compiled into each kernel.

View File

@ -1,4 +1,4 @@
.\" $NetBSD: console.4,v 1.11 2009/03/09 19:24:29 joerg Exp $
.\" $NetBSD: console.4,v 1.12 2011/04/05 08:24:43 wiz Exp $
.\"
.Dd September 6, 2006
.Dt CONS 4 i386
@ -61,7 +61,8 @@ The available
options are:
.Bl -ohang
.It Cd options CONSDEVNAME=string
specifies the name of the console device. Valid values are
specifies the name of the console device.
Valid values are
.Dq pc
for the pc keyboard / display (default)
and
@ -74,15 +75,18 @@ sets the baudrate for the serial console (default: 9600).
.It Cd options CONS_OVERRIDE
causes console information passed by the bootloader to be ignored and
the settings specified by the three options above (or the defaults) to be
used. Default behaviour is to use the settings from the bootloader if
used.
Default behaviour is to use the settings from the bootloader if
present, and to use option / default values only if no information was
passed.
.It Cd options CONMODE=integer
allows to specify terminal control flags. The argument is a
allows to specify terminal control flags.
The argument is a
.Dq cflag
value, see
.Xr termios 4
for details. Default is
for details.
Default is
.Li (CREAD | CS8 | HUPCL)
(8N1).
This option takes always effect, because mode settings are not passed
@ -105,7 +109,8 @@ The console device is chosen early in system startup regardless
if the specified driver / device is present in the system configuration file.
If the driver asked for by the bootloader or
.Dq Cd options CONSDEVNAME
is not configured into the system, a panic is caused. Because there is
is not configured into the system, a panic is caused.
Because there is
no console device, no explaining message will be printed.
If the driver is present, but the specific device instance not, kernel
printf will work, but

View File

@ -1,4 +1,4 @@
.\" $NetBSD: elanpex.4,v 1.4 2009/10/19 23:19:38 rmind Exp $
.\" $NetBSD: elanpex.4,v 1.5 2011/04/05 08:24:43 wiz Exp $
.\"
.\"
.\" Copyright (c) 2008 David Young. All rights reserved.
@ -82,7 +82,7 @@ Failures may occur for the following reasons:
.It elanpex0: %s %x target data parity
.El
.Pp
Transaction types are alike to failed master exceptions.
Transaction types are alike to failed master exceptions.
.El
.Sh SEE ALSO
.Xr dmesg 8 ,

View File

@ -1,4 +1,4 @@
.\" $NetBSD: fdc.4,v 1.14 2010/03/22 18:58:31 joerg Exp $
.\" $NetBSD: fdc.4,v 1.15 2011/04/05 08:24:43 wiz Exp $
.\"
.\" Copyright (c) 1996, 1997 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -64,7 +64,8 @@ The driver supports floppy disk formatting using the interfaces in
.In sys/fdio.h :
.Bl -tag -width FDIOCFORMAT_TRACK -compact
.It Dv FDIOCGETFORMAT Fa struct fdformat_parms
Fetch current formatting parameters. This gets the default parameters
Fetch current formatting parameters.
This gets the default parameters
for the open device if no parameters have been set during the session.
.It Dv FDIOCSETFORMAT Fa struct fdformat_parms
Set formatting parameters.
@ -78,8 +79,8 @@ If it returns
.Er EIO ,
there was a medium error while formatting the track.
.It Dv FDIOCSETOPTS Fa int
Set driver options which persist until the device is closed. The
options should be the logical OR of the desired values below:
Set driver options which persist until the device is closed.
The options should be the logical OR of the desired values below:
.Bl -tag -width FDOPT_NORETRY -compact
.It Dv FDOPT_NORETRY
Do not retry operations on failure

View File

@ -1,4 +1,4 @@
.\" $NetBSD: intro.4,v 1.26 2005/06/20 13:25:24 peter Exp $
.\" $NetBSD: intro.4,v 1.27 2011/04/05 08:24:43 wiz Exp $
.\"
.\" Copyright (c) 1997 Jonathan Stone
.\" Copyright (c) 1994 Christopher G. Demetriou
@ -68,8 +68,8 @@ The networking support is introduced in
.Sh DEVICE SUPPORT
This section describes the hardware supported on the i386
(PC-clone) platform.
Software support for these devices comes in two forms. A hardware
device may be supported with a character or block
Software support for these devices comes in two forms.
A hardware device may be supported with a character or block
.Em device driver ,
or it may be used within the networking subsystem and have a
.Em network interface driver .
@ -82,7 +82,8 @@ communication facilities provided by the system; see
.Pp
A hardware device is identified to the system at configuration time
and the appropriate device or network interface driver is then compiled
into the system. When the resultant system is booted, the
into the system.
When the resultant system is booted, the
autoconfiguration facilities in the system probe for the device
and, if found, enable the software support for it.
If a device does not respond at autoconfiguration
@ -95,7 +96,8 @@ The autoconfiguration system is described in
A list of the supported devices is given below.
.Sh LIST OF DEVICES
The devices listed below are supported in this incarnation of
the system. Devices are indicated by their functional interface.
the system.
Devices are indicated by their functional interface.
Not all supported devices are listed.
.\"
.\"
@ -184,14 +186,14 @@ Symbios (formerly NCR) PCI SCSI adapter boards.
.It pciide
PCI IDE controllers.
.It sea
Seagate/Future Domain SCSI cards. ST01/02, Future Domain TMC-885, and
Future Domain TMC-950.
Seagate/Future Domain SCSI cards.
ST01/02, Future Domain TMC-885, and Future Domain TMC-950.
.It uha
Ultrastor ISA and EISA SCSI adapter cards. Ultrastore 14f, Ultrastore 34f,
and Ultrastore 24f.
Ultrastor ISA and EISA SCSI adapter cards.
Ultrastore 14f, Ultrastore 34f, and Ultrastore 24f.
.It wdc
Standard ISA Western Digital type hard drives controllers. MFM, RLL, ESDI, and
IDE.
Standard ISA Western Digital type hard drives controllers.
MFM, RLL, ESDI, and IDE.
.It wt
Wangtek and compatible ISA controllers for QIC-02 and QIC-36 tapes.
.El

View File

@ -1,4 +1,4 @@
.\" $NetBSD: lpt.4,v 1.20 2009/03/23 16:05:53 joerg Exp $
.\" $NetBSD: lpt.4,v 1.21 2011/04/05 08:24:43 wiz Exp $
.\"
.\" Copyright (c) 1993 Christopher G. Demetriou
.\" All rights reserved.
@ -48,8 +48,9 @@ Parallel port driver
.Cd "lpt* at pnpbios? index ?"
.Cd "lpt* at puc? port ?"
.Sh DESCRIPTION
This driver provides access to parallel ports. The bits in the minor
number select various features of the driver. If no IRQ is
This driver provides access to parallel ports.
The bits in the minor number select various features of the driver.
If no IRQ is
specified in the kernel configuration, only the polling device may be used.
.Pp
.Bl -column "Minor Bit" "Functionxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -offset indent

View File

@ -1,4 +1,4 @@
.\" $NetBSD: pcibios.4,v 1.17 2009/11/02 00:50:29 joerg Exp $
.\" $NetBSD: pcibios.4,v 1.18 2011/04/05 08:24:43 wiz Exp $
.\"
.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -47,7 +47,8 @@ using information extracted from the BIOS.
.Pp
Ideally, the boot firmware of a machine (a.k.a. BIOS) should set
up all PCI devices; assigning them I/O and memory addresses and
interrupts. Alas, this does not always happen, so there is some
interrupts.
Alas, this does not always happen, so there is some
PC specific code that can do the initialization when
.Nx
boots.
@ -60,7 +61,7 @@ turn on the PCI BIOS support.
make the setup procedure verbose.
.It Nm PCIBIOS_IRQS_HINT
hint for IRQ use.
When
When
.Em PCI_INTR_FIXUP
cannot guess an adequate IRQ for a device, the hint is used.
.Pp
@ -108,9 +109,10 @@ prompt:
.It Nm PCIBIOS_INTR_FIXUP_FORCE
Some buggy BIOS implementations provide inconsistent
information between the PCI Interrupt Configuration Register
and the PCI Interrupt Routing table. In such case,
the PCI Interrupt Configuration Register takes precedence
by default. If this happens, a kernel with
and the PCI Interrupt Routing table.
In such case, the PCI Interrupt Configuration Register takes precedence
by default.
If this happens, a kernel with
.Em PCIBIOSVERBOSE
shows
.Qq Sy WARNING: preserving irq XX

View File

@ -1,4 +1,4 @@
.\" $NetBSD: pnpbios.4,v 1.12 2008/04/30 13:10:56 martin Exp $
.\" $NetBSD: pnpbios.4,v 1.13 2011/04/05 08:24:43 wiz Exp $
.\"
.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -103,7 +103,8 @@ bus provides a different way to attach devices than the real buses
The reason to use
.Nm
instead of the real bus is that some machines have weird routings
of, e.g., interrupts. The exact information about these things can
of, e.g., interrupts.
The exact information about these things can
be found in the BIOS, which is why the
.Nm
bus has a better chance of succeeding with getting it right.

View File

@ -1,4 +1,4 @@
.\" $NetBSD: spic.4,v 1.3 2008/04/30 13:10:56 martin Exp $
.\" $NetBSD: spic.4,v 1.4 2011/04/05 08:24:43 wiz Exp $
.\"
.\" Copyright (c) 2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -37,7 +37,8 @@
Some
.Tn Sony
computers have an I/O controller that handles various interface
devices, e.g., the jog dial. The
devices, e.g., the jog dial.
The
.Nm
driver provides support for some of these.
.Pp
@ -48,10 +49,11 @@ been tested on the Vaio SRX77.
.Pp
The
.Nm
driver handles the jog dial and its associated buttons. They are turned
into a
driver handles the jog dial and its associated buttons.
They are turned into a
.Nm wsmouse
which can the be accessed in the normal way. The jog dial works as a
which can the be accessed in the normal way.
The jog dial works as a
scroll button, and clicking it generates a click with the "middle" button.
.Sh SEE ALSO
.Xr acpi 4 ,