Import translated manuals from JM CVS Repository.

[linuxjm/jm.git] / manual / pcmcia-cs / draft / man5 / pcmcia.5

.\" Copyright (C) 1998 David A. Hinds -- dahinds@users.sourceforge.net
.\" pcmcia.5 1.27 2000/10/16 16:37:38
.\"
.\" Japanese Version Copyright (c) 2000 KOJIMA Mitsuhiro and NAKANO Takeo
.\" all rights reserved.
.\" Translated Sun May 14 2000 by NAKANO Takeo <nakano@apm.seikei.ac.jp>
.\" based on the draft by KOJIMA Mitsuhiro <isle@st.rim.or.jp>
.\" Updated Mon 12 Mar 2001 by NAKANO Takeo
.\"
.TH PCMCIA 5 "2000/10/16 16:37:38" "pcmcia-cs"
.\"O .SH NAME
.\"O /etc/pcmcia/config \- PCMCIA card configuration database
.SH ̾Á°
/etc/pcmcia/config \- PCMCIA ¥«¡¼¥É¤ÎÀßÄê¥Ç¡¼¥¿¥Ù¡¼¥¹
.\"O 
.\"O .SH DESCRIPTION
.SH ÀâÌÀ
.\"O The PCMCIA card configuration file is read by \fIcardmgr\fR(8)
.\"O at startup time.  It defines what resources are available for use by
.\"O Card Services, describes how to load and initialize device drivers,
.\"O and describes specific PCMCIA cards.
PCMCIA ¥«¡¼¥ÉÀßÄê¥Õ¥¡¥¤¥ë¤Ï
.BR cardmgr (8)
¤¬µ¯Æ°»þ¤ËÆɤ߹þ¤à¡£
¤³¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤Ï¡¢¥«¡¼¥É¥µ¡¼¥Ó¥¹¤¬ÍøÍѤǤ­¤ë
IO ¥Ý¡¼¥È¡¦¥á¥â¥ê¡¦IRQ ¤È¤¤¤Ã¤¿¥ê¥½¡¼¥¹¤òÄêµÁ¤·¡¢
¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Î¥í¡¼¥É¤ä½é´ü²½¤ÎÊýË¡¤ò»ØÄꤷ¡¢
¤½¤ì¤¾¤ì¤Î PCMCIA ¥«¡¼¥É¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æµ­½Ò¤¹¤ë¡£
.\"O 
.\"O .SH Resource descriptions
.SH ¥ê¥½¡¼¥¹¤Îµ­½Ò
.\"O There are three kinds of resource entries: \fBinclude\fR,
.\"O \fBexclude\fR, and \fBreserve\fR. Including a resource enables Card
.\"O Services to allocate that resource for client drivers.  Part of a
.\"O resource that is under Card Services control can be excluded if a
.\"O specific device in the system uses that resource.  And, a resource can
.\"O be reserved, so that it will only be assigned to a client if that
.\"O client specifically asks for that resource, or no other suitable
.\"O resources are available.
¥ê¥½¡¼¥¹¤Î¥¨¥ó¥È¥ê¤Ë¤Ï 3 ¤Ä¤Î¼ïÎब¤¢¤ë¡£
.BR include ,
.BR exclude ,
.B reserve
¤Ç¤¢¤ë¡£
include ¤·¤¿¥ê¥½¡¼¥¹¤Ï¡¢
¥«¡¼¥É¥µ¡¼¥Ó¥¹¤¬¥¯¥é¥¤¥¢¥ó¥È¤È¤Ê¤ë³Æ¼ï¥É¥é¥¤¥Ð¤Ë³ä¤êÅö¤Æ¤ë¡£
¥«¡¼¥É¥µ¡¼¥Ó¥¹¤ÎÀ©¸æ²¼¤Ë¤¢¤ë¥ê¥½¡¼¥¹¤Ï exclude ¤¹¤ë¤³¤È¤â¤Ç¤­¤ë¡£
Î㤨¤Ð¥·¥¹¥Æ¥à¤ÎÆÃÄê¤Î¥Ç¥Ð¥¤¥¹¤¬¤½¤Î¥ê¥½¡¼¥¹¤ò»È¤¦¤è¤¦¤Ê¾ì¹ç¤Ç¤¢¤ë¡£
¥ê¥½¡¼¥¹¤Ï reserve ¤¹¤ë¤³¤È¤â¤Ç¤­¤ë¡£
¤³¤Î¾ì¹ç¤Ï¡¢¤½¤Î¥ê¥½¡¼¥¹¤òÆä˻Ȥ¤¤¿¤¤¤ÈÍ׵᤹¤ë¥¯¥é¥¤¥¢¥ó¥È¤¬¸½¤ï¤ì¤ë¤«¡¢
¤¢¤ë¤¤¤Ï¾¤Ë³ä¤êÅö¤Æ²Äǽ¤Ê¥ê¥½¡¼¥¹¤¬Ìµ¤¯¤Ê¤ë¤Þ¤Ç¡¢
¤½¤Î¥ê¥½¡¼¥¹¤Ï³ä¤êÅö¤Æ¤Ê¤¤¡£
.PP
.\"O There are three resource types: \fBport\fR, \fBmemory\fR, and
.\"O \fBirq\fR. By default, Card Services assumes that it can use any
.\"O interrupt that is not bound by another device driver.  However, it
.\"O makes no assumptions about IO port and address ranges, because some
.\"O Linux drivers do not register their resource usage.  So, port and
.\"O memory ranges must be explicitly made available for use by PCMCIA
.\"O devices.
¥ê¥½¡¼¥¹¤Î¥¿¥¤¥×¤Ë¤Ï 3 ¤Ä¤Î¼ïÎब¤¢¤ë¡£
.BR port ,
.BR memory ,
.B irq
¤Ç¤¢¤ë¡£
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¥«¡¼¥É¥µ¡¼¥Ó¥¹¤Ï¾¤Î¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤¬»È¤Ã¤Æ¤¤¤Ê¤¤
irq ¤ò¼«Í³¤Ë»È¤¨¤ë¤â¤Î¤È²¾Äꤹ¤ë¡£
¤·¤«¤·¡¢¥«¡¼¥É¥µ¡¼¥Ó¥¹¤Ï I/O ¥Ý¡¼¥È¤È¥¢¥É¥ì¥¹¤ÎÈϰϤ˴ؤ·¤Æ¤Ï
¤Ê¤ó¤Î²¾Äê¤â¹Ô¤ï¤Ê¤¤¡£ Linux ¤Î¥É¥é¥¤¥Ð¤ÎÃæ¤Ë¤Ï
¥ê¥½¡¼¥¹¤ÎÍøÍѾõ¶·¤òÅÐÏ¿¤·¤Ê¤¤Êª¤¬¤¢¤ë¤«¤é¤Ç¤¢¤ë¡£
¤½¤Î¤¿¤á¡¢
IO ¥Ý¡¼¥È¤È¥á¥â¥ê¤ÎÈϰϤˤĤ¤¤Æ¤Ï¡¢
PCMCIA ¥Ç¥Ð¥¤¥¹¤¬»È¤Ã¤ÆÎɤ¤Éôʬ¤òÌÀ¼¨Åª¤Ë»ØÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
.PP
.\"O So, here is a portion of a config file:
¤³¤ì¤é¤ò¤Þ¤È¤á¤ë¤È¡¢ÀßÄê¥Õ¥¡¥¤¥ë¤ÎÆâÍƤϰʲ¼¤Î¤è¤¦¤Ë¤Ê¤ë:
.sp
.RS
.nf
include port 0x300-0x3ff, memory 0xd0000-0xdffff
reserve irq 3
exclude irq 4, port 0x3f8-0x3ff
.RE
.fi
.sp
.\"O This says that Card Services can allocate ports in the range 0x300 to
.\"O 0x3ff, and memory in the range 0xd0000 to 0xdffff.  It should not use
.\"O irq 4 or ports 0x3f8-0x3ff (even if they seem to be available).  And
.\"O irq 3 should only be allocated if a client specifically asks for it.
¤³¤ÎÎã¤Ç¤Ï¡¢¥«¡¼¥É¥µ¡¼¥Ó¥¹¤Ï I/O ¥Ý¡¼¥È¤Î 0x300 ¤«¤é
0x3ff ¤È¡¢¥á¥â¥ê¤Î 0xd0000  ¤«¤é 0xdffff ¤Þ¤Ç¤ò³ä¤êÅö¤Æ¤ÆÎɤ¤¤³¤È¤Ë¤Ê¤ë¡£
exclude »ØÄê¤ò¤·¤¿ irq 4 ¤È I/O ¥Ý¡¼¥È¤Î 0x3f8 ¤«¤é 0x3ff ¤Ï¡¢
ÍøÍѲÄǽ¤Ç¤¢¤Ã¤Æ¤â»È¤ï¤Ê¤¤¡£
reserve »ØÄꤷ¤¿ irq 3 ¤Ï¡¢
Æäˤ½¤Î³ä¤ê¹þ¤ß¤ò¥¯¥é¥¤¥¢¥ó¥È¤¬É¬ÍפȤ·¤¿¾ì¹ç¤Ë¸Â¤Ã¤ÆÍøÍѤ¹¤ë¡£
.PP
.\"O Card Services will never allocate resources already allocated by
.\"O another kernel device driver.  The
.\"O .BR include / exclude / reserve
.\"O mechanism just provides a way of controlling what resources it will
.\"O try to use, to accomodate devices that are not registered with the
.\"O Linux resource manager.
¥«¡¼¥É¥µ¡¼¥Ó¥¹¤Ï¡¢Â¾¤Î¥«¡¼¥Í¥ë¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Ë³ä¤êÅö¤Æ¤é¤ì¤Æ¤¤¤ë
¥ê¥½¡¼¥¹¤Ï·è¤·¤ÆÍøÍѤ·¤Ê¤¤¡£
.BR include / exclude / reserve
¥á¥«¥Ë¥º¥à¤Ï¡¢¥«¡¼¥É¥µ¡¼¥Ó¥¹¤¬»È¤ª¤¦¤È»î¤ß¤ë¥ê¥½¡¼¥¹¤ò»ØÄꤹ¤ë¤â¤Î¤Ç¡¢
Linux ¤Î¥ê¥½¡¼¥¹¥Þ¥Í¡¼¥¸¥ã¡¼¤ËÅÐÏ¿¤µ¤ì¤Ê¤¤¥Ç¥Ð¥¤¥¹¤È
¤¦¤Þ¤¯¶¦Â¸¤¹¤ë¤¿¤á¤Î»ÅÁȤߤʤΤǤ¢¤ë¡£
.\"kojima [Ãð ¼á¡§¤«¤Ã¤Æ¥ê¥½¡¼¥¹¤Î»ØÄê¤Ï /etc/pcmcia/config ¤ÎºÇ½é¤Ë
.\"kojima ¤¢¤ê¤Þ¤·¤¿¤¬¡¢¸½ºß¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï /etc/pcmcia/config.opts
.\"kojima ¤È ¤·¤ÆÆÈΩ¤·¤Æ¤¤¤Þ¤¹¡£/etc/pcmcia/config ¤Ï¿·¤·¤¯¥µ¥Ý¡¼¥È
.\"kojima ¤µ¤ì¤¿¥«¡¼¥É¤¬Áý¤¨¤ë¤¿¤Ó¤Ë½ñ¤­¤«¤¨¤é¤ì ¤Þ ¤¹ ¤¬¡¢/etc/pcm-
.\"kojima cia/config.opts ¤Ï½ñ¤­¤«¤ï¤é¤Ê¤¤¤Î¤Ç¡¢¥·¥¹¥Æ¥à¤Ë°Í¸¤¹¤ëµ­
.\"kojima ½Ò¤Ï *.opts ¥Õ¥¡¥¤¥ë¤Ë¤Þ¤È¤á¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£]
.\"O 
.\"O .SH Device driver descriptions
.SH ¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Îµ­½Ò
.\"O All Card Services client drivers are identified by a 32-character tag.
.\"O \fBDevice\fR entries in the config file describe client drivers.  The only
.\"O required field is the device tag.  Additional fields can specify
.\"O kernel modules that need to be loaded to make the device available,
.\"O and a script to be executed to enable and disable instances of
.\"O a device.  When an instance of a driver is assigned to a socket, it
.\"O gives cardmgr a device name by which this device will be known by the
.\"O system (for example, \fIeth0\fR for a net device, or \fIcua1\fR for a
.\"O modem).  This name will be passed to the configuration script.  For
.\"O example:
¥«¡¼¥É¥µ¡¼¥Ó¥¹¤ÎÁ´¤Æ¤Î¥¯¥é¥¤¥¢¥ó¥È¥É¥é¥¤¥Ð¤Ï¡¢
32 ʸ»ú¤Î¥¿¥°¤Ë¤è¤Ã¤Æ¼±Ê̤µ¤ì¤ë¡£
ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î
.B device
¥¨¥ó¥È¥ê¤¬¥¯¥é¥¤¥¢¥ó¥È¥É¥é¥¤¥Ð¤òµ­½Ò¤¹¤ë¡£
ɬ¿Ü¤Î¥Õ¥£¡¼¥ë¥É¤Ï¼±ÊÌÍѤΥ¿¥°¤Î¤ß¤Ç¡¢
¤½¤Î¾¤Î¥Õ¥£¡¼¥ë¥É¤Ë¤Ï¡¢
¤½¤Î¥Ç¥Ð¥¤¥¹¤òÍøÍѤ¹¤ë¤¿¤á¤Ë¥í¡¼¥É¤¹¤Ù¤­¥«¡¼¥Í¥ë¥â¥¸¥å¡¼¥ë¤ä
¥Ç¥Ð¥¤¥¹¤Î¼ÂÂΤòÍ­¸ú/̵¸ú¤¹¤ë¤¿¤á¤Ë¼Â¹Ô¤¹¤ë¥¹¥¯¥ê¥×¥È¤ò»ØÄꤹ¤ë¡£
¥É¥é¥¤¥Ð¤Î¼ÂÂΤ¬¥½¥±¥Ã¥È¤Ë³ä¤êÅö¤Æ¤é¤ì¤ë¤È¡¢
¥É¥é¥¤¥Ð¤Ï cardmgr ¤Ë¥·¥¹¥Æ¥à¤«¤é¸«¤¿¤½¤Î¥Ç¥Ð¥¤¥¹¤Î̾¾Î
(¥Í¥Ã¥È¥ï¡¼¥¯¥Ç¥Ð¥¤¥¹¤Ê¤é¤Ð
.IR eth0 ¡¢
¥â¥Ç¥à¤Ê¤é¤Ð
.I cua1
¤Ê¤É)
¤òÄÌÃΤ¹¤ë¡£
¤³¤Î̾¾Î¤ÏÀßÄêÍÑ¥¹¥¯¥ê¥×¥È¤ËÅϤµ¤ì¤ë¡£Î㤨¤Ð:
.sp
.RS
.nf
device "pcnet_cs"
  class "network"
  module "net/8390" opts "ei_debug=4", "pcnet_cs"
