1.\" $NetBSD: pcmcia.4,v 1.24 2001/09/29 19:39:52 augustss Exp $ 2.\" 3.\" Copyright (c) 1999 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 August 29, 2000 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.Ss amiga 52.Cd "pcmcia* at pccard0" 53.Ss hpcmips 54.Cd "pcmcia* at it8368e? controller ? socket ?" 55.Cd "pcmcia* at plumpcmcia? controller ? socket ?" 56.Ss sh3 57.Cd "pcmcia* at shpcic? controller ? socket ?" 58.Sh DESCRIPTION 59.Nx 60provides machine-independent bus support and drivers for 61.Tn PCMCIA 62.Pq Personal Computer Memory Card International Association 63a.k.a. 64.Tn "PC Card" , 65.Tn CardBus 66devices. 67.Sh HARDWARE 68.Nx 69includes the following machine-independent 70.Tn PCMCIA 71drivers, sorted by function and driver name: 72.Ss Serial interfaces and modems 73.Bl -tag -width speaker -offset indent 74.It com 758250/16450/16550-compatible PCMCIA serial cards and modems. 76.El 77.Ss Network interfaces 78.Bl -tag -width speaker -offset indent 79.It an 80Aironet 4500/4800 and Cisco 340 series 802.11 controller. 81.It awi 82802.11 controller based on the AMD PCnetMobile chipset. 83.It cnw 84Netwave AirSurfer Wireless LAN interface. 85.It ep 863com 3c589 Etherlink-III Ethernet card. 87.It mbe 88Ethernet card based on the Fujitsu MB86960A/MB86965A chipset. 89.It mhzc 90Megahertz Ethernet/Modem combo cards 91.It ne 92NE2000 compatible cards. 93.It ray 94Raytheon Raylink and WebGear Aviator2.4 802.11 controller. 95.It sm 96Megahertz Ethernet card. 97.It wi 98Lucent WaveLan/IEEE and PRISM-II based 802.11 controller. 99.It xi 100Xircom CreditCard Ethernet 101.El 102.Ss SCSI controllers 103.Bl -tag -width speaker -offset indent 104.It aic 105Adaptec APA-1460 106.Tn SCSI 107controller card. 108.It esp 109NCR 53C9x, Emulex ESP406, and Qlogic FAS408 110.Tn SCSI 111controllers. 112.El 113.Ss IDE controllers 114.Bl -tag -width speaker -offset indent 115.It wdc 116Digital Hinote Ultra Mobile Media Adapter 117.El 118.Ss Audio devices 119.Bl -tag -width speaker -offset indent 120.It esl 121Eiger Labs ESS1688 AudioDrive. 122.El 123.Sh SEE ALSO 124.Xr aic 4 , 125.Xr an 4 , 126.Xr awi 4 , 127.Xr cardbus 4 , 128.Xr cnw 4 , 129.Xr com 4 , 130.Xr ep 4 , 131.Xr esl 4 , 132.Xr esp 4 , 133.Xr intro 4 , 134.Xr isa 4 , 135.Xr mbe 4 , 136.Xr mhzc 4 , 137.Xr ne 4 , 138.Xr options 4 , 139.Xr pcic 4 , 140.Xr pcmcom 4 , 141.Xr ray 4 , 142.Xr sm 4 , 143.Xr tcic 4 , 144.Xr wi 4 , 145.Xr xi 4 146.Pp 147.Pa http://www.pcmcia.org/ 148.Sh HISTORY 149The 150.Nm 151driver appeared in 152.Nx 1.3 . 153.Sh BUGS 154.Ss IO space conflicts 155.Nx 156probes the 157.Tn PCMCIA 158IO bus width and uses that information to decide 159where to map 160.Tn PCMCIA 161IO space. For 10-bit wide cards, 0x300-0x3ff is 162used. For 12-bit wide cards, 0x400-0x4ff is used. 163.Pp 164Neither choice is perfect. In the 12-bit case, 0x400 appears to work 165on substantially more devices than 0x300. In the event that 166.Tn PCMCIA 167devices are mapped in 0x400-0xfff and appear to be nonfunctional, 168remapping to 0x300-0x3ff may be appropriate; consult 169.Cd options PCIC_ISA_ALLOC_IOBASE 170and 171.Cd options PCIC_ISA_ALLOC_IOSIZE 172in 173.Xr options 4 . 174Example: 175.Bd -literal -offset indent 176# Avoid pcmcia bus space conflicts with the default io space 177# allocation on 12-bit wide busses (base 0x400 size 0xfff). 178options PCIC_ISA_ALLOC_IOBASE=0x300 179options PCIC_ISA_ALLOC_IOSIZE=0x0ff 180.Ed 181.Ss Interrupt conflicts 182.Nx 183attempts to probe for available interrupts to assign to 184.Tn PCMCIA 185devices. In some cases, it is not possible to detect 186all interrupts in use; in such cases, use of 187.Cd options PCIC_ISA_INTR_ALLOC_MASK 188may be necessary. See 189.Xr options 4 . 190.Ss Unconfigured devices 191During autoconfiguration, if a message is displayed saying that your card 192is "not configured" it indicates that there isn't support for your card 193compiled into the kernel. To fix this problem, it may simply be a matter 194of adding the manufacturer and product IDs to the 195.Tn PCMCIA 196database or adding a front-end attachment to an existing driver. In 197the latter case, it is normally always necessary to get a dump of the 198CIS table from the card. You can do this by adding 199.Cd options PCMCIACISDEBUG 200and 201.Cd options PCMCIADEBUG 202into your kernel config file. Additionally, you will have to patch the 203kernel to enable run-time debugging. This can be done in the source 204by changing the variables 205.Va pcmcia_debug 206and 207.Va pcmciacis_debug 208to 0xff. Alternatively, you can patch the same variables at run-time 209using 210.Xr ddb 4 . 211For most drivers you should also consider enabling any driver-specific 212debugging options. 213