Date: Fri, 5 Mar 1999 08:14:09 -0800 (PST) From: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> To: FreeBSD-gnats-submit@freebsd.org Subject: docs/10401: ppbus.4 spelling and grammar corrections Message-ID: <199903051614.IAA79876@troutmask.apl.washington.edu>
next in thread | raw e-mail | index | archive | help
>Number: 10401 >Category: docs >Synopsis: ppbus.4 spelling and grammar corrections >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Mar 5 08:20:01 PST 1999 >Closed-Date: >Last-Modified: >Originator: Steven G. Kargl >Release: FreeBSD 4.0-CURRENT i386 >Organization: APL/UW >Environment: FreeBSD-current >Description: Spelling and grammar errors in ppbus.4 man page. >How-To-Repeat: man 4 ppbus >Fix: --- ppbus.4.orig Fri Mar 5 07:46:32 1999 +++ ppbus.4 Fri Mar 5 08:06:29 1999 @@ -59,3 +59,3 @@ .Xr ppi 4 -that allows parallel port access from outside the kernel without confliting +that allows parallel port access from outside the kernel without conflicting with kernel-in drivers. @@ -70,3 +70,3 @@ .It Sy vpo Ta "VPI0 parallel to Adaptec AIC-7110 SCSI controller driver." -It uses standard and non-standard parallel port accesses +It uses standard and non-standard parallel port accesses. .It Sy ppi Ta "Parallel port interface for general I/O" @@ -95,3 +95,3 @@ .Pp -ppc makes chipset detection and initialisation and then calls ppbus attach +ppc makes chipset detection and initialization and then calls ppbus attach functions to initialize the ppbus system. @@ -123,3 +123,3 @@ checked for no errors and that it is not busy, and then a data Strobe is -generated by the sofware to clock the data to the printer. +generated by the software to clock the data to the printer. .Pp @@ -185,3 +185,3 @@ Bidirectional Parallel Peripheral Interface for Personal Computers". It -defines a signaling method for asynchroneous, fully interlocked, bidirectional +defines a signaling method for asynchronous, fully interlocked, bidirectional parallel communications between hosts and printers or other peripherals. It @@ -190,6 +190,6 @@ .Pp -This standard is architecture independent and only specifiy dialog handshake -at signal level. One should refer to any architecture specific document in -order to manipulate machine dependent registers, mapped memory or whatelse -to control these signals. +This standard is architecture independent and only specifies dialog handshake +at signal level. One should refer to architecture specific documentation in +order to manipulate machine dependent registers, mapped memory or other +methods to control these signals. .Pp @@ -200,4 +200,4 @@ properly manage the fully interlocked scheme of the signaling method. -The compatible mode is supported "as is" without any negociation because it -is compatible. Any other mode must be firstly negociated by the host to check +The compatible mode is supported "as is" without any negotiation because it +is compatible. Any other mode must be firstly negotiated by the host to check it is supported by the peripheral, then to enter one of the forward idle @@ -207,3 +207,3 @@ possible from forward idle states (nibble, byte, ecp...). So, the -host must have previously negociated to permit the peripheral to +host must have previously negotiated to permit the peripheral to request transfer. Interrupt lines may be dedicated to the requesting signals @@ -212,3 +212,3 @@ But peripheral requests are only a hint to the master host. If the host -accepts the transfer, it must firstly negociate the reverse mode and then +accepts the transfer, it must firstly negotiate the reverse mode and then starts the transfer. At any time during reverse transfer, the host may @@ -218,8 +218,8 @@ IEEE1284 Standard support has been implemented at the top of the ppbus system -as a set of procedures that perform high level functions like negociation, +as a set of procedures that perform high level functions like negotiation, termination, transfer in any mode without bothering you with low level -caracteristics of the stantdard. +characteristics of the standard. .Pp IEEE1284 interacts with the ppbus system as least as possible. That means -you still have to request the ppbus when you want to access it, the negociate +you still have to request the ppbus when you want to access it, the negotiate function doesn't do it for you. And of course, release it later. @@ -245,3 +245,3 @@ .Pp -Finaly, the +Finally, the .Em device @@ -255,6 +255,6 @@ .Xr ppbconf 9 . -.Ss Parallel modes managment -We have to differenciate operating modes at various ppbus system layers. +.Ss Parallel modes management +We have to differentiate operating modes at various ppbus system layers. Actually, ppbus and adapter operating modes on one hands and for each -one, current and available modes are seperated. +one, current and available modes are separated. .Pp @@ -265,3 +265,3 @@ .Pp -This achitecture should support IEEE1284-1994 modes. +This architecture should support IEEE1284-1994 modes. .Sh FEATURES @@ -270,3 +270,3 @@ .Xr ppc 4 -driver during ISA bus (PC architecture) initialisation. During attachment of +driver during ISA bus (PC architecture) initialization. During attachment of the ppc driver, a new ppbus structure is allocated, initialized @@ -308,3 +308,3 @@ Standard I/O operations are implemented at ppbus level whereas basic I/O -operations and microseq langage are coded at adapter level for efficiency. +operations and microseq language are coded at adapter level for efficiency. .Pp >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903051614.IAA79876>