.RE
.fi
.sp
.\"O This says that the \fBpcnet_cs\fR device requires two loadable modules.
.\"O The first one is located in the \fInet\fR module subdirectory and will
.\"O be loaded with a specific parameter setting.  The second module should
.\"O be in the \fIpcmcia\fR module subdirectory.  The device is in the
.\"O network class, so the \fInetwork\fR script in the configuration
.\"O directory will be used to start or stop the device.
¤È¤¤¤¦»ØÄê¤Ç¤Ï¡¢
.B pcnet_cs
¥Ç¥Ð¥¤¥¹¤Ï 2 ¤Ä¤Î¥í¡¼¥À¥Ö¥ë¥â¥¸¥å¡¼¥ë¤¬É¬ÍפǤ¢¤ë¤³¤È¤ò¼¨¤·¤Æ¤¤¤ë¡£
1 ¤Ä¤á¤Î¥â¥¸¥å¡¼¥ë (8390) ¤Ï¥â¥¸¥å¡¼¥ë¥Ç¥£¥ì¥¯¥È¥ê¤Î
.I net
¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ê¡¢»ØÄꤷ¤¿¥Ñ¥é¥á¡¼¥¿
.I ei_debug=4
¤È¶¦¤Ë¥í¡¼¥É¤µ¤ì¤ë¡£
2 ¤Ä¤á¤Î¥â¥¸¥å¡¼¥ë (de650_cs) ¤Ï
.I pcmcia
¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë¡£
¤³¤Î¥Ç¥Ð¥¤¥¹ (pcnet_cs) ¤Ï
.I network
¤È¤¤¤¦¥¯¥é¥¹¤Ë°¤·¡¢¥Ç¥Ð¥¤¥¹¤Îµ¯Æ°¤È½ªÎ»¤Ë¤Ï¡¢
ÀßÄê¥Õ¥¡¥¤¥ë¤ÈƱ¤¸¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë
.I network ¥¹¥¯¥ê¥×¥È (/etc/pcmcia/network) ¤¬ÍøÍѤµ¤ì¤ë¡£
.PP
.\"O It is also possible to specify default options for a particular kernel
.\"O module, outside of a device driver declaration.  This is convenient
.\"O for keeping local configuration options in a file separate from the
.\"O main card configuration file.  For example:
¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥ÐÀë¸À¤Î³°Éô¤Ç¡¢
ÆÃÄê¤Î¥«¡¼¥Í¥ë¥â¥¸¥å¡¼¥ë¤Î¥Ç¥Õ¥©¥ë¥È¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤ë¡£
¤³¤ì¤Ï¥í¡¼¥«¥ë¤ÊÀßÄꥪ¥×¥·¥ç¥ó¤ò
¥á¥¤¥ó¤Î¥«¡¼¥ÉÀßÄê¥Õ¥¡¥¤¥ë¤«¤éʬΥ¤¹¤ë¤Î¤ËÊØÍø¤Ç¤¢¤ë¡£
.\"kojima ³Æ¥Ç¥Ð¥¤¥¹¤ÎÀßÄêÍÑ¥¹¥¯¥ê¥×¥È¤Ï¥Ç¥Ð¥¤¥¹¤Î½é´ü²½¤È½ªÎ»¤ÎºÝ¤Ë
.\"kojima µ¯Æ°¤µ¤ì¤Þ¤¹¤¬¡¢¤½¤ì°Ê³°¤Ë¤â¡¢¥µ¥¹¥Ú¥ó¥É»þ¤Ë¤½¤Î¥Ç¥Ð¥¤¥¹¤¬
.\"kojima ¸½ºß»ÈÍÑÃ椫¤É¤¦¤«¤ò³Îǧ¤·¤¿¤ê¡¢¥ì¥¸¥å¡¼¥à¤ÎºÝ¤Ë¥Ç¥Ð¥¤¥¹¤ò
.\"kojima ºÆÀßÄꤷ¤¿¤ê¤¹¤ë¤Î¤Ë¤â»È¤ï¤ì¤Þ¤¹¡£ cardmgr ¤ÏÀßÄêÍÑ¥¹¥¯ ¥ê
.\"kojima ¥×¥È¤ò¤¤¤¯¤Ä¤«¤Î°ú¿ô¤ò»ØÄꤷ¤Æµ¯Æ°¤·¤Þ¤¹¡£°ú¿ô¤È¤·¤Æ»ØÄꤵ
.\"kojima ¤ì¤ë¤Î¤Ï¡Ö¼è¤ë¤Ù¤­Æ°ºî¡×¤È¡Ö¥Ç¥Ð¥¤¥¹Ì¾¡×¤Ç¡¢²Äǽ¤Ê¤é¤Ð¡Ö¥Ç
.\"kojima ¥Ð¥¤¥¹ÈÖ¹æ(major/minor)¡×¤â»ØÄꤷ¤Þ¤¹¡£
.sp
.RS
.nf
module "pcnet_cs" opts "mem_speed=600"
.RE
.fi
.sp
.\"O 
.\"O .SH Card descriptions
.SH ¥«¡¼¥É¤Îµ­½Ò
.\"O Card declarations map PCMCIA cards to their client drivers.  A card
.\"O declaration consists of a descriptive name, a method for identifying
.\"O the card when it is inserted, and driver bindings.  There are six
.\"O identification methods: the \fBversion\fR method matches a card using
.\"O its VERSION_1 id strings, the \fBmanfid\fR method matches a card using
.\"O its MANFID tuple codes, the \fBpci\fR method matches a CardBus card
.\"O using its PCI device ID's, the \fBtuple\fR method matches a card using
.\"O any string embedded in any arbitrary CIS tuple, the \fBfunction\fR
.\"O method matches a card using its function ID, and the \fBanonymous\fR
.\"O method matches any card that does not have a CIS.  This last method
.\"O is only intended to be used for old-style Type I memory cards.  For
.\"O example:
card Àë¸À¤Ï¡¢PCMCIA ¥«¡¼¥É¤È¤½¤Î¥¯¥é¥¤¥¢¥ó¥È¥É¥é¥¤¥Ð¤È¤ò
·ë¤Ó¤Ä¤±¤ë¤â¤Î¤Ç¤¢¤ë¡£
card Àë¸À¤Ï¡¢¥«¡¼¥É¤Î̾¾Î¡¦¥«¡¼¥É¤¬ÁÞÆþ¤µ¤ì¤¿ºÝ¤Î¼±ÊÌÊýË¡¡¦
ÍøÍѤ¹¤ë¥É¥é¥¤¥Ð¡¢¤Î 3 ¤Ä¤ÎÉôʬ¤«¤é¤Ê¤ë¡£
¥«¡¼¥É¤ò¼±Ê̤¹¤ë¤Ë¤Ï 6 ¤Ä¤Î¥á¥½¥Ã¥É (ÊýË¡) ¤¬¤¢¤ë¡£
.B version
¥á¥½¥Ã¥É¤Ï¥«¡¼¥É¼±ÊÌ¤Ë VERSION_1 id ʸ»úÎó¤òÍѤ¤¤ë¡£
.B manfid
¥á¥½¥Ã¥É¤Ï¥«¡¼¥É¤Î MANFID ¥¿¥×¥ë¥³¡¼¥É¤òÍѤ¤¤ë¡£
.B pci
¥á¥½¥Ã¥É¤Ï CardBus ¥«¡¼¥É¤Î PCI ¥Ç¥Ð¥¤¥¹ ID ¤òÍѤ¤¤ë¡£
.B tuple
¥á¥½¥Ã¥É¤Ï¥«¡¼¥É¤ÎǤ°Õ¤Î CIS ¥¿¥×¥ë¤ËËä¤á¤³¤Þ¤ì¤¿Ê¸»úÎó¤òÍѤ¤¤ë¡£
.B function
¥á¥½¥Ã¥É¤Ï¥«¡¼¥É¤Î function ID ¤òÍѤ¤¤ë¡£
.B anonymous
¥á¥½¥Ã¥É¤Ï CIS ¤ò»ý¤¿¤Ê¤¤¥«¡¼¥É¤Ë¥Þ¥Ã¥Á¤¹¤ë
(¤³¤ì¤Ïµì¼°¤Î¥¿¥¤¥× I ¥á¥â¥ê¥«¡¼¥É¤ËÍѤ¤¤ëʪ¤Ç¤¢¤ë)¡£
°Ê²¼¤Ë¤¤¤¯¤Ä¤«Îã¤ò¼¨¤¹¡£
.sp
.RS
.nf
card "Linksys Ethernet Card"
  tuple 0x40, 0x0009, "E-CARD PC Ethernet Card"
  bind "pcnet_cs"
