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] 2014 hardware overview
Date: Sun, 29 Jun 2014 17:46:35 -0400	[thread overview]
Message-ID: <76234a1690c733adb4e8d5ec1deb2c96@ladd.quanstro.net> (raw)
In-Reply-To: <53b056d2.SeOZ0rD4J/kbDfR9%plan9@utroff.org>

> > Nick Owens wrote:
> > the obvious hardware is a thinkpad.
> Using a laptop as a server seems strange, but is effectively a
> simple solution.

the regular supermicro server boards are known to work well.
the x9 series are better tested than the x10s.  but the x10s should
work.  also the supermicro d5xx work fine.

> > Arisawa wrote:
> > look http://plan9.aichi-u.ac.jp/hardware/
> Very handfull.
> 
> > Steve Simon wrote: 
> > At home I run...
> That confirm the usual list of known working hardware.
> 
> Thanks a lot for the various answers. Reading them, I
> believe that:
> 
> 1) It's not possible to chainload plan9 when the firmware is
> uefi. But someone wrote me off list that «most uefi firmware
> also includes bios», and apparently, that is the case of the
> supermicro boards (their documentation seems to mention uefi
> boot as an option, and not as the default).

that's the case for everything i've tried, but perhaps that's not
a representive sample.

> 2) C2000 sata soc and i354 ethernet controllers are not
> known working yet.

should be working with 9atom.

> 3) There's not so much hope to see a port for another arm
> board than the raspberry pi and the trimslice soon.

that's news to me.

- erik



  reply	other threads:[~2014-06-29 21:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29  9:32 Pierre-Jean
2014-06-29 10:27 ` Nick Owens
2014-06-29 11:55 ` arisawa
2014-06-29 15:47   ` Ramakrishnan Muthukrishnan
2014-06-29 18:38     ` sl
2014-06-29 19:20       ` Jacob Todd
2014-06-29 18:11   ` Pierre-Jean
2014-06-29 21:46     ` erik quanstrom [this message]
2014-07-01  8:23       ` Pierre-Jean
2014-07-01 14:20         ` balaji
2014-07-01 14:23           ` balaji
2014-07-01 15:02           ` David du Colombier
2014-07-01 16:13             ` Balaji
2014-07-02 15:29               ` David du Colombier
2014-07-02 19:15                 ` Balaji
2014-07-03  6:13                   ` erik quanstrom
2014-07-07 16:40           ` erik quanstrom
2014-06-29 12:09 ` Steve Simon
2014-06-29 18:19 ` cinap_lenrek
2014-07-07 16:45   ` erik quanstrom

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=76234a1690c733adb4e8d5ec1deb2c96@ladd.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).