From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 port to Raspberry Pi 3 Model B (ARM64)?
Date: Thu, 3 Mar 2016 15:37:10 +0000 [thread overview]
Message-ID: <3f8302eb0255b15a26efc3da907bd0c2@hamnavoe.com> (raw)
In-Reply-To: <CAOw7k5g9Qfp+w1evh7s4_=Bnh_H+iMZvYBiY_HbYWqWk59J6ZQ@mail.gmail.com>
>> cpu0: 1200MHz ARM Cortex-A53 r0p4
>
> it's ARMv8-A!
When booted in 32-bit mode, it behaves like armv7a.
next prev parent reply other threads:[~2016-03-03 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 20:06 Skip Tavakkolian
2016-02-29 20:28 ` Richard Miller
2016-02-29 20:33 ` Bakul Shah
2016-02-29 21:46 ` erik quanstrom
2016-03-01 10:04 ` Mark Lee Smith
2016-03-01 11:04 ` Aram Hăvărneanu
2016-03-03 14:50 ` Richard Miller
2016-03-03 15:28 ` Charles Forsyth
2016-03-03 15:31 ` Charles Forsyth
2016-03-03 15:37 ` Richard Miller [this message]
2016-03-03 16:14 ` Charles Forsyth
2016-09-07 23:54 ` James A. Robinson
2016-03-02 6:49 ` Ramakrishnan Muthukrishnan
2016-03-02 9:10 ` Richard Miller
2016-03-02 9:22 ` Ramakrishnan Muthukrishnan
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=3f8302eb0255b15a26efc3da907bd0c2@hamnavoe.com \
--to=9fans@hamnavoe.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).