.RE
.fi
.sp
.\"O This card is identified by a string at offset 0x0009 in tuple 0x40,
.\"O and will be bound to the \fBpcnet_cs\fR driver (which must be already
.\"O declared in a \fBdriver\fR declaration).
¤³¤Î¥«¡¼¥É¤Ï 0x40 ¥¿¥×¥ë¤Î¥ª¥Õ¥»¥Ã¥È 0x0009 ¤«¤é»Ï¤Þ¤ë
ʸ»úÎó "E-CARD PC Ethernet Card" ¤Ë¤è¤Ã¤Æ¼±Ê̤µ¤ì¡¢
.B pcnet_cs
¥É¥é¥¤¥Ð¤Ë¥Ð¥¤¥ó¥É¤µ¤ì¤ë
(¥É¥é¥¤¥Ð¤Ï¤¢¤é¤«¤¸¤á
.B driver
Àë¸À¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤)¡£
.sp
.RS
.nf
card "Connectware LANdingGear Adapter"
  manfid 0x0057, 0x1004
  bind "pcnet_cs"
.RE
.fi
.sp
.\"O This card is identified by its MANFID tuple contents.  The \fBpci\fR
.\"O method has the same form, with \fBpci\fR replacing \fBmanfid\fR.
¤³¤Î¥«¡¼¥É¤Ï MANFID ¥¿¥×¥ë¤ÎÆâÍƤˤè¤Ã¤Æ¼±Ê̤µ¤ì¤ë¡£
.B pci
¥á¥½¥Ã¥É¤âƱ¤¸·Á¼°¤Ç¡¢
.B manfid
¤ÎÂå¤ï¤ê¤Ë
.B pci
¤È½ñ¤¯¡£
.sp
.RS
.nf
card "D-Link DE-650 Ethernet Card"
  version "D-Link", "DE-650"
  bind "pcnet_cs"
