9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pc boot and ether drivers
Date: Tue, 16 Nov 2004 18:09:49 -0800	[thread overview]
Message-ID: <8646f4629a0e396e87b1c335bb542adf@collyer.net> (raw)
In-Reply-To: <Pine.BSI.4.58.0411161553470.6130@malasada.lava.net>

The internals of the bootstraps are different from the internals of
the kernels (which differ from each other).  For example, the kernels
have machinery such as kernel processes available to drivers.  Some of
these differences could be papered over with #defines and
compatibility functions.  On the other hand, the bootstrap drivers
don't have to be very sophisticated.

I'd love to have just one set of drivers, but there doesn't seem to be
much interest-and-energy available to reconcile the kernels with each
other and the bootstraps.



  reply	other threads:[~2004-11-17  2:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17  1:55 Tim Newsham
2004-11-17  2:09 ` geoff [this message]
2004-11-17  2:11 ` jmk
2004-11-18  0:54   ` Vester Thacker
2004-11-18  1:28     ` Eric Van Hensbergen
2004-11-18  2:32       ` Karl Magdsick
2004-11-18  2:43         ` geoff
2004-11-18  3:09           ` Tim Newsham
2004-11-18  3:16             ` geoff
2004-11-18  3:54               ` Tim Newsham
2004-11-18  4:01                 ` Russ Cox
2004-11-18  4:53                   ` jmk
2004-11-18  6:04                     ` Vester Thacker
2004-11-18 10:39                       ` C H Forsyth
2004-11-18 11:45                         ` Vester Thacker
2004-11-18  7:10                 ` geoff
2004-11-18  4:16               ` bs
2004-11-18  3:40             ` Russ Cox
2004-11-18  4:26           ` Vester Thacker
2004-11-18  4:34             ` Vester Thacker
2004-11-18 16:23             ` Ronald G. Minnich
2004-11-18 15:08     ` Ronald G. Minnich

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=8646f4629a0e396e87b1c335bb542adf@collyer.net \
    --to=geoff@collyer.net \
    --cc=9fans@cse.psu.edu \
    /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).