9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Christopher Nielsen <cnielsen@pobox.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go (again) on plan9/arm
Date: Wed, 10 Apr 2013 16:53:49 -0700	[thread overview]
Message-ID: <CAH7AAvrWK70-dEesd61vm2SYOVofE88K=R7Mjp7tX_5gUaMF7w@mail.gmail.com> (raw)
In-Reply-To: <9f71f8d13bf0b8e1fba7e22626b8dbc8@proxima.alt.za>

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

I have a dreamplug I've been meaning to put Plan 9 on. I should have time
this week to get that done for testing.

--
Christopher Nielsen
"They who can give up essential liberty for temporary safety, deserve
neither liberty nor safety." --Benjamin Franklin
"The tree of liberty must be refreshed from time to time with the blood of
patriots & tyrants." --Thomas Jefferson
"The duty of a patriot is to protect his country from its government."
--Thomas Paine
On Apr 10, 2013 12:25 PM, <lucio@proxima.alt.za> wrote:

> Gorka has made good progress with his port of Go, his implementation
> on the Raspberry PI tests to completion and only a few tests are
> failing.  The outstanding failures are being investigated and will
> be corrected.
>
> On the Sheevaplug the problem is a bit more complicated.  Gorka and I
> are in perfect (if there is such a state) synchronisation regarding
> the Go sources: we are presently working with a copy of the "tip" Hg
> release onto which CL 7987044 has been applied.  The description in
> the CL goes into details regarding additional adjustments required,
> but is silent about the nature of the changes that were needed to the
> Plan 9 distribution.
>
> Given that Gorka and I are working on different ARM platforms, it is
> not surprising that on my side testing is not as successful.  On the
> one hand, there may still be issues in the Go sources, but it is also
> very difficult to synchronise the Plan 9 installations and at this
> point I don't know what differences there may be in there.
>
> We are expecting a release from Bell Labs of Plan 9 with 21-bit runes
> replacing the current 16-bit version.  This is big and difficult and
> almost certainly extremely painful, so I doubt it will be completed
> quickly (feel free to surprise me, guys!).  I noticed some changes
> being applied today, I think Geoff and Co. are approaching the problem
> circumspectly and, this is my guess, by making adjustments that can be
> kept self-contained.  I do wish them speedy success.
>
> In the meantime, I'd like some 9fans who may own a Sheevaplug,
> possibly also other ARM equipment supported by Plan 9 - 9fans with
> some interest in Go - to try to install Go on their devices.  The
> instructions are detailed in "codereview" CL 7987044, see the Go
> documentation on how to contribute for guidelines.  Briefly, the idea
> is to clone the "tip" (default) Go development tree and build it
> _after_ applying CL 7987044 as a patch.  To the best of my knowledge,
> "make.rc" will build the Go distribution and "run.rc --no-rebuild"
> will run the tests.
>
> Ideally, I'm looking for a breakthrough with a pristine Plan 9
> distribution.  This would require building the ARM (5?) development
> toolchain, then the entirety of the runtime for the ARM as well as the
> appropriate kernel(s).  I guess the interested parties already know
> this, as well as how to boot the ARM equipment with the most recent
> available ARM kernel.
>
> There are additional changes that must be applied to the Plan 9
> distribution before we approach a successful Go build (the build is
> easier, but the Go runtime needs a good few changes).  The idea would
> be, in parallel with Bell Labs proceeding on their own path, to
> identify the changes that are absolutely critical and document them so
> that we can have Go running without putting undo pressure on Bell
> Labs.
>
> I'm keen to coordinate these efforts, but Gorka, Richard Miller and
> Ron Minnich may also want to participate and/or lead; I am not
> volunteering their involvement, I merely mention those I know have the
> interest and knwoledge to take part.  There are quite a few others and
> they are welcome to introduce themselves if they want to be involved.
> I can't offer the same code review infrastructure as Go does, but I
> believe that coreboot.org has a similar system - that's outside my
> realm and each party may want to specify what rules apply to them.
>
> I hope I'm not treading on any sensitive toes this time.
>
> Lucio.
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 4702 bytes --]

      parent reply	other threads:[~2013-04-10 23:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 19:21 lucio
2013-04-10 19:53 ` erik quanstrom
2013-04-11  5:48   ` lucio
2013-04-10 20:20 ` Bakul Shah
2013-04-10 22:56   ` Skip Tavakkolian
2013-04-11  5:40   ` lucio
2013-04-10 21:31 ` Skip Tavakkolian
2013-04-10 23:53 ` Christopher Nielsen [this message]

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='CAH7AAvrWK70-dEesd61vm2SYOVofE88K=R7Mjp7tX_5gUaMF7w@mail.gmail.com' \
    --to=cnielsen@pobox.com \
    --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).