From: Ramakrishnan Muthukrishnan <ram@rkrishnan.org>
To: 9fans@9fans.net
Subject: Re: [9fans] Porting plan9
Date: Tue, 2 Dec 2014 06:00:53 +0530 [thread overview]
Message-ID: <1417480253.1877890.197578989.45CBCBCD@webmail.messagingengine.com> (raw)
In-Reply-To: <CAGGHmKH7yDkQF08YLshbnkh9UVoi7T4S7uZ2VKbK3763zdVzXw@mail.gmail.com>
On Tue, Dec 2, 2014, at 03:24 AM, Steven Stallion wrote:
> They do. In fact, I contributed a patch a while back to add u-boot
> image support to 5l a while back. U-boot has also been patched to
> expect these binaries. You can take a look at what has been done in
> the Chromebook port (http://code.google.com/p/9chrome), but I've been
> stalled due to demands at the office.
>
> FWIW, u-boot is not a net-negative at all. For SoC's it simplifies
> boot significantly - there is zero reason to eschew the functionality
> it brings.
>
> http://plan9.bell-labs.com/sources/contrib/stallion/patch/arm-uboot/
>
> HTH,
Thanks. That is very helpful. I will look at your patches.
Ramakrishnan
> On Mon, Dec 1, 2014 at 2:43 AM, Ramakrishnan Muthukrishnan
> <ram@rkrishnan.org> wrote:
> > On Mon, Dec 1, 2014, at 11:14 AM, erik quanstrom wrote:
> >> > Surprisingly I didn't see a paper on porting Plan9 to new architectures
> >> > in the plan9 paper collection. Any help and pointers on how to get
> >> > started with the porting effort will be highly appreciated.
> >>
> >> it's all about the documentation. if you can get it, boringing up a new
> >> kernel for a new architecture can go from impossible to very doable.
> >> it's still a lot of work, and it can be hard to sit down and spend a week
> >> finding that one little bit that prevents anything from working. good
> >> luck, nonetheless. more architectures is definately moar better.
> >
> > Thanks. IMX6 documentation is freely available. There is a version of
> > u-boot. The manufacturer (Solid Run) also has made the board schematics
> > etc available.
> >
> > From the reading of booting(8), I am assuming that the ARM devices in
> > plan9 use the u-boot for booting the kernel up?
> >
>
next prev parent reply other threads:[~2014-12-02 0:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 5:14 Ramakrishnan Muthukrishnan
2014-12-01 5:44 ` erik quanstrom
2014-12-01 8:43 ` Ramakrishnan Muthukrishnan
2014-12-01 14:13 ` erik quanstrom
2014-12-01 21:54 ` Steven Stallion
2014-12-02 0:30 ` Ramakrishnan Muthukrishnan [this message]
2014-12-02 0:56 ` Kurt H Maier
2014-12-02 2:16 ` Steven Stallion
2014-12-02 2:23 ` Skip Tavakkolian
2014-12-02 4:03 ` Kurt H Maier
2014-12-02 4:05 ` erik quanstrom
2014-12-02 4:19 ` Kurt H Maier
2014-12-02 4:23 ` erik quanstrom
2014-12-02 2:42 ` Bakul Shah
2014-12-02 3:31 ` Steven Stallion
2014-12-02 2:43 ` erik quanstrom
2014-12-02 9:32 ` Richard Miller
2014-12-02 10:12 ` Jens Staal
2014-12-02 10:48 ` mischief
2014-12-02 10:54 ` mischief
2014-12-02 14:10 ` erik quanstrom
2014-12-02 15:21 ` Steven Stallion
2014-12-02 21:57 ` Enrico Weigelt, metux IT consult
2014-12-02 22:02 ` Iruatã Souza
2014-12-02 22:28 ` Enrico Weigelt, metux IT consult
2014-12-02 22:55 ` Iruatã Souza
2014-12-03 0:20 ` yoann padioleau
-- strict thread matches above, loose matches on Subject: below --
2002-01-24 1:17 [9fans] porting plan9 forsyth
2002-01-24 19:13 ` Michael Grunditz
2002-01-24 0:45 jmk
2002-01-23 23:58 Michael Grunditz
2002-01-23 23:06 anothy
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=1417480253.1877890.197578989.45CBCBCD@webmail.messagingengine.com \
--to=ram@rkrishnan.org \
--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).