I82365(3) Library Functions Manual I82365(3)NAME
i82365 - Personal Computer Memory Card Interface Association (PCMCIA) device
SYNOPSIS
bind -a #y /dev
/dev/pcm0attr
/dev/pcm0ctl
/dev/pcm0mem
/dev/pcm1attr
/dev/pcm1ctl
/dev/pcm1mem
DESCRIPTION
The i82365 driver provides an interface to an Intel 82365-compatible PCMCIA interface chip. This chip supports up to 2 PCMCIA slots, 0 and
1. Reading pcm[01]attr returns the contents of attribute memory. Reading or writing pcm[01]mem reads or writes RAM on the card. Reading
pcm[01]ctl returns the card's status.
This driver must be included to use PCMCIA devices such as the NE4100 Ethernet card. The individual card drivers make calls to routines in
the PCMCIA driver.
SOURCE
/sys/src/9/pc/devi82365.c
SEE ALSO plan9.ini(8)BUGS
There is no driver for the Databook PCMCIA interface chip.
The PCMCIA section of the system is new and less reliable than other pieces of the system. Also, its coverage of devices is spotty.
I82365(3)
Check Out this Related Man Page
pcata(7D)pcata(7D)NAME
pcata - PCMCIA ATA card device driver
SYNOPSIS
pcata@socket#:a -u
pcata@socket#:a -u,raw
The PCMCIA ATA card device driver supports PCMCIA ATA disk and flash cards that follow the following standards:
o PC card 2.01 compliance (MBR+fdisk table required for all platforms).
o PC card ATA 2.01 compliance.
o PC card services 2.1 compliance.
The driver supports standard PCMCIA ATA cards that contain a Card Information Structure (CIS). For PCMCIA, nodes are created in /devices
that include the socket number as one component of the device name referred to by the node. However, the names in /dev, /dev/dsk, and
/dev/rdsk follow the current conventions for ATA devices, which do not encode the socket number in any part of the name. For example, you
may have the following:
+------------------------+---------------------------+---------------------+
| Platform | | |
+------------------------+---------------------------+---------------------+
|/devices name | | |
+------------------------+---------------------------+---------------------+
+------------------------+-/dev/dsk-name-------------+---------------------+
|/devices/isa/pcic@1,3e0 | | |
+------------------------+---------------------------+---------------------+
|/disk@0:a | | |
+------------------------+---------------------------+---------------------+
+------------------------+-/devices/iommu@f,e0000000-/sbus@f,e0001000-/SUNW, pcmcia@3,0 /disk@0:a
|SPARC | | /dev/dsk/c1d0s0 |
| | | |
| | | |
+------------------------+---------------------------+---------------------+
PRECONFIGURATION
If a PC Card ATA device is recognized, the pcata driver is automatically loaded, IRQs allocated, devices nodes created, and special files
created (if they do not already exist).
Known Problems and Limitations
o vold does not support pcata. File systems must be mounted manually.
o You need to umount the file system before removing the disk.
o The ufs file systems on removable media (PC Card ATA) should have one of the onerror={panic, lock, umount} mount options set.
CONFIGURATION
Configuration topics include initial installation and configuration, identifying an unrecognized device, special files and hot-plugging.
Initial Installation and Configuration
1. Install the Solaris software.
2. Boot the system.
3. Insert the PC card ATA device.
Identifying an Unrecognized Device
If you insert a PC card ATA device and it is not recognized (no special files created), use the prtconf command to identify the problem.
1. Run the prtconf -D command to see if your pcata card is recognized. (A recognized device will appear at the end of the prtconf output.
For example:
# prtconf -D
. . .
pcic, instance #0 (driver name: pcic)
. . .
disk, instance #0
2. If pcata does not appear in the prtconf output, there is a problem with the PC card adapter configuration or with the hardware. Check
to see whether the problem is with the card or the adapter by trying to use the card on another machine and by seeing if it works on
the same machine using DOS.
Special Files
For PC card devices, nodes are created in /devices that include the socket number as one component of a device name that the node refers
to. However, the /prtc/dev names and the names in /dev/dsk and /dev/rdsk do follow the current convention for ATA devices, which do not
encode the socket number in any part of the name.
Hot-Plugging
o If you want to remove the disk, you must unmount the file system.
o Use the mkfs_pcfs(1M) command to create a pcfs file system:
# mkfs -F pcfs /dev/rdsk/c#d#p0:d
o To mount a pcfs file system, type:
# mount -F pcfs /dev/dsk/c#d#p0:c /mnt
o If you want to create a ufs file system, use the newfs command and type:
# newfs /dev/rdsk/c#d#s#
o To mount a ufs file system, type:
# mount -F ufs /dev/dsk/c#d#s# /mnt
o To create a Solaris partition, run the format command and go to the Partition menu. For more information, see the format(1M) man page.
/kernel/drv/pcata pcata driver
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE |
+-----------------------------+-----------------------------+
|VALUE | |
+-----------------------------+-----------------------------+
|Availability |SUNWpsdpr |
+-----------------------------+-----------------------------+
format(1M), mount(1M), newfs(1M), pcmcia(7D), attributes(5), pcfs(7FS)
20 Oct 2000 pcata(7D)