9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] P9P on Lemote Yeeloong
Date: Thu, 14 May 2009 20:29:48 +0200	[thread overview]
Message-ID: <f008c09aa912babb20669db65d2c5990@proxima.alt.za> (raw)
In-Reply-To: <3d5064d73b15cd2cbed06e132f419059@terzarima.net>

> since the hard part is writing drivers, just do a normal port using v[acl].
> not fussing about with all the other things that will otherwise go wrong
> will allow you more time to write those drivers.

My take is perhaps flawed, but the way I see it, the BIOS, bootstrap
loader and debugger (all rolled into PMON, supplied with source and
ready for cross compilation on a Linux/386 platform) insists on ELF,
optionally S-record format executables.  It seems easier and more
beneficial to shoehorn the Plan 9 kernel sources into GCC (Russ has
already done a lot of the ground work for that) than to convert the
Plan 9 kernel binaries into ELF.  I'm not sure about S-record, I have
a feeling a lot will be lost in the translation.

Now, I really don't mind hearing of different approaches, often these
have turned out to be better than the dead end I had picked, so I'll
keep that firmly in mind.  In this case there is a small additional
advantage to go the ELF/GCC route, namely that I will be using a
64-bit compiler for the kernel itself.

That said, I'm still fighting with the thread context switch stuff:
there was some exciting stuff Lucho directed me to, but so far I seem
to be held back by the fact that what I found applies to Gentoo rather
than Debian.  I need to dig a little deeper.

Also, the 32-bit/64-bit question comes up again.  I don't know enough
about MIPS to do more than ponder over the likelihood of getting a
64-bit compiler running by the time I have the kernel ported.  I'm
putting that on the backburner.

As for drivers, I'm hoping that most of the drivers will be compatible
with their 386 versions.  There is source for Linux and there is
documentation (I have only found it in Chinese, but that's still
better than nothing and I have not looked very far).  I'm too far from
that bridge to focus on it at this point, I can only wish that I will
get to it any time soon.

But again, I'm willing to listen.

++L




       reply	other threads:[~2009-05-14 18:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3d5064d73b15cd2cbed06e132f419059@terzarima.net>
2009-05-14 18:29 ` lucio [this message]
2009-05-14 18:38   ` Steve Simon
2009-05-14 18:53   ` Eric Van Hensbergen
2009-05-14 19:06     ` Steve Simon
2009-05-14 19:33     ` lucio
2009-05-14 23:04     ` Charles Forsyth
2009-05-13 19:57 lucio
2009-05-13 20:28 ` Bakul Shah
2009-05-14  3:17   ` lucio
2009-05-13 21:24 ` Latchesar Ionkov
2009-05-14  3:38   ` lucio
2009-05-13 22:00 ` Russ Cox
2009-05-14  3:34   ` lucio
2009-05-14 10:03     ` Charles Forsyth

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=f008c09aa912babb20669db65d2c5990@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.net \
    /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).