From: Eric Van Hensbergen <ericvh@gmail.com>
To: lucio@proxima.alt.za,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] P9P on Lemote Yeeloong
Date: Thu, 14 May 2009 13:53:36 -0500 [thread overview]
Message-ID: <a4e6962a0905141153r4a0b9cc8r267aa3e3e900b25b@mail.gmail.com> (raw)
In-Reply-To: <f008c09aa912babb20669db65d2c5990@proxima.alt.za>
On Thu, May 14, 2009 at 1:29 PM, <lucio@proxima.alt.za> wrote:
>> 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.
>
There are versions of Plan 9 compilers that support both those formats
-- perhaps it won't be as hard as you expect.
BlueGene boots Plan 9 from ELF binaries for instance.
>
> 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.
>
There are 64-bit compilers available for Plan 9 as well (for specific
architectures, namely x86_64 and ppc64). So you are a bit out of
luck here on MIPS (unless Brzr has a MIPS64 compiler I've forgotten
about).
-eric
next prev parent reply other threads:[~2009-05-14 18:53 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
2009-05-14 18:38 ` Steve Simon
2009-05-14 18:53 ` Eric Van Hensbergen [this message]
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=a4e6962a0905141153r4a0b9cc8r267aa3e3e900b25b@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@9fans.net \
--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).