summaryrefslogtreecommitdiffstats
path: root/share/man/man4/ppbus.4
diff options
context:
space:
mode:
authorjoel <joel@FreeBSD.org>2012-03-24 13:37:57 +0000
committerjoel <joel@FreeBSD.org>2012-03-24 13:37:57 +0000
commit1994f885d3a28d7f220a6843465ea8a672012003 (patch)
tree8697ad29c4ee769a76bb9c76fc9bd6bb62ccba7f /share/man/man4/ppbus.4
parent306ae35dcaefcbf325fca38d3e534cb7719aefc9 (diff)
downloadFreeBSD-src-1994f885d3a28d7f220a6843465ea8a672012003.zip
FreeBSD-src-1994f885d3a28d7f220a6843465ea8a672012003.tar.gz
Remove superfluous paragraph macro.
Diffstat (limited to 'share/man/man4/ppbus.4')
-rw-r--r--share/man/man4/ppbus.43
1 files changed, 0 insertions, 3 deletions
diff --git a/share/man/man4/ppbus.4 b/share/man/man4/ppbus.4
index 4a873056..327b7c9 100644
--- a/share/man/man4/ppbus.4
+++ b/share/man/man4/ppbus.4
@@ -61,7 +61,6 @@ that allows parallel port access from outside the kernel without conflicting
with kernel-in drivers.
.El
.Ss Developing new drivers
-.Pp
The ppbus system has been designed to support the development of standard
and non-standard software:
.Pp
@@ -74,7 +73,6 @@ It uses standard and non-standard parallel port accesses.
.It Sy lpbb Ta "Philips official parallel port I2C bit-banging interface"
.El
.Ss Porting existing drivers
-.Pp
Another approach to the ppbus system is to port existing drivers.
Various drivers have already been ported:
.Pp
@@ -274,7 +272,6 @@ propose an arch-independent interface to access the hardware layer.
Finally, the
.Em device
layer gathers the parallel peripheral device drivers.
-.Pp
.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
OpenPOWER on IntegriCloud