From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <3d5064d73b15cd2cbed06e132f419059@terzarima.net> Date: Thu, 14 May 2009 13:53:36 -0500 Message-ID: From: Eric Van Hensbergen To: lucio@proxima.alt.za, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] P9P on Lemote Yeeloong Topicbox-Message-UUID: fa0672d2-ead4-11e9-9d60-3106f5b1d025 On Thu, May 14, 2009 at 1:29 PM, wrote: >> since the hard part is writing drivers, just do a normal port using v[ac= l]. >> 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. =A0In 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