From: Kirn Gill <segin2005@gmail.com>
To: Urja Rannikko <0451383440@netti.fi>
Cc: linux-8086@vger.kernel.org
Subject: Re: elksfs removed from ELKS kernel; EMS memory needed
Date: Fri, 17 Feb 2012 04:35:15 -0500 [thread overview]
Message-ID: <CAMKR1yueWWDX+FATjY6-H1-Rc3-BnF-o0wRAg4jh_+Cef34V1Q@mail.gmail.com> (raw)
In-Reply-To: <jXCVB0ylFfhQ.p6tLq6MJ@posti.saunalahti.fi>
Aha, I did not know that. Then I guess what we have here is an
vendor-neutral and EMM-neutral API doc.
Either way, it's an "high" level API doc for DOS-based EMM managers.
We're looking to actually implement an EMM, which, if they're as you
say hardware-specific, gives me the impression that a separate driver
will be required for each addon board.
There's also the issue of how bcc generates code. Notably it doesn't
support far access or far calls, making usage of EMS quite difficult,
to say the very least, although this doc gives the impression that EMS
can be mapped (by the EMM) into the 640k area, of course, that leads
to us having to use/implement a weird API for apps to use EMS under
ELKS. Which wouldn't be portable at all, to say the least.
I think looking to "newer" CPUs might actually be better off, while
maintaining compatibility with older ones. an 286 can address 16MB of
memory, of which a max of 15MB can be RAM. 386s would be nice as well
- there's plenty of them used in the embedded space.
On Fri, Feb 17, 2012 at 04:19, Urja Rannikko <0451383440@netti.fi> wrote:
> Sorry for replying like this (blame nokia 6630 mail app);
> EMM386 only works on 386s (or better) and uses protected mode and VM86 mode to virtually provide EMS for the app running inside the VM86 box. EMS systems on pre-386s were hardware specific and had a hardware specific EMM.
> Sure you can use pm+vm86 to expand elks memory but that sounds a bit weird.
>
next parent reply other threads:[~2012-02-17 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jXCVB0ylFfhQ.p6tLq6MJ@posti.saunalahti.fi>
2012-02-17 9:35 ` Kirn Gill [this message]
2012-02-17 14:35 ` elksfs removed from ELKS kernel; EMS memory needed David Given
2012-02-17 14:48 ` EMS support will probably never happen Jody Bruchon
2012-02-17 5:39 elksfs removed from ELKS kernel; EMS memory needed Jody Bruchon
2012-02-17 7:12 ` Kirn Gill
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=CAMKR1yueWWDX+FATjY6-H1-Rc3-BnF-o0wRAg4jh_+Cef34V1Q@mail.gmail.com \
--to=segin2005@gmail.com \
--cc=0451383440@netti.fi \
--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).