Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

esp(4) [netbsd man page]

ESP(4)							   BSD Kernel Interfaces Manual 						    ESP(4)

esp -- NCR 53C9x, Emulex ESP406, and Qlogic FAS408 SCSI driver SYNOPSIS
ISA bus esp0 at isa? port 0x230 irq ? PCMCIA esp* at pcmcia? function ? MCA esp* at mca? slot ? mac68k esp0 at obio? esp1 at obio? macppc esp0 at obio0 flags 0x00ff sun3x esp0 at obio0 addr 0x66000000 ipl 2 flags 0xff0f sparc dma0 at obio0 addr 0xfa001000 level 4 (Sun 4/300) esp0 at obio0 addr 0xfa000000 level 4 (Sun 4/300) dma0 at sbus0 slot ? offset ? (sun4c and sun4m) esp0 at sbus0 slot ? offset ? (sun4c) esp0 at dma0 (sun4m) dma* at sbus? slot ? offset ? (Sbus) esp* at sbus? slot ? offset ? (SBus, older PROMs) esp* at dma? (SBus) scsibus* at esp? DESCRIPTION
The esp driver provides support for the NCR 53C90, 53C94 and 53C96; Emulex ESP100, ESP100A, ESP200 and ESP406; and Qlogic FAS216 and FAS408 SCSI controller chips found in a wide variety of systems and peripheral boards. This includes the Qlogic ISA and VLB SCSI host adapters, and the Sun Fast SCSI buffered Ethernet for Sbus (FSBE/S, X1053A, Sun part # 501-2015). For Qlogic PCI SCSI host adapters, use the isp(4) device. CONFIGURATION
The esp driver supports the following flags for use in config(1) files: bits 0-7: disable disconnect/reselect for the corresponding SCSI target bits 8-15: disable synchronous negotiation for the corresponding SCSI target bits 16-23: disable tagged queuing for the corresponding SCSI target "Target" is synonymous with SCSI ID number. Note that SCSI tape drives should be allowed to perform disconnect/reselect or performance will suffer. SEE ALSO
cd(4), ch(4), intro(4), le(4), mca(4), pcmcia(4), scsi(4), sd(4), ss(4), st(4), uk(4) BSD
December 3, 2001 BSD

Check Out this Related Man Page

PCMCIA(4)						   BSD Kernel Interfaces Manual 						 PCMCIA(4)

pcmcia -- introduction to PCMCIA (PC Card) support SYNOPSIS
pcmcia* at pcic? controller ? socket ? pcmcia* at tcic? controller ? socket ? pcmcia* at cardslot? options PCMCIAVERBOSE amiga pcmcia* at pccard0 hpcmips pcmcia* at it8368e? controller ? socket ? pcmcia* at plumpcmcia? controller ? socket ? hpcsh pcmcia* at hd64461pcmcia? controller ? socket ? sh3 pcmcia* at shpcic? controller ? socket ? sparc pcmcia* at nell? DESCRIPTION
NetBSD provides machine-independent bus support and drivers for PCMCIA (Personal Computer Memory Card International Association) a.k.a. PC Card, CardBus devices. HARDWARE
NetBSD includes the following machine-independent PCMCIA drivers, sorted by function and driver name: Serial interfaces and modems com 8250/16450/16550-compatible PCMCIA serial cards and modems. Network interfaces an Aironet 4500/4800 and Cisco 340 series 802.11 controller. awi 802.11 controller based on the AMD PCnetMobile chipset. cnw Netwave AirSurfer Wireless LAN interface. ep 3Com 3c589 EtherLink III Ethernet card. mbe Ethernet card based on the Fujitsu MB86960A/MB86965A chipset. mhzc Megahertz Ethernet/Modem combo cards ne NE2000 compatible cards. ray Raytheon Raylink and WebGear Aviator2.4 802.11 controller. sm Megahertz Ethernet card. wi Lucent WaveLAN/IEEE and PRISM-II based 802.11 controller. xi Xircom CreditCard Ethernet SCSI controllers aic Adaptec APA-1460 SCSI controller card. esp NCR 53C9x, Emulex ESP406, and Qlogic FAS408 SCSI controllers. spc Fujitsu MB87030/MB89352 SCSI controllers. IDE controllers wdc Digital Hinote Ultra Mobile Media Adapter Bluetooth devices bt3c 3Com 3CRWB6096 Bluetooth PC Card driver. btbc AnyCom Bluetooth BlueCard driver. USB Controller slhci Cypress/ScanLogic SL811HS USB Host Controller driver. SEE ALSO
aic(4), an(4), awi(4), bt3c(4), btbc(4), cardbus(4), cnw(4), com(4), ep(4), esp(4), intro(4), isa(4), mbe(4), mhzc(4), ne(4), options(4), pcic(4), pcmcom(4), ray(4), slhci(4), sm(4), spc(4), tcic(4), wi(4), xi(4) HISTORY
The pcmcia driver appeared in NetBSD 1.3. BUGS
IO space conflicts NetBSD probes the PCMCIA IO bus width and uses that information to decide where to map PCMCIA IO space. For 10-bit wide cards, 0x300-0x3ff is used. For 12-bit wide cards, 0x400-0x4ff is used. Neither choice is perfect. In the 12-bit case, 0x400 appears to work in substantially more devices than 0x300. In the event that PCMCIA devices are mapped in 0x400-0x4ff and appear to be nonfunctional, remapping to 0x300-0x3ff may be appropriate; consult options PCIC_ISA_ALLOC_IOBASE and options PCIC_ISA_ALLOC_IOSIZE in options(4). Example: # Avoid PCMCIA bus space conflicts with the default IO space # allocation on 12-bit wide busses (base 0x300 size 0xff). options PCIC_ISA_ALLOC_IOBASE=0x300 options PCIC_ISA_ALLOC_IOSIZE=0x0ff Interrupt conflicts NetBSD attempts to probe for available interrupts to assign to PCMCIA devices. In some cases, it is not possible to detect all interrupts in use; in such cases, use of options PCIC_ISA_INTR_ALLOC_MASK may be necessary. See options(4). Unconfigured devices During autoconfiguration, if a message is displayed saying that your card is "not configured" it indicates that there isn't support for your card compiled into the kernel. To fix this problem, it may simply be a matter of adding the manufacturer and product IDs to the PCMCIA data- base or adding a front-end attachment to an existing driver. In the latter case, it is normally always necessary to get a dump of the CIS table from the card. You can do this by adding options PCMCIACISDEBUG and options PCMCIADEBUG into your kernel config file. Additionally, you will have to patch the kernel to enable run-time debugging. This can be done in the source by changing the variables pcmcia_debug and pcmciacis_debug to 0xff. Alternatively, you can patch the same variables at run-time using ddb(4). For most drivers you should also con- sider enabling any driver-specific debugging options. BSD
January 3, 2009 BSD
Man Page