From: Andrey Romanenko <Andrey.Romanenko@infopulse.com.ua>
To: "linux-8086@vger.kernel.org" <linux-8086@vger.kernel.org>
Subject: to make ELKS less 8086-specific and easy portable
Date: Mon, 6 Feb 2012 19:46:59 +0000 [thread overview]
Message-ID: <FC79A7424F669341A72EFA787A3C767541F78DEC@exchdb1-vm-srv.infopulse.local> (raw)
Note this message came out of subj: ELKS Git repository up on SourceForge + patches applied
Hello All,
JB>Additionally, I wish to continue discussing options for making ELKS less 8086-specific, and moving to a compiler that can make ELKS more easily portable.
The last discussion about ELKS possible way of porting/evolution was going on here many years ago. As I remember, I've made short conclusion for myself out of all those quite intensive message "ping pong" and brainstorming. The conclusion was similar to: "The 8088/86/286 memory access models make programming for those processors very similar to many 8-bit chips and PDP-11. The 64kb limit is very strong and serious barrier that is not possible to overcome without serious performance penalties (e.g. FORTH or an virtual 32bit RISC CPU). The whole industry already found the way out by switching to a new hardware with 24/32/64bit address space, so most sources around the world is not possible to compile using 64kb code/data segments. If you ever run any virtual machine on 88/86/286 CPU with dir
ect memory access to few MB of RAM then you would run ucLinux instead of ELKS. So, the only possible way for the ELKS evolution is to support EXE (i.e. multi segments executable) and probably support other systems with 16bit address space limit (including those 8-bit and PDP-11)."
Thanks,
Andrey
reply other threads:[~2012-02-06 19:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=FC79A7424F669341A72EFA787A3C767541F78DEC@exchdb1-vm-srv.infopulse.local \
--to=andrey.romanenko@infopulse.com.ua \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).