.RE
.fi
.sp
.\"O This card will be identified using its VERSION_1 tuple, and will also
.\"O be bound to the \fBpcnet_cs\fR driver.
¤³¤Î¥«¡¼¥É¤Ï VERISON_1 ¥¿¥×¥ë¤Ë¤è¤Ã¤Æ¼±Ê̤µ¤ì¡¢
.B pcnet_cs
¥É¥é¥¤¥Ð¤Ë¥Ð¥¤¥ó¥É¤µ¤ì¤ë¡£
.sp
.RS
.nf
card "Serial port device"
  function serial_port
  bind "serial_cs"
.RE
.fi
.sp
.\"O This binds the \fBserial_cs\fR driver to any card with a CIS function
.\"O ID of 0x02, which corresponds to a serial port card.  The function ID
.\"O can either be a number, or one of the following predefined functions:
.\"O \fBmemory_card\fR, \fBserial_port\fR, \fBparallel_port\fR,
.\"O \fBfixed_disk\fR, \fBvideo_adapter\fR, \fBnetwork_adapter\fR, and
.\"O \fBaims_card\fR.
¤³¤ì¤Ï CIS function ID ¤¬ 0x02 (¥·¥ê¥¢¥ë¥Ý¡¼¥È¥«¡¼¥É¤ËÂбþ)
¤Î¤¢¤é¤æ¤ë¥«¡¼¥É¤ò
.B serial_cs
¥É¥é¥¤¥Ð¤Ë¥Ð¥¤¥ó¥É¤¹¤ë¡£
function ID ¤Ï¿ô»ú¤Ç¤âÎɤ¤¤·¡¢ÄêµÁºÑ¤ß¤Î function ¤Ç¤¢¤ë
.BR memory_card ,
.BR serial_port ,
.BR parallel_port ,
.BR fixed_disk ,
.BR video_adapter ,
.BR network_adapter ,
.BR aims_card
¤Î¤¤¤º¤ì¤«¤Ç¤â¤«¤Þ¤ï¤Ê¤¤¡£
.PP
.\"O Finally, the configuration file can specify that Card Services should
.\"O use a replacement for the configuration information found on a card.
.\"O This can be useful if a card's configuration information is
.\"O particularly incomplete or inaccurate.  The new information is read
.\"O from a file as in this example:
ºÇ¸å¤Ë¡¢¥«¡¼¥É¤Ç¸«ÉÕ¤«¤Ã¤¿ÀßÄê¾ðÊó¤È¤Ï°Û¤Ê¤ë¤â¤Î¤ò
¥«¡¼¥É¥µ¡¼¥Ó¥¹¤ËÍѤ¤¤µ¤»¤ë¤è¤¦¤Ê»ØÄê¤âÀßÄê¥Õ¥¡¥¤¥ë¤Ç¤Ï²Äǽ¤Ç¤¢¤ë¡£
¥«¡¼¥É¤ÎÀßÄê¾ðÊó¤¬ÆäËÉÔ´°Á´¡¦ÉÔÀµ³Î¤Ç¤¢¤ë¾ì¹ç¤Ë¤³¤ì¤ò»È¤¨¤ë¤³¤È¤â¤¢¤ë¡£
¿·¤·¤¤ÀßÄê¤Ï¥Õ¥¡¥¤¥ë¤«¤éÆɤ߹þ¤à¡£Îã¤ò¼¨¤¹:
.sp
.RS
.nf
card "Evil broken card"
  manfid 0x1234, 0x5678
  cis "fixup.cis"
  bind "serial_cs"
