From: Jacob Gorm Hansen <jg@ioi.dk>
To: Karim Yaghmour <karim@opersys.com>
Cc: Pavel Machek <pavel@suse.cz>,
linux-kernel <linux-kernel@vger.kernel.org>,
Adeos <adeos-main@mail.freesoftware.fsf.org>,
Philippe Gerum <rpm@xenomai.org>
Subject: Re: [Adeos-main] Re: [PATCH] Adeos nanokernel for 2.5.38 1/2: no-arch code
Date: Tue, 24 Sep 2002 23:33:57 +0200 [thread overview]
Message-ID: <20020924213356.GA14291@ibook> (raw)
In-Reply-To: <3D90D388.746D0C0D@opersys.com>
On Tue, Sep 24, 2002 at 05:05:12PM -0400, Karim Yaghmour wrote:
>
> To be honest, nothing in Adeos is "new". Adeos is implemented on
> classic early '90s nanokernel research. I've listed a number of
> nanokernel papers in the paper I wrote on Adeos. A complete list
> of nanokernel papers would probably have hundreds of entries.
> Some of these nanokernels even had OS schedulers (exokernel for
> instance). All Adeos implements is a scheme for sharing the
> interrupts among the various OSes using an interrupt pipeline.
Hi,
are you planning to add spaces & portals, like in Space or Pebble?
best,
Jacob
next prev parent reply other threads:[~2002-09-24 21:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 2:58 [Adeos-main] [PATCH] Adeos nanokernel for 2.5.38 1/2: no-arch code Karim Yaghmour
2002-09-22 4:59 ` [Adeos-main] " Pavel Machek
2002-09-24 21:05 ` Karim Yaghmour
2002-09-24 21:05 ` Karim Yaghmour
2002-09-24 21:33 ` Jacob Gorm Hansen [this message]
2002-09-24 23:15 ` [Adeos-main] " Karim Yaghmour
2002-09-24 21:33 ` Jacob Gorm Hansen
2002-09-24 23:15 ` Karim Yaghmour
2002-09-24 22:06 ` Pavel Machek
2002-09-24 23:22 ` Karim Yaghmour
2002-09-25 8:17 ` Pavel Machek
2002-09-24 22:06 ` Pavel Machek
2002-09-24 23:22 ` Karim Yaghmour
2002-09-25 8:17 ` Pavel Machek
2002-09-23 3:03 ` [Adeos-main] " Arnaldo Carvalho de Melo
2002-09-23 3:09 ` Karim Yaghmour
2002-09-23 3:09 ` Karim Yaghmour
-- strict thread matches above, loose matches on Subject: below --
2002-09-23 2:58 Karim Yaghmour
2002-09-22 4:59 ` Pavel Machek
2002-09-23 3:03 ` Arnaldo Carvalho de Melo
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=20020924213356.GA14291@ibook \
--to=jg@ioi.dk \
--cc=adeos-main@mail.freesoftware.fsf.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rpm@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.