memory_cb(4) [redhat man page]
MEMORY_CS(4) Kernel Interfaces Manual MEMORY_CS(4) NAME
memory_cb - CardBus memory driver SYNOPSIS
insmod memory_cb.o [pc_debug=n] DESCRIPTION
Memory_cb gives direct memory access to the address spaces of CardBus cards. It provides character-mode devices for accessing a card's PCI configuration space, up to six mapped memory or IO regions, and its expansion ROM space. When loaded, memory_cb will allocate a free major device number. For each card, it will report which address spaces are available, and their sizes. Minor numbers have the form 'dddddsss', where 'ddddd' is the instance number and 'sss' is the memory space for that instance. When memory_cb is bound to a card, it will report its major and minor device numbers to cardmgr(8). The default memory card initialization script creates device special files for all eight card address spaces, though for a particular card, some of these may be unavailable. These devices have the following names: /dev/cbmem#s0 The card's PCI configuration space. /dev/cbmem#s[1-6] The IO or memory spaces mapped by the card's six Base Address Registers. /dev/cbmem#s7 The card's expansion ROM space. The character special devices can be used to read and write arbitrary numbers of bytes to arbitrary locations. The memory_cb driver can be bound to any card regardless of function. PARAMETERS
pc_debug=n Selects the PCMCIA debugging level. This parameter is only available if the module is compiled with debugging enabled. A non-zero value enables debugging. AUTHOR
David Hinds - dahinds@users.sourceforge.net SEE ALSO
cardmgr(8), pcmcia(5), memory_cs(4). pcmcia-cs 2000/06/12 21:24:48 MEMORY_CS(4)
Check Out this Related Man Page
FTL_CS(4) Kernel Interfaces Manual FTL_CS(4) NAME
ftl_cs - Flash Translation Layer driver for PCMCIA memory cards SYNOPSIS
insmod ftl_cs.o [pc_debug=n] [major_dev=n] DESCRIPTION
Flash memory devices typically need to be erased before they are written, and most flash devices can only be erased on large block bound- aries like 64K or 128K. The Flash Translation Layer driver, ftl_cs, implements a sort of virtual sector-addressable block device that hides the details of erase operations. Using the FTL driver, a flash memory card can be treated as an ordinary block device. The ftl_cs driver allocates a major device number when it is loaded. Minor device numbers have a bitwise layout of 'dddrrppp'. 'ddd' is the device number, with one card counting as one device. 'rr' is the common-memory region number, generally 0. And 'ppp' selects a logi- cal partition within the FTL region. The default configuration script for FTL devices will create a block device with the name of the form '/dev/ftl{d}c{r}', where '{d}' is the device number and '{r}' is the region number, that spans the entire FTL region. It also creates devices '/dev/ftl{d}c{r}p[1-4]' pointing to partitions 1 through 4 within this FTL region. An FTL region must be formatted before use. The formatting utility, ftl_format, needs to write to the corresponding raw memory device rather than the FTL device interface. PARAMETERS
pc_debug=n Selects the PCMCIA debugging level. This parameter is only available if the module is compiled with debugging enabled. A non-zero value enables debugging. major_dev=n Selects the major device number to allocate for FTL devices. The default is to pick any available major number. AUTHOR
David Hinds - dahinds@users.sourceforge.net SEE ALSO
ftl_format(8), cardmgr(8), memory_cs(4), pcmcia(5). pcmcia-cs 2000/06/12 21:24:47 FTL_CS(4)