tcic(4) [redhat man page]
TCIC(4) Kernel Interfaces Manual TCIC(4) NAME
tcic - Databook TCIC-2 PCMCIA controller driver SYNOPSIS
insmod tcic.o [pc_debug=n] [tcic_base=n] [ignore=n] [do_scan=n] [irq_list=i,j,...] [cs_irq=n] [poll_interval=n] [poll_quick=n] [cycle_time=n] DESCRIPTION
This is the low-level driver for the Databook TCIC-2 PCMCIA host controller family. It is used by Card Services for programming the TCIC-2 chip, and for monitoring card status change events. 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. tcic_base=n Sets the base I/O port address of the TCIC-2 chip. The default is 0x240. ignore=n Causes the driver to ignore a single socket. Sockets are numbered starting at 0. The socket will be left in whatever state it was already in, so it can be used for cards with point enablers that do not cooperate with Card Services. do_scan=n This flag specifies that all free interrupts should be tested to see if they can be triggered by the PCMCIA controller. The default is 1 (on). irq_list=i,j,... Specifies the set of interrupts that may be allocated by this driver, if they are otherwise available. The default list is 3, 4, 5, 6, 7, 10, 11, and 14. cs_irq=n Sets the interrupt line to use for monitoring card status changes. The default is 0, which means pick any legal interrupt not already in use. Legal values are 14, 10, 7, 6, 5, 4, and 3. poll_interval=n Sets the card status polling delay, in 1/100 second increments. If this parameter is set, card status interrupts will be disabled. poll_quick=n When a card status change interrupt is received, the TCIC-2 chip is briefly polled for additional status changes. This parameter sets the polling delay, in 1/100 second increments. The default is 5, meaning 0.05 seconds. cycle_time=n Sets the length of a CCLK external clock cycle, in nanoseconds. The default is 70 ns, corresponding to a standard ISA 14.31818 MHz clock. AUTHOR
David Hinds - dahinds@users.sourceforge.net SEE ALSO
cardmgr(8), pcmcia(5). pcmcia-cs 2000/06/12 21:24:48 TCIC(4)
Check Out this Related Man Page
SMC91C92_CS(4) Kernel Interfaces Manual SMC91C92_CS(4) NAME
smc91c92_cs - SMC 91cxx device driver SYNOPSIS
insmod smc91c92_cs.o [pc_debug=n] [if_port=n] [irq_list=i,j,...] DESCRIPTION
Smc91c92_cs is the low-level Card Services driver for SMC 91c92, 91c94, 91c96, and 91c100 based PC Card ethernet adapters. 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 ker- nel log file, and passed on to cardmgr(8). With the default transceiver setting, the driver will attempt to continuously autodetect the transceiver type (10base2 or 10baseT). There should normally only be a one or two second lag before the correct transceiver is selected. On particularly noisy or busy networks, it is possible for the detection logic to incorrectly toggle the transceiver type. If this becomes a problem, it may be necessary to explicitly select the interface type when the module is loaded or with the ifport command. 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. 0 is autodetect (10baseT or 10base2), 1 is 10baseT (twisted pair), and 2 is 10base2 (BNC, or thin net). The default is 0 (autodetect). irq_list=i,j,... Specifies the set of interrupts that may be allocated by this driver. 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. 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
David Hinds - dahinds@users.sourceforge.net SEE ALSO
cardmgr(8), pcmcia(5), ifport(8). pcmcia-cs 2000/06/12 21:24:48 SMC91C92_CS(4)