From: patv@monmouth.com (Pat Villani)
Subject: [TUHS] 32I: spl*() and paging up
Date: Sat, 29 Nov 2003 23:12:27 -0500 [thread overview]
Message-ID: <3FC96E2B.1030200@monmouth.com> (raw)
A quick update.
I have spl*() code as well as ia32 paging up in a small test kernel.
More testing remains to be done before integrating into 32I kernel.
Interrupt structure working well, as well as system call interface.
Still need copyin(), copyout(), fubyte(), fuibyte(), fuword(), etc., as
well as save(), resume(), etc.
Future progress will slow down a little. I have accepted an adjunct
teaching position, and will need to devote some otherwise free time to
preparing lessons. I still expect to have a preliminary running kernel
by New Years.
Pat
--
I've always found paranoia to be a perfectly defensible position. -- Pat
Conroy
next reply other threads:[~2003-11-30 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 4:12 Pat Villani [this message]
2003-12-01 18:51 ` Masoud A. Sharbiani
2003-12-02 12:53 ` Pat Villani
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=3FC96E2B.1030200@monmouth.com \
--to=patv@monmouth.com \
/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).