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 14:50:59 +0000 [thread overview]
Message-ID: <2360386c46c96532cdd592ef4b0966f7@hamnavoe.com> (raw)
In-Reply-To: <998ded302d9f2b5cede4f7f0397a6da3@lilly.quanstro.net>
Getting Plan 9 to boot on the pi3 (in 32-bit mode) was almost trivial.
Plan 9 from Bell Labs
board rev: 0xa02082 firmware rev: 1456410415
cpu0: 1200MHz ARM Cortex-A53 r0p4
fp: 32 registers, simd
fp: arm arch VFPv3+ with null subarch; rev 4
eMMC external clock 250 Mhz
#u/usb/ep1.0: dwcotg: port 0X0 irq 9
992M memory: 200M kernel data, 792M user, 3762M swap
cpu1: 1200MHz ARM Cortex-A53 r0p4
cpu2: 1200MHz ARM Cortex-A53 r0p4
cpu3: 1200MHz ARM Cortex-A53 r0p4
usb/hub... usb/ether...
etherusb smsc: b827ebXXXXXX
version...time...
init: starting /bin/rc
pi3#
The "almost" is because the latest GPU firmware now initialises the
ARM cores in HYP mode. This change seems to have been made in October,
and affects the pi2 as well. Getting from HYP to SVC mode at boot time
is no longer as simple as a MOVW into CPSR, and requires three new
instructions that 5a doesn't know about ...
next prev parent reply other threads:[~2016-03-03 14:50 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 [this message]
2016-03-03 15:28 ` Charles Forsyth
2016-03-03 15:31 ` Charles Forsyth
2016-03-03 15:37 ` Richard Miller
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=2360386c46c96532cdd592ef4b0966f7@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).