From: Zhang Fuxin <fxzhang@ict.ac.cn>
To: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: linux/mips on simos
Date: Thu, 13 Mar 2003 10:47:17 -0500 [thread overview]
Message-ID: <3E70A805.1030007@ict.ac.cn> (raw)
hi,
Recently i am working on stanford SIMOS and trying to make it
run linux/mips kernel.
I've managed to run debian-mips root disk on it now. Work includes
adding a serial device simulation to simos,hack around memory/io
address mapping and adapt a linux/mips kernel for simos.
Many powerful features are to be brought back. I am struggling with
SIMOS symbol handling for ELF kernels. The backdoor,data collection
etc. need check too. I would be very glad if anybody here is willing to
help.
The main purpose of my work is to provide a studying environment for people
who want to learn something about linux/mips but without corresponding
hardware at hand. There are more and more such people in China, and I
am a member of a free orgnization that want to help them.
I believe SIMOS will be helpful for linux/mips kernel developing too.
next reply other threads:[~2003-03-13 3:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 15:47 Zhang Fuxin [this message]
2003-03-13 11:27 ` linux/mips on simos TAKANO Ryousei
2003-03-14 1:23 ` Zhang Fuxin
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=3E70A805.1030007@ict.ac.cn \
--to=fxzhang@ict.ac.cn \
--cc=linux-mips@linux-mips.org \
/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