9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Juan Cuzmar <juan.cuzmar.s@gmail.com>
To: "9fans" <9fans@9fans.net>
Subject: Re: [9fans] ARM hardware and SATA
Date: Thu, 12 Dec 2019 12:15:36 -0000	[thread overview]
Message-ID: <mBzqb2kpgwp4WPEVeuHerh9NDK2HtcK5mcN92cIr23a1@mailpile> (raw)
In-Reply-To: <CAEoi9W4CnuD3XGg1HKOqTBKOLptLUgo+131LrNAGeAVz1NbNOQ@mail.gmail.com>

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

Wow I'm surprised that people are still working on plan9 to
develop things especially in google... If I could aso: what kind
of things you develop with plan9?

Dan Cross <crossd@gmail.com> wrote:
> We had 9legacy running on Intel NUCs at Google for our internal
> development. It worked well enough, though of course wasn't an
> ARM based machine. Getting it going was a little hacky, but not
> too bad. We were using raspberry pi's as terminals.
> 
> I haven't looked in depth, but I suspect there's relatively
> little support for SATA interfaces in Richard's BCM code.
> Targeting something like the BananaPi W2 as a small server
> would probably be doable and the delta from Richard's code
> would be smaller than an ersatz port.
> 
>         - Dan C.
> 
> 
> On Thu, Dec 12, 2019, 12:02 PM Lucio De Re
> <lucio.dere@gmail.com> wrote:
> 
> > I'd like suggestions for some hardware on which to run Plan 9, almost
> > certainly expandable SSD capacity will be a must (Venti service).
> > Price and quality will be the biggest factors, as always.
> > 
> > Ideally, storage is where the value will reside, the actual processor
> > could be expendable.
> > 
> > ARM would allow me to start with Richard Miller's release, which I
> > believe to be a very sound foundation.
> > 
> > Thanks for any and all comments.
> > 
> > Lucio.
> 
> ------------------------------------------
> 9fans: 9fans
> Permalink:
> https://9fans.topicbox.com/groups/9fans/Tfa3a09b0e78ea56b-Mb7916a939d1b3ea5c7cf7b1f
> Delivery options:
> https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2019-12-12 12:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12  6:31 Lucio De Re
2019-12-12  8:30 ` [9fans] " Dan Cross
2019-12-12  8:54   ` Bakul Shah
2019-12-12 12:15   ` Juan Cuzmar [this message]
2019-12-12 12:43     ` hiro
2019-12-12 13:02       ` Juan Cuzmar
2019-12-12 13:14         ` Matthew Singletary
2019-12-12 14:10     ` Dan Cross
2019-12-12 14:14       ` Juan Cuzmar
2019-12-12 13:20 ` David Arnold
2019-12-12 15:14   ` hiro
2019-12-12 15:24     ` hiro
2019-12-12 15:31       ` hiro
2019-12-13  7:08       ` Dan Cross
2019-12-13 10:28         ` hiro
2019-12-14  6:13 ` David Arnold

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=mBzqb2kpgwp4WPEVeuHerh9NDK2HtcK5mcN92cIr23a1@mailpile \
    --to=juan.cuzmar.s@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).