diff options
author | jkoshy <jkoshy@FreeBSD.org> | 1999-09-30 09:35:54 +0000 |
---|---|---|
committer | jkoshy <jkoshy@FreeBSD.org> | 1999-09-30 09:35:54 +0000 |
commit | c51c3d7fcd40066e9098227c51ffd2c6ae0cdb4a (patch) | |
tree | 50bff2acdd12692b6054b7e70915297752fe1ecd /share | |
parent | da8f96a0d65950d56832fcb553a66e21475e596e (diff) | |
download | FreeBSD-src-c51c3d7fcd40066e9098227c51ffd2c6ae0cdb4a.zip FreeBSD-src-c51c3d7fcd40066e9098227c51ffd2c6ae0cdb4a.tar.gz |
Correct typos and -mdoc usage. Improve clarity of language.
PR: docs/140007
(partial)
Submitted by: Adam Wight <adamw@holonet.net>
Diffstat (limited to 'share')
-rw-r--r-- | share/man/man4/man4.i386/ppc.4 | 41 | ||||
-rw-r--r-- | share/man/man4/ppc.4 | 41 |
2 files changed, 52 insertions, 30 deletions
diff --git a/share/man/man4/man4.i386/ppc.4 b/share/man/man4/man4.i386/ppc.4 index 1040e8d..e153ad7 100644 --- a/share/man/man4/man4.i386/ppc.4 +++ b/share/man/man4/man4.i386/ppc.4 @@ -38,19 +38,27 @@ For one or more PPBUS busses: .Cd "controller ppbus at ppc0" .Sh DESCRIPTION The -.Em ppc +.Nm driver provides low level support to various parallel port chipsets for the .Xr ppbus 4 system. .Pp -During the probe phasis, ppc detects parallel port chipsets and initialize +During the probe phase, +.Nm +detects parallel port chipsets and initializes private data according to their operating mode: COMPATIBLE, -NIBBLE, PS/2, EPP, ECP and other mixed modes. If a mode is provided at startup -throw the flags variable of the boot interface, the operating mode of the -chipset is forced according to 'flags' and its available modes. +NIBBLE, PS/2, EPP, ECP and other mixed modes. +If a mode is provided at startup through the +.Va flags +variable of the boot +interface, the operating mode of the chipset is forced according to +.Va flags +and the hardware supported modes. .Pp -During attach phasis, ppc allocates a ppbus structure, initializes it and -calls ppbus attach function. +During the attach phase, +.Nm +allocates a ppbus structure, initializes it and calls the ppbus +attach function. .Ss Supported flags .Bl -item -offset indent .It @@ -74,8 +82,9 @@ bit 6: disable chipset specific detection bit 7: disable FIFO detection .El .Ss Supported chipsets -Some parallel port chipsets are explicitly supported by ppc: detection and -initialisation code has been written according to specs datasheets. +Some parallel port chipsets are explicitly supported: +detection and initialisation code has been written according to +their datasheets. .Bl -bullet -offset indent .It SMC FDC37C665GT and FDC37C666GT chipsets @@ -88,9 +97,10 @@ SMC-like chipsets with mixed modes (see .Xr ppbus 4 ) .El .Ss Adding support to a new chipset -You may want to add support for the newest chipset your last motherboard was -sold with? For the ISA bus, just retrieve the specs of the chipset and -write the corresponding +You may want to add support for the newest chipset your motherboard was +sold with. +For the ISA bus, just retrieve the specs of the chipset and write the +corresponding .Fn ppc_mychipset_detect "" function. Then add an entry to the general purpose @@ -99,13 +109,14 @@ function. .Pp Your .Fn ppc_mychipset_detect "" -function should ensure that: if the mode field of the +function should ensure that if the mode field of the .Va flags boot variable is not null, then the operating mode is forced to the given mode and no other mode is available and -ppb->ppb_avm field contains the available modes of the chipset +ppb->ppb_avm field contains the available modes of the chipset. .Sh SEE ALSO -.Xr ppbus 4 +.Xr ppbus 4 , +.Xr ppi 4 .Sh BUGS The chipset detection process may corrupt your chipset configuration. You may disable chipset specific detection by using the above flags. diff --git a/share/man/man4/ppc.4 b/share/man/man4/ppc.4 index 1040e8d..e153ad7 100644 --- a/share/man/man4/ppc.4 +++ b/share/man/man4/ppc.4 @@ -38,19 +38,27 @@ For one or more PPBUS busses: .Cd "controller ppbus at ppc0" .Sh DESCRIPTION The -.Em ppc +.Nm driver provides low level support to various parallel port chipsets for the .Xr ppbus 4 system. .Pp -During the probe phasis, ppc detects parallel port chipsets and initialize +During the probe phase, +.Nm +detects parallel port chipsets and initializes private data according to their operating mode: COMPATIBLE, -NIBBLE, PS/2, EPP, ECP and other mixed modes. If a mode is provided at startup -throw the flags variable of the boot interface, the operating mode of the -chipset is forced according to 'flags' and its available modes. +NIBBLE, PS/2, EPP, ECP and other mixed modes. +If a mode is provided at startup through the +.Va flags +variable of the boot +interface, the operating mode of the chipset is forced according to +.Va flags +and the hardware supported modes. .Pp -During attach phasis, ppc allocates a ppbus structure, initializes it and -calls ppbus attach function. +During the attach phase, +.Nm +allocates a ppbus structure, initializes it and calls the ppbus +attach function. .Ss Supported flags .Bl -item -offset indent .It @@ -74,8 +82,9 @@ bit 6: disable chipset specific detection bit 7: disable FIFO detection .El .Ss Supported chipsets -Some parallel port chipsets are explicitly supported by ppc: detection and -initialisation code has been written according to specs datasheets. +Some parallel port chipsets are explicitly supported: +detection and initialisation code has been written according to +their datasheets. .Bl -bullet -offset indent .It SMC FDC37C665GT and FDC37C666GT chipsets @@ -88,9 +97,10 @@ SMC-like chipsets with mixed modes (see .Xr ppbus 4 ) .El .Ss Adding support to a new chipset -You may want to add support for the newest chipset your last motherboard was -sold with? For the ISA bus, just retrieve the specs of the chipset and -write the corresponding +You may want to add support for the newest chipset your motherboard was +sold with. +For the ISA bus, just retrieve the specs of the chipset and write the +corresponding .Fn ppc_mychipset_detect "" function. Then add an entry to the general purpose @@ -99,13 +109,14 @@ function. .Pp Your .Fn ppc_mychipset_detect "" -function should ensure that: if the mode field of the +function should ensure that if the mode field of the .Va flags boot variable is not null, then the operating mode is forced to the given mode and no other mode is available and -ppb->ppb_avm field contains the available modes of the chipset +ppb->ppb_avm field contains the available modes of the chipset. .Sh SEE ALSO -.Xr ppbus 4 +.Xr ppbus 4 , +.Xr ppi 4 .Sh BUGS The chipset detection process may corrupt your chipset configuration. You may disable chipset specific detection by using the above flags. |