9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ARM and u-boot
Date: Sat,  1 Jun 2013 09:31:29 -0400	[thread overview]
Message-ID: <19d2abc3d484343ca1b8c4288d9d0e62@brasstown.quanstro.net> (raw)
In-Reply-To: <20130601071926.GA2936@polynum.com>

> I have read on the wiki that there is a 5c, for ARM 32bits
> little-endian, but that there is no flash memory support.

i boot my openrd from flash.

> Unfortunately, it happens that in France, for small enterprises (not to
> say independant worker like me), we are not a worthy target. And the
> hardware can not be bought directly but only from VAR. (I was looking
> for example for Coraid products---I don't what put me this name in the
> head...).

i believe alissio (sp) is a reseller in france.  you can contact me off list
for more information.

> But I still want to experiment with WORM (more kenfs I think) and I have
> this ARMv5 thing at disposal.
>
> Since it has u-boot installed and that the mapping of the flash is given
> does one know if one could build a Plan9 kernel, write it (via
> u-boot) to the flash and be able to boot?
>
> Here are the dmesg from the installed Linux kernel (note: it has GbE,
> but it was accessed through a network with a 100Mb switch, hence the
> speed reported on the interface):

i have some experience with the marvell ferceron, and they are similar to
the plug computers/open rd, but most of the memory mapping will be
different.

if your want your focus to be on the file server, and not porting to arm,
it would be more efficient to use the existing 386 port.

- erik



  parent reply	other threads:[~2013-06-01 13:31 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 [this message]
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
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=19d2abc3d484343ca1b8c4288d9d0e62@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).