9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: Again: (self)hosted Plan9? Was: [9fans] extending xen to allow
Date: Sat,  9 Dec 2006 14:43:25 +0200	[thread overview]
Message-ID: <20bac480ae6e0f8c9374a0da0cc76417@proxima.alt.za> (raw)
In-Reply-To: <e1e1d3e3266ab5e656eabdae89aa3030@quintile.net>

[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]

I seem to have long range objectives: I believe that Plan 9 could
make a better virtualisation host than the current choice for the job
and that we ought to sell to the world that it is worth (a) adopting
the Plan 9 paradigm for hosted device drivers and (b) developing all
future physical device drivers to this paradigm.

Putting it in a different way, consider replacing GRUB with 9LOAD as
first step.  Then extend 9LOAD so that it somehow contains the correct
device drivers for the particular platform and use it to boot the next
stage which accesses device drivers Plan 9-style.  Now, if we can get
the hordes of device driver implementors to focus on this approach,
Plan 9's greatest shortcoming (and all other Open Source OSes's)
suddenly disappears.

Sure, there are efficiency considerations to take into account, as
well as the unlikelihood of persuading Lunix developers to switch
allegiances, but a concerted effort to head that way is certainly not
doomed before even starting, at least not unless I'm subconsciously
ignoring some obvious obstacle.

This idea has been bugging me ever since rminnich started making
noises about Xen and I was tempted to look at it.  It bothers me that
Xen is designed very much with Linux as its model, not just its
primary target.  My claim is that a design founded on a Plan 9
foundation would be almost guaranteed to be more successful.  That's
what I call "faith", I suppose.

++L

[-- Attachment #2: Type: message/rfc822, Size: 3621 bytes --]

From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: Again: (self)hosted Plan9? Was: [9fans] extending xen to allow
Date: Sat, 9 Dec 2006 11:21:55 +0000
Message-ID: <e1e1d3e3266ab5e656eabdae89aa3030@quintile.net>

I am keen enough to try and get some hardware documentation, and maybe
even have a go at codeing a/some drivers for plan9.

I only use hardware which plan9 is compatible with so I don't know
which way to look. At IWP9 modern, inexpensive SATA cards where
mentioned as somwhere we had a gap in our coverage.

Is this all we need? Can anyone suggest a card that fits the bill?

how about modern laptops, we have a ⅞ finished centrino driver which
needs to be finished off, but what graphics chipset is common enough
to make it worthwhile chasing the manufacturer, is nvidia still king?
Do they have weird interrupt controllers, southbridges etc which will
cause problems?

As usual I promise nothing but I will do what I can.

-Steve

  reply	other threads:[~2006-12-09 12:43 UTC|newest]

Thread overview: 47+ 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
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 [this message]
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
2006-12-10 13:00 erik quanstrom
2006-12-10 20:19 erik quanstrom
2006-12-10 23:52 erik quanstrom
2006-12-12  0:22 ` Dave Eckhardt
2006-12-12  2:29   ` Russ Cox
2006-12-12  5:01     ` Lucio De Re
2006-12-12 14:21       ` Brantley Coile
2006-12-12  9:22     ` Charles Forsyth
2006-12-12  9:41       ` Bruce Ellis
2006-12-12 14:31         ` Brantley Coile
2006-12-12 14:55         ` ron minnich
2006-12-12 15:18           ` Eric Van Hensbergen
2006-12-12 15:25             ` erik quanstrom
2006-12-12 22:01             ` ron minnich
2006-12-12 22:19               ` Latchesar Ionkov
2006-12-12 23:13                 ` ron minnich
2006-12-12 23:47                   ` Bakul Shah
2006-12-12 23:37                 ` Charles Forsyth
2006-12-13 18:27                   ` ron minnich
2006-12-13 19:02                     ` Matt
2006-12-13 19:13                       ` Latchesar Ionkov
2006-12-12  9:41       ` Gabriel Diaz
2006-12-12  9:51         ` Bruce Ellis
2006-12-12 10:28           ` Lucio De Re
2006-12-12 10:30             ` Bruce Ellis
2006-12-12 23:26               ` Scott Schwartz
2006-12-12 14:42             ` Brantley Coile
2006-12-12 14:51               ` Gabriel Diaz
2006-12-12 11:49           ` Charles Forsyth
2006-12-12 14:17     ` Brantley Coile

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=20bac480ae6e0f8c9374a0da0cc76417@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).