9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steven Stallion <sstallion@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ARM and u-boot
Date: Mon,  3 Jun 2013 11:21:20 -0700	[thread overview]
Message-ID: <CAGGHmKHh=ZAKZh9yXLwcw0BRHZO6rUrdRqq3z8NubmAy180LfA@mail.gmail.com> (raw)
In-Reply-To: <2ef52570c9c6f8a5f541e1ab9465159e@brasstown.quanstro.net>

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

On Mon, Jun 3, 2013 at 6:19 AM, erik quanstrom <quanstro@quanstro.net>wrote:

> unfortunately, as far as i know plan 9 can't be used as a primary
> loader most of the environments where uboot is used because
> we haven't written the (usually small) memory initialization code, etc.
>

It's more than that. Many board vendors will use a secured stage 1
bootloader that assumes U-Boot. It's probably possible to shove in a
different second stage loader, but you'll still need to do board
initialization as you mentioned. It's not that onerous and there is source
out there, but I think it's really a question of motivation. U-Boot is
supported by the same vendors and covers of the behavior you will likely
want in a boot loader (and then some). Board configs are easy to customize
so that you aren't carrying around a massive binary. The binary I use for
the Arndale is measured in kilobytes, not megabytes.

Every SoC is going to have a different process - in the end, you'll have
something that will probably look quite a bit like U-Boot without any real
benefit. I'd rather tilt at other windmills...

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

  reply	other threads:[~2013-06-03 18:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01  7:19 tlaronde
2013-06-01  8:04 ` lucio
2013-06-01  9:30   ` tlaronde
2013-06-01 13:31 ` erik quanstrom
2013-06-01 15:02   ` tlaronde
2013-06-01 19:29   ` tlaronde
2013-06-01 22:10     ` erik quanstrom
2013-06-02  6:14       ` tlaronde
2013-06-02  4:06 ` Steven Stallion
2013-06-02  6:02   ` tlaronde
2013-06-02 13:09   ` erik quanstrom
2013-06-02 15:50     ` Richard Miller
2013-06-03  3:53       ` erik quanstrom
2013-06-03  4:29         ` Skip Tavakkolian
2013-06-03 10:35           ` Richard Miller
2013-06-03 12:34             ` Skip Tavakkolian
2013-06-03 16:58             ` Bakul Shah
2013-06-03 18:21               ` Richard Miller
2013-06-03 18:35                 ` Bakul Shah
2013-06-03 18:40                   ` Richard Miller
2013-06-03 10:41         ` Richard Miller
2013-06-03 13:19           ` erik quanstrom
2013-06-03 18:21             ` Steven Stallion [this message]
2013-06-03 18:43               ` erik quanstrom
2013-06-03 20:02                 ` Steven Stallion
2013-06-03 20:13                   ` erik quanstrom
2013-06-03 20:19                     ` erik quanstrom
2013-06-03  5:40     ` Steven Stallion

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='CAGGHmKHh=ZAKZh9yXLwcw0BRHZO6rUrdRqq3z8NubmAy180LfA@mail.gmail.com' \
    --to=sstallion@gmail.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).