From: jim mckie jmk@plan9.bell-labs.com
Subject: [9fans] Re: Plan 9 from Bell Labs - Frequently Asked
Date: Mon, 8 Dec 1997 13:08:42 -0500 [thread overview]
Message-ID: <19971208180842.6ZIw1QvkW0_6_eaVswSBkKsX9CBgzG2Q5yXdRnX7vcw@z> (raw)
>It is interesting that you bring this up...
>
>>Hello 9fans!
>>
>>FAQ says in comp.os.plan9:
>>>Ethernet Adapters
>>> 3Com 3C509, 3C509B are recommended. The EISA 3C579 works, but
>>> isn't worth the extra cost. The PCMCIA 3C589, PCI 3C590 and PCI
>>>! 3C595 (fast ethernet) also work. AMD 79C970 based adapters seem to
>>> work fine. SMC (WD) series up to the Elite (and the Elite Ultra),
>>> some NE2000 compatibles (including an NE4100 PCMCIA card) and one
>>> Eagle NE3210 EISA card. The 3Com 3C503 does not work at all under
>>>! load. The 3Com 3C595 is not supported.
>>Does 3C595 work or not?
>>
>>According to 3COME Home Page
>>the Fast EtherLink that 3COM currentlly sails are:
>>PCI: 3C905-TX, 3C905-T4
>>EISA: 3C597-TX
>>ISA: 3C515-TX
>
>I have a 3c509, 3c579, 3c597 and 3c905. The ISA card works, except
>under heavy receive load with an adaptec 1542 bus-master the small
>receive FIFO will drive you crazy!
>
>But the 32bit cards don't work worth a sh*t! After spending too
>much time going through Plan9 and Net/FreeBSD source I have determined
>these cards go into stupid mode on transmit when presented with
>bursts of receive data. In other words, if you rip a lot of data
>off the card or force a lot into the card, it works great. But just
>try a single compile session, which does full 8k reads and writes,
>and the cards go stupid. A cp of a ~large file in a directory will
>do it to.
>
>They will not accept any more data into the transmit FIFO, will not
>transmit what is in the FIFO and will not give you a TxAvail interrupt
>when the FIFO finally does drain!
>
>I don't have any documentation to the cards, so I'm in the dark.
>Any body want to help?
>
>David Butler
>gdb@dbSystems.com
which of the above cards are you classifying as 32-bit? the 579 and 597 are
32-bit (eisa). we have 579s and they work fine. the 597 probably won't work without
dealing with various chip errata.
the 905 is problematic: although it has compatibility with the older cards the
fifos are tiny and the card really has to be run in busmastering mode or it gums
up a lot (it works well enough in fifo mode to boot a kernel with b.com though).
in busmastering mode there are chip errata which have to be dealt with or it can
hang up too.
as i mentioned in a previous message i still have problems with the 905 so i'm
interested in any other experiences with it.
--jim
next reply other threads:[~1997-12-08 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-08 18:08 jim [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-12-11 2:37 jim
1997-12-10 22:18 G.David
1997-12-10 20:54 jim
1997-12-10 19:58 G.David
1997-12-10 16:50 G.David
1997-12-08 23:51 forsyth
1997-12-08 21:02 forsyth
1997-12-08 20:57 forsyth
1997-12-08 16:48 G.David
1997-12-06 16:58 jim
1997-12-06 6:27 Kenji
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19971208180842.6ZIw1QvkW0_6_eaVswSBkKsX9CBgzG2Q5yXdRnX7vcw@z \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).