.RE
.fi
.sp
.\"O 
.\"O .SH Memory region definitions 
.SH ¥á¥â¥êÎΰèÄêµÁ
.\"O Memory region definitions are used to associate a particular type of
.\"O memory device with a Memory Technology Driver, or "MTD".  An MTD is
.\"O used to service memory accesses in a device-independent fashion.  When
.\"O a card is identified, Card Services will attempt to load MTD's for all
.\"O its memory regions.
¥á¥â¥êÎΰèÄêµÁ¤Ï¡¢ÆÃÄê¤Î·Á¼°¤Î¥á¥â¥ê¥Ç¥Ð¥¤¥¹¤ò
Memory Technology Driver (MTD) ¤Ë´ØÏ¢ÉÕ¤±¤¹¤ë¤¿¤á¤ËÍѤ¤¤é¤ì¤ë¡£
MTD ¤Ï¥á¥â¥ê¥¢¥¯¥»¥¹¤ò¡¢¥Ç¥Ð¥¤¥¹ÆÈΩ¤Ê¤ä¤êÊý¤ÇÄ󶡤¹¤ë¡£
¥«¡¼¥É¤¬¤³¤Î¼ï¤Î¥á¥â¥ê¥Ç¥Ð¥¤¥¹¤Ç¤¢¤ë¤È¼±Ê̤µ¤ì¤ë¤È¡¢
¥«¡¼¥É¥µ¡¼¥Ó¥¹¤Ï¤½¤Î¥á¥â¥êÎΰèÁ´¤Æ¤ËÂФ·¤Æ MTD ¤òÆɤ߹þ¤â¤¦¤È¤¹¤ë¡£
.PP
.\"O A memory region definition begins with the \fBregion\fR keyword and a
.\"O descriptive string.  This is followed by an identification method:
.\"O either \fBdefault\fR to identify an MTD to be used for any otherwise
.\"O unclassified region, or \fBjedec\fR to identify a region based on its
.\"O JEDEC identification codes.  Thus, for example,
¥á¥â¥êÎΰèÄêµÁ¤Ï
.B region
¥­¡¼¥ï¡¼¥É¤È¼±ÊÌʸ»úÎ󤫤é»Ï¤Þ¤ë¡£
¼¡¤Ë¼±Ê̥᥽¥Ã¥É¤Ç¤¢¤ë
.BR default " ¤« " jedec
¤¬Íè¤ë¡£
.B default
¤Ï¾¤ËʬÎव¤ì¤Ê¤«¤Ã¤¿¤¹¤Ù¤Æ¤ÎÎΰè¤Ç»È¤¦ MTD ¤ò»ØÄꤷ¡¢
.B jedec
¤Ï¥á¥â¥êÎΰè¤ò JEDEC ¤Î¼±ÊÌ¥³¡¼¥É¤Ë¤è¤Ã¤Æ¼±Ê̤¹¤ë¡£
Î㤨¤Ð
.sp
.RS
.nf
region "Intel Series 2 Flash"
  jedec 0x89 0xa2
  mtd "iflash2_mtd"
