From: Andrey Romanenko <andrey.romanenko@infopulse.com.ua>
To: Linux-8086@vger.kernel.org
Subject: Re: BCC, ELKS 24 Bit addressing mode
Date: Fri, 24 Mar 2006 11:44:40 +0200 [thread overview]
Message-ID: <4423BF88.7090802@infopulse.com.ua> (raw)
In-Reply-To: <20060323210950.G88845@agora.rdrop.com>
Dan Olson wrote:
> I hate to ask, but why bother with a 186 in the first place? As I
> understand it, the only real difference (other than some hardware
> integration) between the two is that the 286 has a 24 bit address
> space....which you'd need if you're going to use 16M of RAM anyway.
>
> Dan
That was something I was thinking about after that post. I wonder what
the benefits to have addressing mode even more constrained than found in
286 and still bother with those crappy 64kb segments? Is that hardware
really cheap or wide spread around?
Anyway, it looks like you may add this addressing mode handling to EXE
image loader that would change all cross-segment access addresses to be
compatible with this addressing mode. You may want to try it under plain
DOS. Btw, seems this way you still keep all EXE compatible with 8088.
Andrey
next prev parent reply other threads:[~2006-03-24 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 11:01 BCC, ELKS 24 Bit addressing mode Serdar Sutay
2006-03-23 18:56 ` Segin
2006-03-23 18:22 ` Serdar Sutay
2006-03-24 5:11 ` Dan Olson
2006-03-24 5:17 ` Jody
2006-03-24 5:28 ` Dan Olson
2006-03-25 22:11 ` Gregg C Levine
2006-03-24 9:44 ` Andrey Romanenko [this message]
2006-03-23 19:53 ` Jody
2006-03-23 23:00 ` Eric des Courtis
2006-03-24 10:39 ` David Given
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=4423BF88.7090802@infopulse.com.ua \
--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