9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "ron minnich" <rminnich@gmail.com>
To: "Lucio De Re" <lucio@proxima.alt.za>,
	"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Again: (self)hosted Plan9? Was: [9fans] extending xen to allow driver
Date: Wed,  6 Dec 2006 22:01:36 -0700	[thread overview]
Message-ID: <13426df10612062101i3f2485ffyec9409d5c6fc851c@mail.gmail.com> (raw)
In-Reply-To: <a1a48546d919454b28ab4b56dd17ab70@proxima.alt.za>

On 12/6/06, Lucio De Re <lucio@proxima.alt.za> wrote:
> > I guess the Plan9 Kernel could be separated in two layers, the upper
> > one just doing "high-level" and 9P-protocol stuff, and a lower one,
> > providing the #-channel interfaces to the upper layer and doing I/O.
>
> My thoughts are along similar lines.  My approach would be to expose
> the device drivers in a hardware dependent "BIOS" as Plan 9 devices,
> adding only as much OS glue at this level as makes this possible.
> This would be as close as damn what we know as 9load today.
>
> The Plan 9 kernel is the only one that would be able to interface to
> this BIOS currently, but over time it ought to be possible, mutatis
> mutandis, to boot other OSes on this layer.  My dream is that the BIOS
> could then be extended by the hordes of device driver writers and
> every compliant OS would be able to use new devices immediately.

well, we're trying to sort of do that now. We're using linux as the
driver layer. It's not what you guys want implementation-wise, but it
is something  like the idea.

It's not that drivers are fundamentally hard. It's that the hardware
we work with is undocumented crap. Linux drivers know all the secrets;
we're riding on that knowledge.

ron


  reply	other threads:[~2006-12-07  5:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 16:59 [9fans] extending xen to allow driver development in Plan 9 ron minnich
2006-12-06 19:58 ` Richard Miller
2006-12-06 21:27 ` Again: (self)hosted Plan9? Was: " Georg Lehner
2006-12-07  4:32   ` Again: (self)hosted Plan9? Was: [9fans] extending xen to allow driver Lucio De Re
2006-12-07  5:01     ` ron minnich [this message]
2006-12-07  5:46       ` Again: (self)hosted Plan9? Was: [9fans] extending xen to allow Lucio De Re
2006-12-07  6:06         ` ron minnich
2006-12-09  4:21           ` Chad Dougherty
2006-12-09 11:21             ` Steve Simon
2006-12-09 12:43               ` Lucio De Re
2006-12-09 12:56               ` erik quanstrom
2006-12-10  4:55                 ` geoff
2006-12-10  5:04                   ` andrey mirtchovski
2006-12-10 20:16               ` Charles Forsyth
2006-12-10 20:56                 ` Francisco J Ballesteros
2006-12-10 21:38                   ` Charles Forsyth
2006-12-10 20:52               ` ron 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=13426df10612062101i3f2485ffyec9409d5c6fc851c@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=lucio@proxima.alt.za \
    /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).