introduction to PCMCIA (PC Card) support
pcic0 at isa? port 0x3e0 iomem 0xd0000 iosiz
pcic1 at isa? port 0x3e2 iomem 0xe0000 iosiz 0x4000
pcic2 at isa? port 0x3e4 iomem 0xe0000 iosiz 0x4000
pcic* at isapnp?
pcic* at pci? dev?
pcmcia* at pcic?
tcic0 at isa? port 0x240 iomem 0xd0000 iosiz
pcmcia* at tcic?
pcic* at cbus?
pcmcia* at pcic?
stp* at sbus?
pcmcia* at stp?
# all architectures
cbb* at pci?
cardslot* at cbb? flags 0x0000
pcmcia* at cardslot?
subsystem provides machine-independent
bus support and drivers for PCMCIA (PC Card) devices.
provides support for the following devices. Note
that not all architectures support all devices.
- GemPlus GPR400 smartcard reader
- serial communications interface
- 3Com EtherLink III and Fast EtherLink III 10/100 Ethernet
- NE2000 and compatible 10/100 Ethernet device
- SMC91C9x and SMC91C1xx-based 10/100 Ethernet device
- Xircom-based 16-bit PCMCIA 10/100 Ethernet device
- Aironet Communications 4500/4800 IEEE 802.11FH/b wireless
- Marvell Libertas IEEE 802.11b/g wireless network
- WaveLAN/IEEE, PRISM 2-3, and Spectrum24 IEEE 802.11b
wireless network device
- Adaptec AIC-6260 and AIC-6360 SCSI interface
- WD100x compatible hard disk controller driver
The supported PCMCIA controllers are those that are i82365 compatible.
On some pcmcia
adapters, for instance the
bus will be mapped in big-endian format
instead of the natural (and preferred) little endian format. Unfortunately
such controllers lack the hardware facility to swap bytes, and it is not
efficient to convert all drivers to always know about this. While 8 bit
drivers can invisibly work on such a bus, 16 bit drivers will need
modification to handle this. So far,
is the only driver to require
If the pcmcia
adapter is not detected, or if
events (such as card insertion) do not
occur, there may be a PCI card BIOS mapped in the same memory space the
driver is configured to use (this is often
the case with Ethernet card boot ROMs). The output from
should contain a line
beginning with “bios0” that lists the memory address and size of
mapped regions. If there is a conflict, you can use
the iomem parameter of the pcic
device to a
non-overlapping address, such as 0xd8000 for
. Some experimentation may be required to
find a working value; in some cases the size parameter of the
device may need to be decreased to avoid a
driver appeared in