From: Andrey Romanenko <andrey.romanenko@infopulse.com.ua>
To: Jody <jbruchon@nc.rr.com>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Documentation
Date: Mon, 17 May 2004 16:35:03 +0300 [thread overview]
Message-ID: <40A8BF87.3020700@infopulse.com.ua> (raw)
In-Reply-To: <001601c43a88$f2df9a00$0101a8c0@vash>
Hi everybody,
Jody wrote:
>If anyone has any
>ideas what I can go about documenting, please email me back or look for
>"nsx" in the #elks IRC channel.
>
>
I think there is NO decent documentation about elks kernel. What I would
like to see is:
1. Kernel architecture: (supported CPU modes; memory modes for 8086 and
286 for kernel and for processes; processes scheduling and interrupt
handling; memory managment and swap support; system invocation
mechanism; processes synchronization mechanisms; other kernel issues);
2. Available and expected to be done API and libraries;
3. Porting issues (tools,guides,how-tos);
this documents will help us to involve more peoples to project, cause
many guys even won't bother to spend couple weeks exploring source code
to find out all those mentioned issues.
thanks,
Andrey
next prev parent reply other threads:[~2004-05-17 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 14:28 Documentation Jody
2004-05-17 13:35 ` Andrey Romanenko [this message]
2004-05-17 13:40 ` Documentation Miguel Bolanos
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=40A8BF87.3020700@infopulse.com.ua \
--to=andrey.romanenko@infopulse.com.ua \
--cc=jbruchon@nc.rr.com \
--cc=linux-8086@vger.kernel.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