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 debug
ging. - 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 han
dled 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 inter
rupt notification for some reason. The driver will
poll the card (with a significant 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.source
forge.net