From: geoff@plan9.bell-labs.com
To: 9fans@9fans.net
Subject: [9fans] new arm port: teg2
Date: Tue, 1 May 2012 18:30:24 -0400 [thread overview]
Message-ID: <955e22468668dee5e11c6c1b79ed897f@plan9.bell-labs.com> (raw)
After you pull, you should see a new directory,
/sys/src/9/teg2. From the _announce file:
This is a preliminary Plan 9 port to the Compulab Trimslice,
containing a Tegra 2 SoC: a dual-core, (truly) dual-issue 1GHz
Cortex-A9 v7a-architecture ARM system, *and* it comes in a case. VFP
3 floating-point hardware is present, but 5l doesn't yet generate
those instructions. This is the first multiprocessor ARM port we've
done, and much of the code should be reusable in future ports. There
are still things to be done but it can run both processors and is
believed to have adequate kernel support for VFP 3 floating-point.
next reply other threads:[~2012-05-01 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 22:30 geoff [this message]
2012-05-01 22:48 ` John Floren
2012-05-01 23:58 ` Anthony Sorace
2012-05-02 0:55 ` David Leimbach
2012-05-02 0:58 ` Charles Forsyth
2012-05-06 12:38 ` erik quanstrom
2012-05-06 12:45 ` hiro
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=955e22468668dee5e11c6c1b79ed897f@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.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).