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