From: cherry <lunaria21@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Loongson port, and 64 bit MIPS
Date: Fri, 15 Aug 2014 13:34:13 -0400 [thread overview]
Message-ID: <CACzOosC5BZy=yz55GBJg=eMJ+aKyQX-4-EsNAkAS62VE1DUZuA@mail.gmail.com> (raw)
In-Reply-To: <20140815092301.0b0a85bb@zinc.9fans.fr>
On Fri, Aug 15, 2014 at 3:23 AM, David du Colombier <0intro@gmail.com> wrote:
> Awesome job! Thanks.
>
> --
> David du Colombier
>
Thanks again!
Indeed I have a question about unifying the 2E and 2F kernels.
Currently 2F is separated so that it is convenient for me to
experiment new code for 2F hardwares without worrying breaking 2E.
Eventually it might be better to unify them. I think it is possible to
share the C code, with specific hardware enabled/disabled in
configuration file. Mainly the differences are some #define'd or enum
constants in mem.h and io.h, including IRQ and some addresses. What
would be the best way to do it?
Would it be possible to upstream this port to distribution? Minux
strongly encouraged me to do so.
Thanks,
- cherry
next prev parent reply other threads:[~2014-08-15 17:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 2:07 cherry
2014-08-15 4:41 ` Skip Tavakkolian
2014-08-15 5:54 ` Fausto Saporito
2014-08-15 14:20 ` cherry
2014-08-15 7:23 ` David du Colombier
2014-08-15 17:34 ` cherry [this message]
2014-08-15 18:30 ` David du Colombier
2014-08-16 20:29 ` cherry
2014-08-16 6:54 ` lucio
2014-08-16 10:13 ` Shane Morris
2014-08-16 20:58 ` cherry
2014-08-16 22:34 ` Shane Morris
2014-08-17 5:28 ` lucio
2014-08-17 18:16 ` cherry
2014-08-16 16:03 ` lucio
2014-08-16 20:42 ` cherry
2014-08-17 5:24 ` lucio
2014-08-17 18:39 ` cherry
2014-08-17 12:37 Richard Miller
2014-08-17 14:17 ` lucio
2014-08-17 15:49 Richard Miller
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='CACzOosC5BZy=yz55GBJg=eMJ+aKyQX-4-EsNAkAS62VE1DUZuA@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).