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