1.\" $NetBSD: pcmcia.4,v 1.26 2002/09/27 22:31:43 wiz Exp $ 2.\" 3.\" Copyright (c) 1999, 2002 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Lennart Augustsson. 8.\" 9.\" Redistribution and use in source and binary forms, with or without 10.\" modification, are permitted provided that the following conditions 11.\" are met: 12.\" 1. Redistributions of source code must retain the above copyright 13.\" notice, this list of conditions and the following disclaimer. 14.\" 2. Redistributions in binary form must reproduce the above copyright 15.\" notice, this list of conditions and the following disclaimer in the 16.\" documentation and/or other materials provided with the distribution. 17.\" 3. All advertising materials mentioning features or use of this software 18.\" must display the following acknowledgement: 19.\" This product includes software developed by the NetBSD 20.\" Foundation, Inc. and its contributors. 21.\" 4. Neither the name of The NetBSD Foundation nor the names of its 22.\" contributors may be used to endorse or promote products derived 23.\" from this software without specific prior written permission. 24.\" 25.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS 26.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 27.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 28.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS 29.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 30.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 31.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 32.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 33.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 34.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 35.\" POSSIBILITY OF SUCH DAMAGE. 36.\" 37.Dd September 27, 2002 38.Dt PCMCIA 4 39.Os 40.Sh NAME 41.Nm pcmcia 42.Nd 43introduction to 44.Tn PCMCIA 45.Pq Tn "PC Card" 46support 47.Sh SYNOPSIS 48.Cd "pcmcia* at pcic? controller ? socket ?" 49.Cd "pcmcia* at tcic? controller ? socket ?" 50.Cd "pcmcia* at cardslot?" 51.Pp 52.Cd options PCMCIAVERBOSE 53.Ss amiga 54.Cd "pcmcia* at pccard0" 55.Ss hpcmips 56.Cd "pcmcia* at it8368e? controller ? socket ?" 57.Cd "pcmcia* at plumpcmcia? controller ? socket ?" 58.Ss sh3 59.Cd "pcmcia* at shpcic? controller ? socket ?" 60.Ss sparc 61.Cd "pcmcia* at nell?" 62.Sh DESCRIPTION 63.Nx 64provides machine-independent bus support and drivers for 65.Tn PCMCIA 66.Pq Personal Computer Memory Card International Association 67a.k.a. 68.Tn "PC Card" , 69.Tn CardBus 70devices. 71.Sh HARDWARE 72.Nx 73includes the following machine-independent 74.Tn PCMCIA 75drivers, sorted by function and driver name: 76.Ss Serial interfaces and modems 77.Bl -tag -width speaker -offset indent 78.It com 798250/16450/16550-compatible PCMCIA serial cards and modems. 80.El 81.Ss Network interfaces 82.Bl -tag -width speaker -offset indent 83.It an 84Aironet 4500/4800 and Cisco 340 series 802.11 controller. 85.It awi 86802.11 controller based on the AMD PCnetMobile chipset. 87.It cnw 88Netwave AirSurfer Wireless LAN interface. 89.It ep 903com 3c589 Etherlink-III Ethernet card. 91.It mbe 92Ethernet card based on the Fujitsu MB86960A/MB86965A chipset. 93.It mhzc 94Megahertz Ethernet/Modem combo cards 95.It ne 96NE2000 compatible cards. 97.It ray 98Raytheon Raylink and WebGear Aviator2.4 802.11 controller. 99.It sm 100Megahertz Ethernet card. 101.It wi 102Lucent WaveLan/IEEE and PRISM-II based 802.11 controller. 103.It xi 104Xircom CreditCard Ethernet 105.El 106.Ss SCSI controllers 107.Bl -tag -width speaker -offset indent 108.It aic 109Adaptec APA-1460 110.Tn SCSI 111controller card. 112.It esp 113NCR 53C9x, Emulex ESP406, and Qlogic FAS408 114.Tn SCSI 115controllers. 116.El 117.Ss IDE controllers 118.Bl -tag -width speaker -offset indent 119.It wdc 120Digital Hinote Ultra Mobile Media Adapter 121.El 122.Ss Audio devices 123.Bl -tag -width speaker -offset indent 124.It esl 125Eiger Labs ESS1688 AudioDrive. 126.El 127.Sh SEE ALSO 128.Xr aic 4 , 129.Xr an 4 , 130.Xr awi 4 , 131.Xr cardbus 4 , 132.Xr cnw 4 , 133.Xr com 4 , 134.Xr ep 4 , 135.Xr esl 4 , 136.Xr esp 4 , 137.Xr intro 4 , 138.Xr isa 4 , 139.Xr mbe 4 , 140.Xr mhzc 4 , 141.Xr ne 4 , 142.Xr options 4 , 143.Xr pcic 4 , 144.Xr pcmcom 4 , 145.Xr ray 4 , 146.Xr sm 4 , 147.Xr tcic 4 , 148.Xr wi 4 , 149.Xr xi 4 150.Pp 151.Pa http://www.pcmcia.org/ 152.Sh HISTORY 153The 154.Nm 155driver appeared in 156.Nx 1.3 . 157.Sh BUGS 158.Ss IO space conflicts 159.Nx 160probes the 161.Tn PCMCIA 162IO bus width and uses that information to decide 163where to map 164.Tn PCMCIA 165IO space. For 10-bit wide cards, 0x300-0x3ff is 166used. For 12-bit wide cards, 0x400-0x4ff is used. 167.Pp 168Neither choice is perfect. In the 12-bit case, 0x400 appears to work 169on substantially more devices than 0x300. In the event that 170.Tn PCMCIA 171devices are mapped in 0x400-0xfff and appear to be nonfunctional, 172remapping to 0x300-0x3ff may be appropriate; consult 173.Cd options PCIC_ISA_ALLOC_IOBASE 174and 175.Cd options PCIC_ISA_ALLOC_IOSIZE 176in 177.Xr options 4 . 178Example: 179.Bd -literal -offset indent 180# Avoid pcmcia bus space conflicts with the default io space 181# allocation on 12-bit wide busses (base 0x400 size 0xfff). 182options PCIC_ISA_ALLOC_IOBASE=0x300 183options PCIC_ISA_ALLOC_IOSIZE=0x0ff 184.Ed 185.Ss Interrupt conflicts 186.Nx 187attempts to probe for available interrupts to assign to 188.Tn PCMCIA 189devices. In some cases, it is not possible to detect 190all interrupts in use; in such cases, use of 191.Cd options PCIC_ISA_INTR_ALLOC_MASK 192may be necessary. See 193.Xr options 4 . 194.Ss Unconfigured devices 195During autoconfiguration, if a message is displayed saying that your card 196is "not configured" it indicates that there isn't support for your card 197compiled into the kernel. To fix this problem, it may simply be a matter 198of adding the manufacturer and product IDs to the 199.Tn PCMCIA 200database or adding a front-end attachment to an existing driver. In 201the latter case, it is normally always necessary to get a dump of the 202CIS table from the card. You can do this by adding 203.Cd options PCMCIACISDEBUG 204and 205.Cd options PCMCIADEBUG 206into your kernel config file. Additionally, you will have to patch the 207kernel to enable run-time debugging. This can be done in the source 208by changing the variables 209.Va pcmcia_debug 210and 211.Va pcmciacis_debug 212to 0xff. Alternatively, you can patch the same variables at run-time 213using 214.Xr ddb 4 . 215For most drivers you should also consider enabling any driver-specific 216debugging options. 217