From: Dan Cross <crossd@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] ARM hardware and SATA
Date: Thu, 12 Dec 2019 19:40:03 +0530 [thread overview]
Message-ID: <CAEoi9W7dvHxZrAV7OiB=_LhHEyBN84yZqLXBqH96BUDFfDA58A@mail.gmail.com> (raw)
In-Reply-To: <mBzqb2kpgwp4WPEVeuHerh9NDK2HtcK5mcN92cIr23a1@mailpile>
[-- Attachment #1: Type: text/plain, Size: 2935 bytes --]
Our use of plan9 was really incidental and was in support of our work on
Akaros. It was a tool we used to support our development environment, but
not a focus of development itself nor something we did development on
directly. We did contribute a few things back to 9legacy; some bug fixes
for the i218 driver where the NIC would lock up come to mind; we found a
few bugs in the 9pi USB stack that Richard fixed. I suppose that counts as
"improving" plan9.
Work on Akaros has stopped however, at least at Google.
Those that I know who use acme at Google are not, generally, writing web
services. Rather, they are working on the Go compiler and runtime. I
suppose it's possible that someone uses acme to write web services, but the
number of people doing that kind of thing is actually pretty small, even
though a lot of people think of Google as a "web" company. I dunno; I work
on kernels.
- Dan C.
On Thu, Dec 12, 2019, 5:47 PM Juan Cuzmar <juan.cuzmar.s@gmail.com> wrote:
> 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
> ------------------------------------------
> 9fans: 9fans
> Permalink:
> https://9fans.topicbox.com/groups/9fans/Tfa3a09b0e78ea56b-M4e6f7e9ded09cec99479a158
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>
[-- Attachment #2: Type: text/html, Size: 4318 bytes --]
next prev parent reply other threads:[~2019-12-12 14:10 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
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 [this message]
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='CAEoi9W7dvHxZrAV7OiB=_LhHEyBN84yZqLXBqH96BUDFfDA58A@mail.gmail.com' \
--to=crossd@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).