From: rsc@research.att.com rsc@research.att.com
Subject: [9fans] plug and play woes
Date: Sun, 3 Aug 1997 18:47:23 -0400 [thread overview]
Message-ID: <19970803224723.kIT6UpdMIPNEvpMbuLnBUu9CxzKiyzmgdpR9hK24xFM@z> (raw)
I've been reading the last month worth of 9fans
after being away. Why not do most of the plug and
play stuff in b.com to initialize IRQs, etc., and
then load the kernel with appropriate plan9.ini lines
generated for it? Thus, the code that has to
worry about plug and play drops out of memory as soon
as the OS starts, and the kernel doesn't have to be
bothered. Note that I distinguish between plug and
play (PnP, the much-hyped garbage that your BIOS does
to you every time you boot) and cards that ``autoconfigure''
like 3Com cards and SoundBlasters. I'm not sure if this
distinction is a valid one. Perhaps autoconfig stuff
should be done in b.com as well... Just my 2¢.
Russ
next reply other threads:[~1997-08-03 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-03 22:47 rsc [this message]
1997-08-04 1:21 David
1997-08-04 3:29 jmk
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=19970803224723.kIT6UpdMIPNEvpMbuLnBUu9CxzKiyzmgdpR9hK24xFM@z \
--to=rsc@research.att.com \
/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).