From: cherry <lunaria21@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] loongson (spim) port
Date: Sat, 14 Sep 2013 01:09:35 -0400 [thread overview]
Message-ID: <CACzOosB5Wid+wnLZP799FduQcOwuLfHpQoWC-G=5aXCwFDX1Ng@mail.gmail.com> (raw)
In-Reply-To: <d173ec1000bff99745d38781f037c4a8@proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Thank you Lucio. I am so encouraged as it's my first work on Plan 9. I am
sending you the code off list, due to the big attachment.
On Fri, Sep 13, 2013 at 1:08 AM, <lucio@proxima.alt.za> wrote:
> > I would like to share it and I am asking for a contrib directory.
>
> I'd love to see what you've done, so maybe I can help twist Geoff's
> arm (not that I've ever known Bell Labs to be reluctant with contrib
> space on sources).
>
So, it seems I need some other way to share it, probably not 9p?
>
> I have a Yeeloong 8089 A I bought specially for this purpose, so
> please can I (a) encourage you to continue and (b) contribute in any
> way to your efforts? It does seem like you know considerably more
> than I do about this, but I'm willing to catch up, if you have the
> patience to guide me.
>
I have not looked up how Yeeloong are different to my 2E machine. There are
general bits to fix/improve, e.g. spim libs. FP could be very helpful.
Sadly, I have not been able to get any FP instruction out of 0a/c/l to
run... Devices are also great, even if they could be different for
different machines. I am still new to the 9 kernel and do not actually know
more. I am willing to talk with you and learn from you about it.
Thanks,
- cherry
[-- Attachment #2: Type: text/html, Size: 1825 bytes --]
prev parent reply other threads:[~2013-09-14 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 4:32 cherry
2013-09-13 5:08 ` lucio
2013-09-14 5:09 ` cherry [this message]
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='CACzOosB5Wid+wnLZP799FduQcOwuLfHpQoWC-G=5aXCwFDX1Ng@mail.gmail.com' \
--to=lunaria21@gmail.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).