From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <701581b43c25c1d9450823536223f6ce@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 20 Mar 2009 11:15:55 -0400
To: 9fans@9fans.net
In-Reply-To: <13426df10903200723h48d692e3lb1266a112c61d8f7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] I can not remember if I sent this or not: MIPS-64 (sort
	of) notebook
Topicbox-Message-UUID: c1432d14-ead4-11e9-9d60-3106f5b1d025

> Let me say it differently. The way in which the plan 9 kernel code was
> changed to be gcc-compilable as part of the vx32 kernel might provide
> some hints as to how to change a whole plan 9 kernel. The point being,
> it is not impossible to get a gcc-compilable plan 9 kernel. We used to
> talk about this at LANL all the time: we called it the "evil project".
> (This idea predates vx32 but it was not my idea; I will let the evil
> person behind the evil project identify himself). This change would
> remove "have to port&test&validate&fix&validate&... the C compiler
> first" as a barrier to entry on new CPUs.
>
> see src/vx32 in the vx32 tree.

i'm really missing something.  what executables does this
kernel run?  how are they generated?

wouldn't it just be easier to use 32-bit compatability mode
(http://www.mips.com/products/processors/architectures/mips64/)
for bootstrapping using vc?

- erik