From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] new arm port: teg2
Date: Tue, 1 May 2012 19:58:44 -0400 [thread overview]
Message-ID: <C4B2EBFB-674D-4142-B42C-24AE196B068C@9srv.net> (raw)
In-Reply-To: <CAL4LZyj0ef+Na-92WanfOFe0KxkgyZpDOd9zYwyo8hJO8ohWUA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 263 bytes --]
> Great! Graphics support at this point, or is it still in the cpu server stage?
The version on sources, at least, doesn't seem to drive video. There are
pretty good notes on what works and what doesn't in that directory, in
particular words and notes/*.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 210 bytes --]
next prev parent reply other threads:[~2012-05-01 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 22:30 geoff
2012-05-01 22:48 ` John Floren
2012-05-01 23:58 ` Anthony Sorace [this message]
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=C4B2EBFB-674D-4142-B42C-24AE196B068C@9srv.net \
--to=a@9srv.net \
--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).