From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Porting Plan 9 to the TI Beagle Board
Date: Fri, 22 Aug 2008 13:42:36 -0700 [thread overview]
Message-ID: <5fe57dd57eb2497d8edc8f6af8da5d99@9netics.com> (raw)
In-Reply-To: <4f34febc0808221310tfd4c0d0w523a01cad11a7eef@mail.gmail.com>
this is what brucee said a while back about an ARM Cortex-M3
based device:
> I found the data sheet for the
> Cortex chip if someone needs it. A bit of a challenge for an arm port
> but it's fun indeed.
the "fun" refers to this device:
http://www.stm32circle.com
> In the recent NeXT thread Eric mentioned the TI Beagle Board
> (http://beagleboard.org/). It's quite neat: $150 for a 3" x 3" PCB
> w/ a 600 MHz ARM core, HD capable video, and SD card, audio, serial,
> USB and DVI ports. The documentation seems fairly complete, although
> according the mailing list there are issues about how much of the
> video and DSP interfaces will be documented. Hardware-wise it seems
> it only needs Ethernet to make it capable of being a Plan 9 terminal,
> although in theory that can be added via USB.
>
> How much would be involved in porting Plan 9 to it? Would the current
> Plan 9 ARM compiler be up to the task?
>
> John
next prev parent reply other threads:[~2008-08-22 20:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 20:10 John Barham
2008-08-22 20:42 ` Skip Tavakkolian [this message]
2008-08-23 2:09 ` Bruce Ellis
2008-08-23 4:14 ` Pietro Gagliardi
2008-08-23 5:22 ` Bruce Ellis
2008-08-23 5:35 ` Skip Tavakkolian
2008-08-23 5:38 ` Bruce Ellis
2008-08-23 5:49 ` Bruce Ellis
2008-08-23 9:04 ` Salva Peiró
2008-08-24 3:19 ` Latchesar Ionkov
2008-08-24 3:28 ` ron minnich
2008-08-22 21:59 ` David Leimbach
2008-08-23 6:03 ` John Barham
2008-08-23 6:22 ` Bruce Ellis
2008-08-23 14:00 erik quanstrom
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=5fe57dd57eb2497d8edc8f6af8da5d99@9netics.com \
--to=9nut@9netics.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).