lpt(4) [netbsd man page]

LPT(4)							   BSD Kernel Interfaces Manual 						    LPT(4)

NAME

     lpt -- generic printer device driver

SYNOPSIS

     device ppc
     device ppbus
     device lpt

DESCRIPTION

     The current lpt driver is the port of the original lpt driver to the ppbus(4) system.

     One purpose of this port was to allow parallel port sharing with other parallel devices.  Secondly, inb()/outb() calls have been replaced by
     ppbus function calls.  lpt is now arch-independent thanks to the ppbus interface.	See ppbus(4) for more info about the ppbus system.

     The parallel port bus is allocated by lpt when the printer device is opened and released only when the transfer is completed: either when the
     device is closed or when the entire buffer is sent in interrupt driven mode.

     The driver can be configured to be either interrupt-driven, or to poll the printer.  Ports that are configured to be interrupt-driven can be
     switched to polled mode by using the lptcontrol(8) command.

     Depending on your hardware, extended capabilities may be configured with the lptcontrol(8) command.  With an ECP/ISA port, you can take
     advantage of FIFO and DMA.

     In order to retrieve printer info from /dev/lpt0, just apply the cat command to the device.  If the printer supports IEEE1284 nibble mode and
     has data to send to the host, you will get it.

FILES

     /dev/lpt0			       first parallel port driver

SEE ALSO

     ppbus(4), ppc(4), lptcontrol(8)

HISTORY

     This driver replaces the functionality of the lpa driver, which is now defunct.

BUGS

     There are lots of them, especially in cheap parallel port implementations.

     It is only possible to open a lpt port when a printer is connected and on-line, making it impossible to run lptcontrol(8) when there is no
     printer connected.

     This driver could still stand a rewrite.

BSD
								 February 14, 1999							       BSD

ATPPC(4)						   BSD Kernel Interfaces Manual 						  ATPPC(4)

NAME

     atppc -- driver for AT-style parallel port chip sets

SYNOPSIS

     atppc* at acpi?
     atppc* at isa? port 0x378 irq 7 drq 3 flags 0x00
     atppc* at isapnp?
     atppc* at ofisa?
     atppc* at pnpbios? index ?
     atppc* at puc? port ?
     options ATPPC_VERBOSE
     options ATPPC_DEBUG

DESCRIPTION

     atppc supports parallel ports and provides the low level support needed by higher level drivers such as ppbus(4).	This driver attaches where
     the traditional NetBSD lpt(4) driver would ordinarily.  It provides the data transport and chip set manipulation needed by higher driver lay-
     ers, such as ppbus(4) and lpt(4).	This driver is designed to be one of many possible implementations supporting machine independent parallel
     device support via ppbus(4).

   IEEE 1284 support
     atppc is intended to provide to data-link like services to higher level IEEE 1284 device drivers (such as ppbus(4)).  atppc does not directly
     support IEEE 1284 features such as mode negotiation but rather provides the necessary infrastructure to allow a higher level driver to pro-
     vide these services.

     atppc does provide chip set manipulation, device handshakes (where appropriate), low-level error detection, and data transfer.

   Supported data transfer modes
     atppc supports the following data transfer modes: Centronics Compatible (Standard), Nibble, Byte (PS2), Fast Centronics, ECP, and EPP.  Stan-
     dard and Fast Centronics modes are write only, Nibble and Byte modes are read only, and ECP and EPP modes are bidirectional.

SEE ALSO

     acpi(4), i386/pnpbios(4), isa(4), isapnp(4), lpt(4), ofisa(4), ppbus(4), puc(4)

HISTORY

     The atppc driver is based on the ppc driver, which originally appeared in FreeBSD.  The driver was ported over in NetBSD 2.0.

AUTHORS

     This manual page is based on the FreeBSD ppc manual page.	The information has been updated for the NetBSD port by Gary Thorpe.

BUGS

     The FreeBSD driver includes support for some specific chip sets, specifically detection of some non-standard device I/O locations on the ISA
     bus.  This support was not ported over to the NetBSD version of the driver yet.

BSD
								 January 30, 2004							       BSD