.RE
.fi
.sp
.\"O specifies that the \fBiflash2_mtd\fR driver will be loaded based on a
.\"O JEDEC match.
¤Ï¡¢ JEDEC ¤¬¥Þ¥Ã¥Á¤¹¤ì¤Ð
.B iflash_mtd
¥É¥é¥¤¥Ð¤¬¥í¡¼¥É¤µ¤ì¤ë¤³¤È¤ò¼¨¤·¤Æ¤¤¤ë¡£
.\"O 
.\"O .SH BUGS
.SH ¥Ð¥° 
.\"O The \fBreserve\fR keyword has not actually been implemented in a
.\"O useful way for this version of Card Services.
º£¤Î¤È¤³¤í
.B reserve
¥­¡¼¥ï¡¼¥É¤Î¼ÂÁõ¤Ï¤³¤Î¥Ð¡¼¥¸¥ç¥ó¤Î¥«¡¼¥É¥µ¡¼¥Ó¥¹¤Ë¤Ï¤¢¤Þ¤êÊØÍø¤Ç¤Ê¤¤¡£
.\"O .SH AUTHOR
.SH Ãø¼Ô
David Hinds \- dahinds@users.sourceforge.net
.\"O .SH "SEE ALSO"
.SH ´ØÏ¢¹àÌÜ
.\"O cardmgr(8).
.BR cardmgr (8)