iflash2_mtd(4) [redhat man page]
IFLASH2_MTD(4) Kernel Interfaces Manual IFLASH2_MTD(4) NAME
iflash2_mtd - memory technology driver for Intel Series 2 flash SYNOPSIS
insmod iflash2_mtd.o [pc_debug=n] [mem_speed=n] [word_width=n] [vpp_timeout_period=n] [vpp_settle=n] [erase_timeout=n] [erase_limit=n] [retry_limit=n] [max_tries=n] [mem_speed=n] [word_width=n] DESCRIPTION
Iflash2_mtd is a memory technology driver for Intel Series 2 and Series 100 flash devices. Memory technology drivers are used by Card Ser- vices to provide device-independent access for memory cards through bulk memory services. Writing to Series 2 and Series 100 flash devices is very processor intensive. Individual words are written one at a time, at a speed of roughly 10 us per word. This busy period is too short to schedule other processes to run, so the driver will not yield the processor until an entire block is written. 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. mem_speed=n Sets the access speed of shared memory windows, in nanoseconds. The default is 0 (i.e., no extra wait states). Values of up to 1000 are legal. word_width=n A flag indicating if memory windows should be configured for 8-bit (if 0) or 16-bit (if 1) transfers. The default is 1 (16-bit). vpp_timeout_period=n In milliseconds, this specifies the maximum idle period after a write operation before programming power will be switched off. The default is 1000 ms. vpp_settle=n In milliseconds, this gives a delay between when programming power is switched on, and when the device is assumed to be powered up and ready to receive erase or write commands. The default is 100 ms. erase_timeout=n In milliseconds, specifies the poll interval for monitoring the status of a bulk erase operation. The default is 100 ms. erase_limit=n In milliseconds, specifies the maximum elapsed time before an erase operation is assumed to have failed. The default is 10000 ms. retry_limit=n The maximum number of retries for a write operation. The default is 4. max_tries=n The maximum number of status register polls before a single word write is assumed to have timed out. The default is 4096. AUTHOR
David Hinds - dahinds@users.sourceforge.net SEE ALSO
iflash2+_mtd(4), memory_cs(4). pcmcia-cs 2000/06/12 21:24:48 IFLASH2_MTD(4)
Check Out this Related Man Page
3C574_CS(4) Kernel Interfaces Manual 3C574_CS(4) NAME
3c574_cs - 3Com 3c574 Etherlink XL 10/100 PC Card device driver SYNOPSIS
insmod 3c574_cs.o [pc_debug=n] [if_port=n] [irq_list=i,j,...] [full_duplex=n] [auto_polarity=n] [max_interrupt_work=n] DESCRIPTION
3c574_cs is the low-level Card Services driver for the 3Com 3c574 EtherLink XL PCMCIA ethernet adapter. When this driver is attached to a card, it allocates the next available ethernet device (eth0..eth#). This device name will be reported in the kernel log file, and passed on to cardmgr(8). The driver uses the N-Way autonegotiating transceiver to negotiate the speed and duplex of the network link. If the link partner does not support negotiation, only the link speed is detected. 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. if_port=n Selects the transceiver type. Only 0, 1, and 4 are acceptable values, other values return an error. This actual value specificed is ignored -- the autonegotiating transceiver selects the media speed and duplex used. irq_list=i,j,... This option limits the set of interrupts that may be allocated by this driver. The default is all normally-usable IRQs. full_duplex=n This flag determines if only full-duplex modes are advertised. It defaults to 0 (false). This flag can be used to control the transceiver's auto polarity detection capability. Some Cisco Catalyst switches are known to interact badly with this feature in 10baseT mode. It defaults to 1 (enabled). max_interrupt_work=work-limit This option selects the maximum amount of work handled during each interrupt. Each received packet counts as one unit of work, as does updating statistics counters and handling errors. The default is 32. DIAGNOSTICS
eth#: interrupt(s) dropped! Indicates that the driver did not receive an interrupt notification for some reason. The driver will poll the card (with a signifi- cant performance penalty) if the problem persists. The most likely cause is an interrupt conflict and/or host bridge configuration problem. AUTHOR
Driver core: Donald Becker - becker@scyld.com PC Card interface: David Hinds - dahinds@users.sourceforge.net SEE ALSO
cardmgr(8), pcmcia(5), ifport(8). pcmcia-cs $Date 3C574_CS(4)