From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] Re: Plan 9 from Bell Labs - Frequently Asked
Date: Mon, 8 Dec 1997 20:57:18 +0000 [thread overview]
Message-ID: <19971208205718.h3TVQo7lPJxSS1LCA7DdS6GJZt11KI0g8YtcQQ5_AFA@z> (raw)
i've been using a 3com XL quite happily for months now.
it will hang up if you haven't got the txashift change posted
here some time ago. the newer card has got a bigger fifo,
and the representation of the TxAvailable value differs
(it's in words, not bytes, or some such thing).
b.com needs a similar change.
i wasn't sure whether the plan9.bell-labs.com updates had
the change, but i thought they had. i haven't had a chance
to fetch the boddles to check. i've a feeling that the kernel's
driver has got the change but b.com's hasn't.
next reply other threads:[~1997-12-08 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-08 20:57 forsyth [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 18:08 jim
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=19971208205718.h3TVQo7lPJxSS1LCA7DdS6GJZt11KI0g8YtcQQ5_AFA@z \
--to=forsyth@caldo.demon.co.uk \
/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).