From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: pc file server kernel: caveats
Date: Tue, 8 Aug 1995 16:39:16 -0400 [thread overview]
Message-ID: <19950808203916.lW7GojCr0qzlGEFcqt7BNj8jpaXILl_QijTnB-KBQ-w@z> (raw)
the pc file server kernel's ether509 driver needs similar changes
to /sys/src/9/pc/ether509.c: specifically, it needs to loop until
there aren't any more interrupts waiting. otherwise, under load
it can suddenly stop seeing further interrupts and things time out.
i have the impression that this is more likely to happen with the
newer 3c509b than with the original 3c509.
the pc file server decides my 16 Mbyte AMD486dx4/100 (no-obvious-name clone) motherboard
has 256 Mbytes (would be nice). not surprisingly, it then blows up in iobufinit.
i've no idea what the m/board is doing that causes the probe
not to detect that the memory subsystem has wrapped the
addresses; perhaps this board doesn't do the usual thing.
it's happy if the probe is limited to 128 Mbytes.
reply other threads:[~1995-08-08 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19950808203916.lW7GojCr0qzlGEFcqt7BNj8jpaXILl_QijTnB-KBQ-w@z \
--to=forsyth@plan9.cs.york.ac.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).