From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Raghavan <raghavan.viswanathan@wipro.com>
Cc: Linux-8086@vger.kernel.org
Subject: Re: Porting ELKS
Date: 19 Jul 2003 21:12:46 +0100 [thread overview]
Message-ID: <1058645565.22000.19.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <044401c34d1b$5d6f3210$8c06770a@wipro.com>
On Gwe, 2003-07-18 at 11:57, Raghavan wrote:
> (1) Does ELKS take advantage of the MMU facility of the x86 Systems ?. I ask
> this because the Blackfin does not.
ELKS uses the segmentation on the 8086 CPU.
> (2) What would be a good strategy to start the porting exercise ? Any
> previous porting lessons would help.
It depends what you need the OS for and what size you want. eCOS is
probably the better embedded OS and there is mmuless support in the 2.6
development Linux kernels if you want the full thing.
next prev parent reply other threads:[~2003-07-19 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 10:57 Porting ELKS Raghavan
2003-07-19 20:12 ` Alan Cox [this message]
2003-07-20 19:42 ` Syed Faisal Akber
2003-07-21 5:09 ` Raghavan
2003-07-21 6:22 ` Riley Williams
2003-07-21 16:49 ` Syed Faisal Akber
2003-07-21 16:48 ` Syed Faisal Akber
2003-07-22 6:12 ` Raghavan
2003-07-29 1:56 ` Syed Faisal Akber
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=1058645565.22000.19.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Linux-8086@vger.kernel.org \
--cc=raghavan.viswanathan@wipro.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