redhat man page for smc91c92_cs

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)