9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ARM and u-boot
Date: Sat,  1 Jun 2013 17:02:17 +0200	[thread overview]
Message-ID: <20130601150217.GB390@polynum.com> (raw)
In-Reply-To: <19d2abc3d484343ca1b8c4288d9d0e62@brasstown.quanstro.net>

On Sat, Jun 01, 2013 at 09:31:29AM -0400, erik quanstrom wrote:
>
> 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.
>

Well, the ARM is now ubiquitous and I don't know if there are x86
(whether 32 or 64 bits) without a FPU (now a GPU is even integrated),
so ARM is something definitively to consider along x86_* now for uses
that don't involve floating point calculus. Fileservers come first to
mind, well terminals too for still a significative number of applications
not needing high 3D rendering (leaving CPU for... computing).

Plus I have the hardware (it was not planned).

And finally, if Plan9 could be used as easily as on the Sheevaplug
on this kind of Iomega appliance, when it comes to price, with
typically two disks of 1, 2 or 4 terabytes, it is an ARM appliance
not more expensive than a sheevaplug, and more widely available...
(not the same size, and producing---to my taste---a lot of heat;
but I had rough times with Iomega software, but if one can get rid
of the software and deal with the hardware...).

--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2013-06-01 15:02 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 [this message]
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=20130601150217.GB390@polynum.com \
    --to=tlaronde@polynum.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).