pkg://Ethernet-HOWTO-html.tar.gz:84888/Ethernet-HOWTO-5.html
downloads
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>Linux Ethernet-Howto: 특정 판매자/제조업체/모델별 정보</TITLE>
<LINK HREF="Ethernet-HOWTO-6.html" REL=next>
<LINK HREF="Ethernet-HOWTO-4.html" REL=previous>
<LINK HREF="Ethernet-HOWTO.html#toc5" REL=contents>
</HEAD>
<BODY>
<A HREF="Ethernet-HOWTO-6.html">다음</A>
<A HREF="Ethernet-HOWTO-4.html">이전</A>
<A HREF="Ethernet-HOWTO.html#toc5">차례</A>
<HR>
<H2><A NAME="card-intro"></A> <A NAME="s5">5. 특정 판매자/제조업체/모델별 정보</A></H2>
<P>
<P>다음의 목록에서는 판매자 이름과 제품명을 알파벳 순서로 수많은 카드들을 나열하고 있다.
각 제품 ID 옆에는 `지원', `부분지원', '지원안됨'을 볼수 있을 것이다.
<P>지원된다는 의미는 그 카드의 드라이버가 존재하고, 많은 사람들이 문제없이 사용하고
있으며 매우 안정적이라는 뜻이다.
<P>부분지원이라는 뜻은 드라이버가 존재하지만 다음의 설명가운데 적어도 한가지 이상
해당된다는 뜻이다.
(1) 드라이버 그리고/또는 하드웨어에 버그가 있어서 낮은 성능이나, 접속 실패 또는
크래쉬도 발생할수 있다.
(2) 드라이버가 새로운 것이거나 카드가 일반적이지 않아서 드라이버에 대한 사용/테스트가
매우 적어 드라이버 제작자가 피드백을 별로 받지 못했다.
명확하게 (2)인 경우가 (1)인 경우보다 낫고, 그 카드/드라이버에 대한 개별적인 설명에서
어느 것에 해당하는지 확인해야 한다. 두가지 경우 모두, 여러분은 <CODE>make config</CODE>시에
``Prompt for development and/or incomplete code/drivers?''부분에서 `Y'라고 답해야 한다.
<P>지원안된다는 것은 현재 그 카드에 사용할수 있는 드라이버가 존재하지 않는다는 뜻이다.
이것은 구하기 힘들거나 평범하지 않은 하드웨어에 대한 관심이 부족하거나, 아니면 판매자들이
드라이버를 만드는데 필요한 하드웨어 문서를 배포하지 않기 때문이다.
<P>`지원'과 `부분지원'의 차이는 다소 주관적이며, 뉴스 그룹 게시판과 메일링 리스트 메세지들을
통한 사용자 피드백을 조사한것에 기반한 것임을 알아두라. (한사람이 각 커널 버전에서 모든
카드들을 가지고 모든 드라이버를 테스트한다는것은 절대로 불가능하다!!!) 그러므로 카드
리스트에 부분지원이라고 되어있는 것이 여러분의 경우에 완벽하게 동작한다거나(정말 좋군),
또는 지원이라고 적힌 카드가 문제가 발생하는 것을 (그리 좋지 못하군) 발견할수도 있다는
것에 주의하길 바란다.
<P>status 다음에는, 리눅스 커널내에 주어진 드라이버 이름이 나열되어 있다. 이것은 또한
<CODE>/etc/conf.modules</CODE> 모듈 설정 화일내의 <CODE>alias eth0 driver_name</CODE> 행으로
사용되는 드라이버 모듈의 이름이기도 하다.
<P>
<P>
<H2><A NAME="3com"></A> <A NAME="ss5.1">5.1 3Com</A>
</H2>
<P>
<P>만일 여러분이 가지고 있는 카드가 무엇인지 잘 모르지만, 아마 3Com 카드일꺼라고 생각하고
있다면, 어셈블리 넘버로부터 무엇인지 알아낼수 있을 것이다. 3Com에는 가장 명확하게 알수
있는 `어셈블리 넘버로 3Com 아답터 알아내기(Identifying 3Com Adapters By Assembly Number)'
(ref 24500002)라는 문서가 있다. 3Com 문서를 어떻게 얻는지는 다음을 보라.
<A HREF="Ethernet-HOWTO-8.html#3com-tech">Technical Information from 3Com</A><P>또한 3Com은 다양한 제품들에 대한 FTP 사이트를 가지고 있다.
<CODE>ftp.3Com.com</CODE>에서 여러분이 원하는 것을 찾을수 있을 것이다.
<P>이문서를 WWW 브라우저로 보고 있는 사람들은, 3Com의 WWW 사이트도 볼수 있다.
<P>
<H3><A NAME="3c501"></A> 3c501</H3>
<P>Status: 부분지원, 드라이버 이름: 3c501
<P>이 구석기 시대의 8비트 카드는 사용하려면 너무 머리가 아플정도다. 전염병을 피하는것처럼
피하라. 농담으로라도 이 카드를 구입하지 말라. 이것의 성능은 끔찍하고, 많은 경우에 문제가
발생한다.
<P>For those not yet convinced, the 3c501 can only do one
thing at a time -- while you are removing one packet
from the single-packet buffer it cannot receive
another packet, nor can it receive a packet while
loading a transmit packet. This was fine for a
network between two 8088-based computers where
processing each packet and replying took 10's of
msecs, but modern networks send back-to-back
packets for almost every transaction.
<P>AutoIRQ works, DMA isn't used, the autoprobe only
looks at <CODE>0x280</CODE> and <CODE>0x300</CODE>, and the debug level is set
with the third boot-time argument.
<P>Once again, the use of a 3c501 is <EM>strongly discouraged</EM>!
Even more so with a IP multicast kernel, as you will
grind to a halt while listening to <EM>all</EM> multicast
packets. See the comments at the top of the source code
for more details.
<P>
<H3><A NAME="3c503"></A> EtherLink II, 3c503, 3c503/16</H3>
<P>Status: Supported, Driver Name: 3c503 (+8390)
<P>The 3c503 does not have ``EEPROM setup'',
so a diagnostic/setup program
isn't needed before running the card with Linux. The
shared memory address of the 3c503 is set using jumpers
that are shared with the boot PROM address. This is
confusing to people familiar with other ISA cards,
where you always leave the jumper set to ``disable''
unless you have a boot PROM.
<P>These cards should be about the same speed as the same bus
width WD80x3, but turn out to be actually a bit slower.
These shared-memory ethercards also have a
programmed I/O mode that doesn't use the 8390
facilities (their engineers found too many bugs!)
The Linux 3c503 driver can also work with the 3c503
in programmed-I/O mode, but this is slower and less
reliable than shared memory mode. Also, programmed-I/O
mode is not as well tested when updating the drivers.
You shouldn't use the programmed-I/O mode
unless you need it for MS-DOS compatibility.
<P>The 3c503's IRQ line is set in software, with no hints
from an EEPROM. Unlike the MS-DOS drivers, the
Linux driver has capability to autoIRQ: it uses the
first available IRQ line in {5,2/9,3,4}, selected each
time the card is ifconfig'ed. (Older driver versions
selected the IRQ at boot time.) The ioctl() call
in `ifconfig' will return EAGAIN if no IRQ line is
available at that time.
<P>Some common problems that people have with the 503
are discussed in
<A HREF="Ethernet-HOWTO-3.html#3com-probs">Problems with...</A>.
<P>If you intend on using this driver as a loadable module
you should probably see
<A HREF="Ethernet-HOWTO-10.html#modules">Using the Ethernet Drivers as Modules</A>
for module specific information.
<P>Note that some old diskless 386 workstations have an on board
3c503 (made by 3Com and sold under different names, like `Bull')
but the vendor ID is not a 3Com ID and so it won't be detected.
More details can be found in the Etherboot package, which you
will need anyways to boot these diskless boxes.
<P>
<H3><A NAME="3c505"></A> Etherlink Plus 3c505</H3>
<P>Status: Semi-Supported, Driver Name: 3c505
<P>This is a driver that was written by Craig Southeren
<CODE>geoffw@extro.ucc.su.oz.au</CODE>. These cards also
use the i82586 chip.
There are not that many of these cards about.
It is included in the standard kernel, but it is classed as
an alpha driver. See
<A HREF="Ethernet-HOWTO-3.html#alfa">Alpha Drivers</A>
for important information on using alpha-test ethernet drivers
with Linux.
<P>There is also the file
<CODE>/usr/src/linux/drivers/net/README.3c505</CODE>
that you should read if you are going to use one of these cards.
It contains various options that you can enable/disable.
<P>
<H3><A NAME="3c507"></A> Etherlink-16 3c507</H3>
<P>Status: Semi-Supported, Driver Name: 3c507
<P>This card uses one of the Intel chips, and the
development of the driver is closely related to
the development of the Intel Ether Express driver.
The driver is included in the standard kernel
release, but as an alpha driver.
See
<A HREF="Ethernet-HOWTO-3.html#alfa">Alpha Drivers</A> for important
information on using alpha-test ethernet drivers
with Linux.
<P>
<H3><A NAME="3c509"></A> Etherlink III, 3c509 / 3c509B</H3>
<P>Status: Supported, Driver Name: 3c509
<P>This card is fairly inexpensive and has
good performance for an ISA non-bus-master design.
The drawbacks are that the original 3c509
requires very low interrupt latency. The 3c509B
shouldn't suffer from the same problem, due to
having a larger buffer. (See below.) These cards
use PIO transfers, similar to a ne2000 card, and so
a shared memory card such as a wd8013 will be more
efficient in comparison.
<P>The original 3c509 has a small packet buffer
(4kB total, 2kB Rx, 2kB Tx), causing the driver to
occasionally drop a packet if interrupts are masked for
too long. To minimize this problem, you can try unmasking
interrupts during IDE disk transfers (see <CODE>man hdparm</CODE>) and/or
increasing your ISA bus speed so IDE transfers finish sooner.
<P>The newer model 3c509B has 8kB on board, and the buffer
can be split 4/4, 5/3 or 6/2 for Rx/Tx. This setting
is changed with the DOS configuration utility, and is stored
on the EEPROM. This should alleviate the
above problem with the original 3c509.
<P>3c509B users should use either the supplied DOS
utility to disable the <EM>plug and play</EM> support, <EM>and</EM>
to set the output media to what they require. The linux
driver currently does <EM>not</EM> support the Autodetect
media setting, so you <EM>have</EM> to select 10Base-T or
10Base-2 or AUI.
Note that to turn off PnP entirely, you should do a
<CODE>3C5X9CFG /PNP:DISABLE</CODE> and then follow that with a hard
reset to ensure that it takes effect.
<P>Some people ask about the ``Server or Workstation'' and ``Highest
Modem Speed'' settings presented in the DOS configuration utility.
Donald writes ``These are only hints to the drivers, and the Linux
driver does not use these parameters: it always optimizes for high
throughput rather than low latency (`Server'). Low latency was
critically important for old, non-windowed, IPX throughput.
To reduce the latency the MS-DOS driver for the 3c509 disables
interrupts for some operations, blocking serial port interrupts.
Thus the need for the `modem speed' setting. The Linux driver avoids
the need to disable interrupts for long periods by operating only
on whole packets e.g. by not starting to transmit a packet
until it is completely transferred to the card.''
<P>Note that the ISA card detection uses a different method
than most cards. Basically, you ask the cards to respond
by sending data to an ID_PORT (port <CODE>0x100</CODE> to <CODE>0x1ff</CODE>
on intervals of <CODE>0x10</CODE>).
This detection method means that
a particular card will <EM>always</EM> get detected first
in a multiple ISA 3c509 configuration.
The card with the lowest hardware ethernet address
will <EM>always</EM> end up being <CODE>eth0</CODE>. This shouldn't matter
to anyone, except for those people who want to assign
a 6 byte hardware address to a particular interface.
If you have multiple 3c509 cards, it is best to append
<CODE>ether=0,0,ethN</CODE> commands without the I/O port specified
(i.e. use I/O=zero) and allow the probe to sort out which
card is first. Using a non-zero I/O value will ensure that it
does not detect all your cards, so don't do it.
<P>If this really bothers you, have a look at Donald's latest driver,
as you may be able to use a <CODE>0x3c509</CODE> value in the unused mem
address fields to order the detection to suit your needs.
<P>
<H3><A NAME="cork"></A> 3c515</H3>
<P>Status: Supported, Driver Name: 3c515
<P>This is 3Com's ISA 100Mbps offering,
codenamed ``CorkScrew''. A relatively new driver from
Donald for these cards is included in the v2.2 kernels.
For the most up to date information, you
should probably look on the Vortex page:
<P>
<A HREF="http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html">Vortex</A><P>
<P>
<H3><A NAME="3c523"></A> 3c523</H3>
<P>Status: Semi-Supported, Driver Name: 3c523
<P>This MCA bus card uses the i82586, and Chris Beauregard
has modified the ni52 driver to work with these cards. The
driver for it can be found in the v2.2 kernel source tree.
<P>More details can be found on the
MCA-Linux page at <CODE>http://glycerine.cetmm.uni.edu/mca/</CODE>
<P>
<H3><A NAME="3c527"></A> 3c527</H3>
<P>Status: Not Supported.
<P>Yes, another MCA card. No, not too much interest in it.
Better chances with the 3c529 if you are stuck with MCA.
<P>
<H3><A NAME="3c529"></A> 3c529</H3>
<P>Status: Supported, Driver Name: 3c509
<P>This card actually uses the same chipset as the 3c509.
Donald actually put hooks into the 3c509 driver to check
for MCA cards after probing for EISA cards, and before
probing for ISA cards, long before MCA support was
added to the kernel. The required MCA probe code is
included in the driver shipped with v2.2 kernels.
More details can be found on the MCA-Linux page at:
<P><CODE>http://glycerine.cetmm.uni.edu/mca/</CODE>
<P>
<H3>3c562</H3>
<P>Status: Supported, Driver Name: 3c589 (distributed separately)
<P>This PCMCIA card is the combination of a 3c589B ethernet card
with a modem. The modem appears as a standard modem to the
end user. The only difficulty is getting the two separate
linux drivers to share one interrupt. There are a couple of new
registers and some hardware interrupt sharing support.
You need to use a v2.0 or newer kernel that has the support
for interrupt sharing.
<P>
<P>Thanks again to Cameron for getting a sample unit and
documentation sent off to David Hinds. Look for support in David's
PCMCIA package release.
<P>See
<A HREF="Ethernet-HOWTO-9.html#pcmcia">PCMCIA Support</A> for more
info on PCMCIA chipsets, socket enablers, etc.
<P>
<H3>3c575</H3>
<P>Status: Unknown.
<P>A driver for this PCMCIA card is under development and hopefully
will be included in David's PCMCIA package in the future.
Best to check the PCMCIA package to get the current status.
<P>
<P>
<H3><A NAME="3c579"></A> 3c579</H3>
<P>Status: Supported, Driver Name: 3c509
<P>The EISA version of the 509. The current EISA version
uses the same 16 bit wide chip rather than a 32 bit
interface, so the performance increase isn't stunning.
Make sure the card is configured for EISA addressing mode.
Read the above 3c509 section for info on the driver.
<P>
<P>
<H3><A NAME="3c589"></A> 3c589 / 3c589B</H3>
<P>Status: Semi-Supported, Driver Name: 3c589
<P>Many people have been using this PCMCIA card for quite some time
now. Note that support for it is not (at present) included
in the default kernel source tree.
The "B" in the name means the same here as it does for
the 3c509 case.
<P>There are drivers available on Donald's ftp site and in
David Hinds PCMCIA package. You will also need
a supported PCMCIA controller chipset.
See
<A HREF="Ethernet-HOWTO-9.html#pcmcia">PCMCIA Support</A> for more
info on PCMCIA drivers, chipsets, socket enablers, etc.
<P>
<H3><A NAME="vortex"></A> 3c590 / 3c595</H3>
<P>Status: Supported, Driver Name: 3c59x
<P>These ``Vortex'' cards are for PCI bus machines, with the '590
being 10Mbps and the '595 being 3Com's 100Mbs offering.
Also note that you can run the '595 as a '590 (i.e. in a 10Mbps mode).
The driver is included in the v2.0 kernel source, but is
also continually being updated. If you have problems with the
driver in the v2.0 kernel, you
can get an updated driver from the following URL:
<P>
<A HREF="http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html">Vortex</A><P>Note that there are two different 3c590 cards out there, early
models that had 32kB of on-board memory, and later models that
only have 8kB of memory. Chances are you won't be
able to buy a new 3c59x for much longer, as it is being replaced
with the 3c90x card. If you are buying a used one off somebody,
try and get the 32kB version. The 3c595 cards have 64kB,
as you can't get away with only 8kB RAM at 100Mbps!
<P>A thanks to Cameron Spitzer and Terry Murphy of 3Com for
sending cards and documentation to Donald so he could write
the driver.
<P>Donald has set up a mailing list for Vortex driver support.
To join the list, just do:
<P><CODE>echo subscribe | /bin/mail
linux-vortex-request@cesdis.gsfc.nasa.gov</CODE>
<P>
<P>
<H3>3c592 / 3c597</H3>
<P>Status: Supported, Driver Name: 3c59x
<P>These are the EISA versions of the 3c59x
series of cards. The 3c592/3c597 (aka Demon) should work with
the vortex driver discussed above.
<P>
<H3>3c900 / 3c905 / 3c905B</H3>
<P>Status: Supported, Driver Name: 3c59x
<P>These cards (aka `Boomerang', aka EtherLink III XL) have been
released to take over the place of the 3c590/3c595 cards.
<P>The support for the Cyclone `B' revision was only recently added.
To use this card with older v2.0 kernels, you must obtain the
updated <CODE>3c59x.c</CODE> driver from Donald's site at:
<P>
<A HREF="http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html">Vortex-Page</A><P>If in doubt about anything then check out the above WWW page.
Donald has set up a mailing list for Vortex driver support
announcements and etc. To join the list, just do:
<P><CODE>echo subscribe | /bin/mail
linux-vortex-request@cesdis.gsfc.nasa.gov</CODE>
<P>
<H3>3c985</H3>
<P>Status: Supported, Driver Name: acenic
<P>This driver, by Jes Sorensen, is available in v2.2 kernels
It supports several other Gigabit cards in addition to
the 3Com model.
<P>
<H2><A NAME="accton"></A> <A NAME="ss5.2">5.2 Accton</A>
</H2>
<P>
<P>
<H3>Accton MPX</H3>
<P>Status: Supported, Driver Name: ne (+8390)
<P>Don't let the name fool you. This is still supposed to be a
NE2000 compatible card, and should work with the ne2000 driver.
<P>
<H3>Accton EN1203, EN1207, EtherDuo-PCI</H3>
<P>Status: Supported, Driver Name: de4x5, tulip
<P>This is another implementation of the DEC 21040 PCI chip.
The EN1207 card has the 21140, and also has a 10Base-2
connector, which has proved troublesome for some people
in terms of selecting that media. Using the card with
10Base-T and 100Base-T media have worked for others though.
So as with all purchases, you should try and make sure
you can return it if it doesn't work for you.
<P>See
<A HREF="#dec-21040">DEC 21040</A>
for more information on these cards, and the present driver
situation.
<P>
<H3>Accton EN2209 Parallel Port Adaptor (EtherPocket)</H3>
<P>Status: Semi-Supported, Driver Name: ?
<P>A driver for these parallel port adapters is available
but not yet part of the 2.0 or 2.1 kernel source. You have to
get the driver from:
<P><CODE>http://www.unix-ag.uni-siegen.de/~nils/accton_linux.html</CODE>
<P>
<P>
<H3>Accton EN2212 PCMCIA Card</H3>
<P>Status: Semi-Supported, Driver Name: ?
<P>David Hinds has been working on a driver for this card, and
you are best to check the latest release of his PCMCIA
package to see what the present status is.
<P>
<P>
<H2><A NAME="allied-telesis"></A> <A NAME="ss5.3">5.3 Allied Telesyn/Telesis</A>
</H2>
<P>
<P>
<H3><A NAME="at-1500"></A> AT1500</H3>
<P>Status: Supported, Driver Name: lance
<P>These are a series of low-cost ethercards using the 79C960 version
of the AMD LANCE. These are bus-master cards, and hence one of
the faster ISA bus ethercards available.
<P>DMA selection and chip numbering information can be found in
<A HREF="#lance">AMD LANCE</A>.
<P>More technical information on AMD LANCE based Ethernet cards
can be found in
<A HREF="Ethernet-HOWTO-8.html#amd-notes">Notes on AMD...</A>.
<P>
<H3><A NAME="at1700"></A> AT1700</H3>
<P>Status: Supported, Driver Name: at1700
<P>Note that to access this driver during <CODE>make config</CODE>
you still have to answer `Y' when asked ``Prompt for
development and/or incomplete code/drivers?'' at
the first. This is simply due to lack of feedback on the
driver stability due to it being a relatively rare card.
If you have problems with the driver that ships with
the kernel then you may be interested in the alternative
driver available at:
<CODE>http://www.cc.hit-u.ac.jp/nagoya/at1700/</CODE>
<P>The Allied Telesis AT1700 series ethercards are based
on the Fujitsu MB86965. This chip uses a programmed
I/O interface, and a pair of fixed-size transmit
buffers. This allows small groups of packets to
be sent back-to-back, with a short pause while
switching buffers.
<P>A unique feature is the ability to drive 150ohm STP
(Shielded Twisted Pair) cable commonly installed for
Token Ring, in addition to 10baseT 100ohm UTP
(unshielded twisted pair). A fibre optic
version of the card (AT1700FT) exists as well.
<P>The Fujitsu chip used on the AT1700 has a design flaw:
it can only be fully reset by doing a power cycle of the machine.
Pressing the reset button doesn't reset the bus interface. This
wouldn't be so bad, except that it can only be reliably detected
when it has been freshly reset. The solution/work-around is to
power-cycle the machine if the kernel has a problem detecting
the AT1700.
<P>
<H3><A NAME="at2450"></A> AT2450</H3>
<P>Status: Supported, Driver Name: pcnet32
<P>This is the PCI version of the AT1500, and it doesn't suffer
from the problems that the Boca 79c970 PCI card does.
DMA selection and chip numbering information can be found in
<A HREF="#lance">AMD LANCE</A>.
<P>More technical information on AMD LANCE based Ethernet cards
can be found in
<A HREF="Ethernet-HOWTO-8.html#amd-notes">Notes on AMD...</A>.
<P>
<H3>AT2500</H3>
<P>Status: Semi-Supported, Driver Name: rtl8139
<P>This card uses the RealTek 8139 chip - see the
section
<A HREF="#rtl8139">RealTek 8139</A>.
<P>
<H3><A NAME="at2540"></A> AT2540FX</H3>
<P>Status: Semi-Supported, Driver Name: eepro100
<P>This card uses the i82557 chip, and hence may/should work
with the eepro100 driver. If you try this please send in
a report so this information can be updated.
<P>
<H2><A NAME="amd"></A> <A NAME="ss5.4">5.4 AMD / Advanced Micro Devices</A>
</H2>
<P>
<P>Carl Ching of AMD was kind enough to provide a very
detailed description of all the relevant AMD ethernet
products which helped clear up this section.
<P>
<H3><A NAME="lance"></A> AMD LANCE (7990, 79C960/961/961A, PCnet-ISA)</H3>
<P>Status: Supported, Driver Name: lance
<P>There really is no AMD ethernet card. You are probably reading this
because the only markings you could find on your card said AMD
and the above number. The 7990 is the original `LANCE' chip,
but most stuff (including this document) refer to all these
similar chips as `LANCE' chips. (...incorrectly, I might add.)
<P>These above numbers refer to chips from AMD
that are the heart of many ethernet cards.
For example, the Allied Telesis AT1500 (see
<A HREF="#at-1500">AT1500</A>) and the NE1500/2100 (see
<A HREF="#ne1500">NE1500</A>) use these chips.
<P>The 7990/79c90 have long been replaced by newer versions.
The 79C960 (a.k.a. PCnet-ISA) essentially contains the 79c90
core, along with all the other hardware support required, which
allows a single-chip ethernet solution. The 79c961 (PCnet-ISA+)
is a jumperless Plug and Play version of the '960. The final
chip in the ISA series is the 79c961A (PCnet-ISA II), which
adds full duplex capabilities.
All cards with one of these chips should work with
the lance.c driver, with the exception of very old cards that
used the original 7990 in a shared memory configuration. These
old cards can be spotted by the lack of jumpers for a DMA channel.
<P>One common problem people have is the `busmaster arbitration
failure' message. This is printed out when the LANCE driver
can't get access to the bus after a reasonable amount of time
has elapsed (50us). This usually indicates that the motherboard
implementation of bus-mastering DMA is broken, or some other device
is hogging the bus, or there is a DMA channel conflict. If your BIOS
setup has the `GAT option' (for Guaranteed Access Time) then try
toggling/altering that setting to see if it helps.
<P>Also note that the driver only looks at the addresses:
<CODE>0x300, 0x320, 0x340, 0x360</CODE> for a valid card, and any
address supplied by an <CODE>ether=</CODE> boot argument is silently
ignored (this will be fixed) so make sure your card is configured
for one of the above I/O addresses for now.
<P>The driver will still work fine, even
if more than 16MB of memory is installed, since low-memory
`bounce-buffers' are used when needed (i.e. any data from
above 16MB is copied into a buffer below 16MB before being
given to the card to transmit.)
<P>The DMA channel can be set with the low bits
of the otherwise-unused dev->mem_start value (a.k.a. PARAM_1).
(see
<A HREF="Ethernet-HOWTO-10.html#ether">PARAM_1</A>)
If unset it is probed for by enabling each free DMA channel
in turn and checking if initialization succeeds.
<P>The HP-J2405A board is an exception: with this board it's easy
to read the EEPROM-set values for the IRQ, and DMA.
<P>See
<A HREF="Ethernet-HOWTO-8.html#amd-notes">Notes on AMD...</A>
for more info on these chips.
<P>
<H3><A NAME="pcnet-32"></A> AMD 79C965 (PCnet-32)</H3>
<P>Status: Supported, Driver Name: pcnet32
<P>This is the PCnet-32 -- a 32 bit bus-master version of the
original LANCE chip for VL-bus and local bus systems.
chip. While these chips can be operated with the standard
<CODE>lance.c</CODE> driver, a 32 bit version (<CODE>pcnet32.c</CODE>) is
also available that does not have to concern itself with
any 16MB limitations associated with the ISA bus.
<P>
<H3><A NAME="pcnet-pci"></A> AMD 79C970/970A (PCnet-PCI)</H3>
<P>Status: Supported, Driver Name: pcnet32
<P>This is the PCnet-PCI -- similar to the PCnet-32, but designed
for PCI bus based systems. Please see the
above PCnet-32 information.
This means that you need to build a kernel with
PCI BIOS support enabled. The '970A adds full duplex support
along with some other features to the original '970 design.
<P>Note that the Boca implementation of the 79C970 fails on
fast Pentium machines. This is a hardware problem, as it
affects DOS users as well. See the Boca section for more
details.
<P>
<H3>AMD 79C971 (PCnet-FAST)</H3>
<P>Status: Supported, Driver Name: pcnet32
<P>This is AMD's 100Mbit chip for PCI systems, which also supports
full duplex operation. It was introduced in June 1996.
<P>
<H3>AMD 79C972 (PCnet-FAST+)</H3>
<P>Status: Unknown, Driver Name: pcnet32
<P>This should also work just like the '971 but this has yet to
be confirmed.
<P>
<H3>AMD 79C974 (PCnet-SCSI)</H3>
<P>Status: Supported, Driver Name: pcnet32
<P>This is the PCnet-SCSI -- which is basically treated like
a '970 from an Ethernet point of view.
Also see the above information. Don't ask if the
SCSI half of the chip is supported -- this is the
<EM>Ethernet-HowTo</EM>, not the SCSI-HowTo.
<P>
<H2><A NAME="ansel"></A> <A NAME="ss5.5">5.5 Ansel Communications</A>
</H2>
<P>
<P>
<H3>AC3200 EISA</H3>
<P>Status: Semi-Supported, Driver Name: ac3200
<P>Note that to access this driver during <CODE>make config</CODE>
you still have to answer `Y' when asked ``Prompt for
development and/or incomplete code/drivers?'' at
the first. This is simply due to lack of feedback on the
driver stability due to it being a relatively rare card.
<P>This driver is included in the present kernel as an
alpha test driver. It is based on the common NS8390
chip used in the ne2000 and wd80x3 cards.
Please see
<A HREF="Ethernet-HOWTO-3.html#alfa">Alpha Drivers</A> in
this document for important information regarding
alpha drivers.
<P>If you use it, let one of us know how things work out,
as feedback has been low, even though the driver has
been in the kernel since v1.1.25.
<P>If you intend on using this driver as a loadable module
you should probably see
<A HREF="Ethernet-HOWTO-10.html#modules">Using the Ethernet Drivers as Modules</A>
for module specific information.
<P>
<H2><A NAME="ss5.6">5.6 Apricot</A>
</H2>
<P>
<P>
<H3>Apricot Xen-II On Board Ethernet</H3>
<P>Status: Semi-Supported, Driver Name: apricot
<P>This on board ethernet uses an i82596 bus-master chip.
It can only be at I/O address <CODE>0x300</CODE>.
By looking at the driver source,
it appears that the IRQ is also hardwired to 10.
<P>Earlier versions of the driver had a tendency to think
that anything living at <CODE>0x300</CODE> was an apricot NIC.
Since then the hardware address is checked to avoid these
false detections.
<P>
<H2><A NAME="arcnet"></A> <A NAME="ss5.7">5.7 Arcnet</A>
</H2>
<P>Status: Supported, Driver Name: arcnet (arc-rimi, com90xx, com20020)
<P>With the very low cost and better performance of ethernet,
chances are that most places will be giving away their Arcnet
hardware for free, resulting in a lot of home systems with Arcnet.
<P>An advantage of Arcnet is that all of the cards have identical
interfaces, so one driver will work for everyone. It also has
built in error handling so that it supposedly never loses a packet.
(Great for UDP traffic!)
<P>Avery Pennarun's arcnet driver has been in the
default kernel sources since 1.1.80. The arcnet driver
uses `arc0' as its name instead of the usual `eth0' for
ethernet devices.
Bug reports and success stories can be mailed to:
<P><CODE>apenwarr@foxnet.net</CODE>
<P>There are information files contained in the standard kernel for
setting jumpers and general hints.
<P>Supposedly the driver also works with the 100Mbs ARCnet cards
as well!
<P>
<H2><A NAME="ss5.8">5.8 AT&T</A>
</H2>
<P>
<P>Note that AT&T's StarLAN is an orphaned technology, like
SynOptics LattisNet, and can't be used in a standard 10Base-T
environment, without a hub that `speaks' both.
<P>
<H3>AT&T T7231 (LanPACER+)</H3>
<P>Status: Not Supported.
<P>These StarLAN cards use an interface similar to the i82586
chip. At one point, Matthijs Melchior
(<CODE>matthijs.n.melchior@att.com</CODE>) was playing with the 3c507
driver, and almost had something useable working. Haven't
heard much since that.
<P>
<H2><A NAME="boca"></A> <A NAME="ss5.9">5.9 Boca Research</A>
</H2>
<P>
<P>Yes, they make more than just multi-port serial cards. :-)
<P>
<H3><A NAME="boca-ben"></A> Boca BEN (ISA, VLB, PCI)</H3>
<P>Status: Supported, Driver Name: lance, pcnet32
<P>These cards are based on AMD's PCnet chips.
Perspective buyers should be warned that many users have had
endless problems with these VLB/PCI cards. Owners of fast Pentium
systems have been especially hit. Note that this is not a driver
problem, as it hits DOS/Win/NT users as well.
Boca's technical support number is (407) 241-8088, and you
can also reach them at <CODE>75300.2672@compuserve.com</CODE>.
The older ISA cards don't appear to suffer the same problems.
<P>Donald did a comparitive test with a Boca PCI card and
a similar Allied Telsyn PCnet/PCI implementation, which showed
that the problem lies in Boca's implementation of the PCnet/PCI
chip. These test results can be accessed on Don's www server.
<P>
<A HREF="http://cesdis.gsfc.nasa.gov/linux/">Linux at CESDIS</A><P>Boca is offering a `warranty repair' for
affected owners, which involves adding one of the missing
capacitors, but it appears that this fix doesn't work 100
percent for most people, although it helps some.
<P>If you are <EM>still</EM> thinking of buying one of these cards, then
at least try and get a 7 day unconditional return policy,
so that if it doesn't work properly in your system, you
can return it.
<P>More general information on the AMD chips can be found in
<A HREF="#lance">AMD LANCE</A>.
<P>More technical information on AMD LANCE based Ethernet cards
can be found in
<A HREF="Ethernet-HOWTO-8.html#amd-notes">Notes on AMD...</A>.
<P>
<H2><A NAME="ctron"></A> <A NAME="ss5.10">5.10 Cabletron</A>
</H2>
<P>
<P>Donald writes:
`Yes, another one of these companies that won't release its
programming information. They waited for months before actually
confirming that all their information was proprietary, deliberately
wasting my time. Avoid their cards like the plague if you can.
Also note that some people have phoned Cabletron, and have been
told things like `a D. Becker is working on a driver
for linux' -- making it sound like I work for them. This is
NOT the case.'
<P>
<P>Apparently Cabletron has changed their policy with respect to
programming information (like Xircom) since Donald made the above
comment several years ago -- send e-mail to <CODE>support@ctron.com</CODE>
if you want to verify this or ask for programming information.
However, at this point in time, there is little demand for
modified/updated drivers for the older E20xx and E21xx cards.
<P>
<P>
<H3><A NAME="e10xx"></A> E10**, E10**-x, E20**, E20**-x</H3>
<P>Status: Semi-Supported, Driver Name: ne (+8390)
<P>These are NEx000 almost-clones that are reported to
work with the standard NEx000 drivers, thanks to a
ctron-specific check during the probe. If there are
any problems, they are unlikely to be fixed, as the
programming information is unavailable.
<P>
<H3><A NAME="e2100"></A> E2100</H3>
<P>Status: Semi-Supported, Driver Name: e2100 (+8390)
<P>Again, there is not much one can do when the
programming information is proprietary.
The E2100 is a poor design. Whenever it maps its
shared memory in during a packet transfer, it
maps it into the <EM>whole 128K region!</EM> That means you
<B>can't</B> safely use another interrupt-driven shared
memory device in that region, including another E2100.
It will work most of the time, but every once in
a while it will bite you. (Yes, this problem can
be avoided by turning off interrupts while
transferring packets, but that will almost certainly
lose clock ticks.) Also, if you mis-program the board,
or halt the machine at just the wrong moment, even
the reset button won't bring it back. You will <EM>have</EM>
to turn it off and <EM>leave</EM> it off for about 30 seconds.
<P>Media selection is automatic, but you can override this
with the low bits of the dev->mem_end parameter.
See
<A HREF="Ethernet-HOWTO-10.html#ether">PARAM_2</A>. Module users
can specify an <CODE>xcvr=N</CODE> value as an <CODE>option</CODE> in
the <CODE>/etc/conf.modules</CODE> file.
<P>Also, don't confuse the E2100 for a NE2100 clone.
The E2100 is a shared memory NatSemi DP8390 design,
roughly similar to a brain-damaged WD8013, whereas
the NE2100 (and NE1500) use a bus-mastering AMD
LANCE design.
<P>There is an E2100 driver included in the standard kernel.
However, seeing as programming info isn't available,
don't expect bug-fixes. Don't use one
unless you are already stuck with the card.
<P>If you intend on using this driver as a loadable module
you should probably see
<A HREF="Ethernet-HOWTO-10.html#modules">Using the Ethernet Drivers as Modules</A>
for module specific information.
<P>
<H3><A NAME="e2200"></A> E22**</H3>
<P>Status: Semi-Supported, Driver Name: lance
<P>According to information in a Cabletron Tech Bulletin, these
cards use the standard AMD PC-Net chipset (see
<A HREF="#lance">AMD PC-Net</A>) and should work with the generic lance
driver.
<P>
<P>
<H2><A NAME="ss5.11">5.11 Cogent</A>
</H2>
<P>
<P>Here is where and how to reach them:
<P>
<P>
<PRE>
Cogent Data Technologies, Inc.
175 West Street, P.O. Box 926
Friday Harbour, WA 98250, USA.
Cogent Sales
15375 S.E. 30th Place, Suite 310
Bellevue, WA 98007, USA.
Technical Support:
Phone (360) 378-2929 between 8am and 5pm PST
Fax (360) 378-2882
Compuserve GO COGENT
Bulletin Board Service (360) 378-5405
Internet: support@cogentdata.com
</PRE>
<P>
<H3>EM100-ISA/EISA</H3>
<P>Status: Semi-Supported, Driver Name: smc9194
<P>These cards use the SMC 91c100 chip and may work with the
SMC 91c92 driver, but this has yet to be verified.
<P>
<H3>Cogent eMASTER+, EM100-PCI, EM400, EM960, EM964</H3>
<P>Status: Supported, Driver Name: de4x5, tulip
<P>These are yet another DEC 21040 implementation that should
hopefully work fine with the standard 21040 driver.
<P>The EM400 and the EM964 are four port cards using a
DEC 21050 bridge and 4 21040 chips.
<P>See
<A HREF="#dec-21040">DEC 21040</A>
for more information on these cards, and the present driver
situation.
<P>
<H2><A NAME="ss5.12">5.12 Compaq</A>
</H2>
<P>
<P>Compaq aren't really in the business of making ethernet
cards, but a lot of their systems have embedded ethernet
controllers on the motherboard.
<P>
<H3>Compaq Deskpro / Compaq XL (Embedded AMD Chip)</H3>
<P>Status: Supported, Driver Name: pcnet32
<P>Machines such as the XL series have an AMD 79c97x PCI chip
on the mainboard that can be used with the standard LANCE
driver. But before you can use it, you have to do some
trickery to get the PCI BIOS to a place where Linux can
see it. Frank Maas was kind enough to provide the
details:
<P>`` The problem with this Compaq machine however is that the PCI
directory is loaded in high memory, at a spot where the Linux
kernel can't (won't) reach. Result: the card is never detected nor
is it usable (sideline: the mouse won't work either)
The workaround (as described thoroughly in
http://www-c724.uibk.ac.at/XL/)
is to load MS-DOS, launch a little driver Compaq wrote and then
load the Linux kernel using LOADLIN. Ok, I'll give you time to
say `yuck, yuck', but for now this is the only working solution
I know of. The little driver simply moves the PCI directory to
a place where it is normally stored (and where Linux can find it).''
<P>More general information on the AMD chips can be found in
<A HREF="#lance">AMD LANCE</A>.
<P>
<H3>Compaq Nettelligent/NetFlex (Embedded ThunderLAN Chip)</H3>
<P>Status: Supported, Driver Name: tlan
<P>These systems use a Texas Instruments ThunderLAN chip
Information on the ThunderLAN driver can be found in
<A HREF="#tlan">ThunderLAN</A>.
<P>
<P>
<P>
<H2><A NAME="ss5.13">5.13 Danpex</A>
</H2>
<P>
<P>
<H3>Danpex EN9400</H3>
<P>Status: Supported, Driver Name: de4x5, tulip
<P>Yet another card based on the DEC 21040 chip, reported to
work fine, and at a relatively cheap price.
<P>See
<A HREF="#dec-21040">DEC 21040</A>
for more information on these cards, and the present driver
situation.
<P>
<H2><A NAME="d-link"></A> <A NAME="ss5.14">5.14 D-Link</A>
</H2>
<P>
<P>
<H3><A NAME="de-100"></A> DE-100, DE-200, DE-220-T, DE-250</H3>
<P>Status: Supported, Driver Name: ne (+8390)
<P>Some of the early D-Link cards didn't have the <CODE>0x57</CODE>
PROM signature, but the ne2000 driver knows about them.
For the software configurable cards, you can get the
config program from <CODE>www.dlink.com</CODE>.
The DE2** cards were the most
widely reported as having the spurious transfer address
mismatch errors with early versions of linux.
Note that there are also cards from
Digital (DEC) that are also named DE100 and DE200,
but the similarity stops there.
<P>
<H3><A NAME="de-520"></A> DE-520</H3>
<P>Status: Supported, Driver Name: pcnet32
<P>This is a PCI card using the PCI version of AMD's LANCE chip.
DMA selection and chip numbering information can be found in
<A HREF="#lance">AMD LANCE</A>.
<P>More technical information on AMD LANCE based Ethernet cards
can be found in
<A HREF="Ethernet-HOWTO-8.html#amd-notes">Notes on AMD...</A>.
<P>
<H3>DE-528</H3>
<P>Status: Supported, Driver Name: ne, ne2k-pci (+8390)
<P>Apparently D-Link have also started making PCI NE2000 clones.
<P>
<P>
<H3><A NAME="de-530"></A> DE-530</H3>
<P>Status: Supported, Driver Name: de4x5, tulip
<P>This is a generic DEC 21040 PCI chip implementation,
and is reported to work with the generic 21040 tulip driver.
<P>See
<A HREF="#dec-21040">DEC 21040</A>
for more information on these cards, and the present driver
situation.
<P>
<H3><A NAME="de-600"></A> DE-600</H3>
<P>Status: Supported, Driver Name: de600
<P>Laptop users and other folk who might want a quick
way to put their computer onto the ethernet may want
to use this. The driver is included with the default
kernel source tree.
Bjorn Ekwall <CODE>bj0rn@blox.se</CODE> wrote the driver.
Expect about 180kb/s transfer speed from this via the
parallel port. You should read the README.DLINK
file in the kernel source tree.
<P>Note that the device name that you pass to <CODE>ifconfig</CODE>
is <EM>now</EM> <CODE>eth0</CODE> and not the previously
used <CODE>dl0</CODE>.
<P>If your parallel port is <EM>not</EM> at the standard <CODE>0x378</CODE>
then you will have to recompile. Bjorn writes:
``Since the DE-620 driver tries to sqeeze the last microsecond
from the loops, I made the irq and port address constants instead
of variables. This makes for a usable speed, but it also means
that you can't change these assignements from e.g. lilo;
you _have_ to recompile...'' Also note that some laptops
implement the on-board parallel port at <CODE>0x3bc</CODE> which
is where the parallel ports on monochrome cards were/are.
<P>
<H3><A NAME="de-620"></A> DE-620</H3>
<P>Status: Supported, Driver Name: de620
<P>Same as the DE-600, only with two output formats.
Bjorn has written a driver for this model,
for kernel versions 1.1 and above. See the above information
on the DE-600.
<P>
<H3><A NAME="de-650"></A> DE-650</H3>
<P>Status: Semi-Supported, Driver Name: de650 (?)
<P>Some people have been using this PCMCIA card for
some time now with their notebooks. It is a basic
8390 design, much like a NE2000. The LinkSys PCMCIA
card and the IC-Card Ethernet are supposedly DE-650 clones
as well. Note that at present, this driver is
<EM>not</EM> part of the standard kernel, and so you will
have to do some patching.
<P>See
<A HREF="Ethernet-HOWTO-9.html#pcmcia">PCMCIA Support</A> in this document,
and if you can, have a look at:
<P>
<A HREF="http://cesdis.gsfc.nasa.gov/linux/pcmcia.html">Don's PCMCIA Stuff</A><P>
<H2><A NAME="dfi"></A> <A NAME="ss5.15">5.15 DFI</A>
</H2>
<P>
<P>
<H3><A NAME="dfi-300"></A> DFINET-300 and DFINET-400</H3>
<P>Status: Supported, Driver Name: ne (+8390)
<P>These cards are now detected (as of 0.99pl15) thanks to
Eberhard Moenkeberg <CODE>emoenke@gwdg.de</CODE> who noted that
they use `DFI' in the first 3 bytes of the prom, instead
of using <CODE>0x57</CODE> in bytes 14 and 15, which is what all the
NE1000 and NE2000 cards use. (The 300 is an 8 bit
pseudo NE1000 clone, and the 400 is a pseudo NE2000 clone.)
<P>
<P>
<H2><A NAME="dec"></A> <A NAME="ss5.16">5.16 Digital / DEC</A>
</H2>
<P>
<P>
<H3><A NAME="dec-200"></A> DEPCA, DE100/1, DE200/1/2, DE210, DE422</H3>
<P>Status: Supported, Driver Name: depca
<P>There is documentation included in the source file
`depca.c', which includes info on how to use more than
one of these cards in a machine. Note that the DE422 is
an EISA card. These cards are all based on the AMD LANCE chip.
See
<A HREF="#lance">AMD LANCE</A> for more info.
A maximum of two of the ISA cards can be used, because they
can only be set for <CODE>0x300</CODE> and <CODE>0x200</CODE> base I/O address.
If you are intending to do this, please read the notes in
the driver source file <CODE>depca.c</CODE> in the standard kernel
source tree.
<P>This driver will also work on Alpha CPU based machines, and
there are various ioctl()s that the user can play with.
<P>
<H3><A NAME="dec-ewrk3"></A> Digital EtherWorks 3 (DE203, DE204, DE205)</H3>
<P>Status: Supported, Driver Name: ewrk3
<P>These cards use a proprietary
chip from DEC, as opposed to the LANCE chip used in the
earlier cards like the DE200. These cards support both shared
memory or programmed I/O, although you take about a 50%performance hit if you use PIO mode. The shared memory size can
be set to 2kB, 32kB or 64kB, but only 2 and 32 have been tested
with this driver. David says that the performance is virtually
identical between the 2kB and 32kB mode. There is more information
(including using the driver as a loadable module) at the top
of the driver file <CODE>ewrk3.c</CODE> and also in <CODE>README.ewrk3</CODE>.
Both of these files come with the standard kernel distribution.
This driver has Alpha CPU support like depca.c does.
<P>The standard driver has a number
of interesting ioctl() calls that can be used to get or clear
packet statistics, read/write the EEPROM, change the
hardware address, and the like. Hackers can see the source
code for more info on that one.
<P>David has also written a configuration utility for this
card (along the lines of the DOS program <CODE>NICSETUP.EXE</CODE>)
along with other tools. These can be found on
most Linux FTP sites in the directory
<CODE>/pub/Linux/system/Network/management</CODE> -- look for the
file <CODE>ewrk3tools-X.XX.tar.gz</CODE>.
<P>
<P>
<H3><A NAME="dec-eisa"></A> DE425 EISA, DE434, DE435, DE500 </H3>
<P>Status: Supported, Driver Name: de4x5, tulip
<P>These cards are based on the 21040 chip mentioned below.
The DE500 uses the 21140 chip to provide 10/100Mbs
ethernet connections.
Have a read of the 21040 section below for extra info.
There are also some compile-time options available for
non-DEC cards using this driver. Have a look at
<CODE>README.de4x5</CODE> for details.
<P>All the Digital cards will autoprobe for their media (except,
temporarily, the DE500 due to a patent issue).
<P>This driver is also Alpha CPU ready and supports being loaded
as a module. Users can access the driver internals through
ioctl() calls - see the 'ewrk3' tools and the de4x5.c sources
for information about how to do this.
<P>
<H3><A NAME="dec-21040"></A> DEC 21040, 21041, 2114x, Tulip </H3>
<P>Status: Supported, Driver Name: de4x5, tulip
<P>The DEC 21040 is a bus-mastering single chip ethernet solution
from Digital, similar to AMD's PCnet chip. The 21040 is
specifically designed for the PCI bus architecture.
SMC's new EtherPower PCI card uses this chip.
<P>You have a choice of <EM>two</EM> drivers for cards based on this
chip. There is the DE425 driver discussed above, and the
generic 21040 `tulip' driver.
<P><B>Warning:</B> Even though your card may be based upon this chip,
<EM>the drivers may not work for you</EM>. David C. Davies writes:
<P>``There are no guarantees that either `tulip.c' OR `de4x5.c'
will run any DC2114x based card other than those they've been
written to support. WHY?? You ask. Because there is a register,
the General Purpose Register (CSR12) that (1) in the DC21140A is
programmable by each vendor and they all do it differently
(2) in the DC21142/3 this is now an SIA control register
(a la DC21041). The only small ray of hope is that we can decode the
SROM to help set up the driver. However, this is not a guaranteed
solution since some vendors (e.g. SMC 9332 card) don't follow the
Digital Semiconductor recommended SROM programming format."
<P>In non-technical terms, this means that if you aren't sure that an
unknown card with a DC2114x chip will work with the linux driver(s),
then make sure you can return the card to the place of
purchase <EM>before</EM> you pay for it.
<P>The updated 21041 chip is also found in place of the 21040
on most of the later SMC EtherPower cards.
The 21140 is for supporting 100Base-? and
works with the Linux drivers for the 21040 chip.
To use David's <CODE>de4x5</CODE> driver with non-DEC cards, have a
look at <CODE>README.de4x5</CODE> for details.
<P>Donald has used SMC EtherPower-10/100 cards to develop
the `tulip' driver. Note that the driver that is
in the standard kernel tree at the moment is not the most
up to date version. If you are having trouble with this driver,
you should get the newest version from Donald's ftp/WWW
site.
<P>
<A HREF="http://cesdis.gsfc.nasa.gov/linux/drivers/tulip.html">Tulip Driver</A><P>The above URL also contains a (non-exhaustive) list of
various cards/vendors that use the 21040 chip.
<P>Also note that the tulip driver is still considered an <EM>alpha</EM>
driver (see
<A HREF="Ethernet-HOWTO-3.html#alfa">Alpha Drivers</A>) at the
moment, and should be treated as such. To use it, you
will have to edit <CODE>arch/i386/config.in</CODE> and
uncomment the line for <CODE>CONFIG_DEC_ELCP</CODE> support.
<P>Donald has even set up a mailing list for tulip driver
support announcements, etc. To join it just type:
<P><CODE>echo subscribe | /bin/mail
linux-tulip-request@cesdis.gsfc.nasa.gov</CODE>
<P>
<H2><A NAME="ss5.17">5.17 Farallon</A>
</H2>
<P>Farallon sells EtherWave adaptors and transceivers. This device
allows multiple 10baseT devices to be daisy-chained.
<P>
<H3>Farallon Etherwave</H3>
<P>Status: Supported, Driver Name: 3c509
<P>This is reported to be a 3c509 clone that includes the
EtherWave transceiver. People have used these successfully
with Linux and the present 3c509 driver. They are too expensive
for general use, but are a great option for special cases. Hublet
prices start at $125, and Etherwave
adds $75-$100 to the price of the board -- worth
it if you have pulled one wire too few, but not if you are two
network drops short.
<P>
<H2><A NAME="ss5.18">5.18 Fujitsu</A>
</H2>
<P>
<P>Unlike many network chip manufacturers, Fujitsu have also
made and sold some network cards based upon their chip.
<P>
<H3>Fujitsu FMV-181/182/183/184</H3>
<P>Status: Supported, Driver Name: fmv18x
<P>According to the driver, these cards are a straight forward
Fujitsu MB86965 implementation, which would make them
very similar to the Allied Telesis AT1700 cards.
<P>
<H2><A NAME="hp"></A> <A NAME="ss5.19">5.19 Hewlett Packard</A>
</H2>
<P>
<P>The 272** cards use programmed I/O, similar to the NE*000 boards,
but the data transfer port can be `turned off' when you aren't
accessing it, avoiding problems with autoprobing drivers.
<P>Thanks to Glenn Talbott for helping clean up the confusion in this
section regarding the version numbers of the HP hardware.
<P>
<H3><A NAME="hp-27245a"></A> 27245A</H3>
<P>Status: Supported, Driver Name: hp (+8390)
<P>8 Bit 8390 based 10BaseT, not recommended for all the
8 bit reasons. It was re-designed a couple years
ago to be highly integrated which caused some
changes in initialization timing which only
affected testing programs, not LAN drivers. (The
new card is not `ready' as soon after switching
into and out of loopback mode.)
<P>If you intend on using this driver as a loadable module
you should probably see
<A HREF="Ethernet-HOWTO-10.html#modules">Using the Ethernet Drivers as Modules</A>
for module specific information.
<P>
<H3>HP EtherTwist, PC Lan+ (27247, 27252A)</H3>
<P>Status: Supported, Driver Name: hp+ (+8390)
<P>The HP PC Lan+ is different to the standard HP PC Lan
card. This driver was added to the list of drivers in the standard
kernel during the v1.1.x development cycle. It can be
operated in either a PIO mode like a ne2000, or a shared
memory mode like a wd8013.
<P>The 47B is a 16 Bit 8390 based 10BaseT w/AUI, and
the 52A is a 16 Bit 8390 based ThinLAN w/AUI.
These cards have 32K onboard RAM for Tx/Rx packet buffering
instead of the usual 16KB, and they both offer LAN
connector autosense.
<P>If you intend on using this driver as a loadable module
you should probably see
<A HREF="Ethernet-H
