Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

atppc(4) [netbsd man page]

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

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

Check Out this Related Man Page

PPC(4)							   BSD Kernel Interfaces Manual 						    PPC(4)

ppc -- Parallel Port Chipset driver SYNOPSIS
device ppc In /boot/device.hints:"isa" hint.ppc.0.irq="7" For one or more PPBUS busses: device ppbus DESCRIPTION
The ppc driver provides low level support to various parallel port chipsets for the ppbus(4) system. During the probe phase, ppc detects parallel port chipsets and initializes private data according to their operating mode: COMPATIBLE, NIB- BLE, PS/2, EPP, ECP and other mixed modes. If a mode is provided at startup through the flags variable of the boot interface, the operating mode of the chipset is forced according to flags and the hardware supported modes. During the attach phase, ppc allocates a ppbus structure, initializes it and calls the ppbus attach function. Supported flags bits 0-3: chipset forced mode(s) PPB_COMPATIBLE 0x0 /* Centronics compatible mode */ PPB_NIBBLE 0x1 /* reverse 4 bit mode */ PPB_PS2 0x2 /* PS/2 byte mode */ PPB_EPP 0x4 /* EPP mode, 32 bit */ PPB_ECP 0x8 /* ECP mode */ And any mixed values. bit 4: EPP protocol (0 EPP 1.9, 1 EPP 1.7) bit 5: activate IRQ (1 IRQ disabled, 0 IRQ enabled) bit 6: disable chipset specific detection bit 7: disable FIFO detection Supported chipsets Some parallel port chipsets are explicitly supported: detection and initialisation code has been written according to their datasheets. o SMC FDC37C665GT and FDC37C666GT chipsets o Natsemi PC873xx-family (PC87332 and PC87306) o Winbond W83877xx-family (W83877F and W83877AF) o SMC-like chipsets with mixed modes (see ppbus(4)) Adding support to a new chipset 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 ppc_mychipset_detect() function. Then add an entry to the general purpose ppc_detect() function. Your ppc_mychipset_detect() function should ensure that if the mode field of the 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. SEE ALSO
ppbus(4), ppi(4), device.hints(5) HISTORY
The ppc manual page first appeared in FreeBSD 3.0. AUTHORS
This manual page was written by Nicolas Souchu. BUGS
The chipset detection process may corrupt your chipset configuration. You may disable chipset specific detection by using the above flags. BSD
March 5, 1998 BSD
Man Page