From: David Given <dg@cowlark.com>
To: Linux-8086@Vger.Kernel.Org
Subject: Re: BCC, ELKS 24 Bit addressing mode
Date: Fri, 24 Mar 2006 10:39:43 +0000 [thread overview]
Message-ID: <4423CC6F.2020800@cowlark.com> (raw)
In-Reply-To: <4422801D.2000006@sentvion.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Serdar Sutay wrote:
[...]
> What am I required to do to support 24 bits addressing in bcc? Can you
> give me some insight or guide me to the correct person?
AFAIK, bcc knows nothing about segmentation --- it deals strictly with
16-bit code. Which means that nothing will need changing. If the
Turbo186 uses all the same opcodes as a normal 186, you wouldn't even
need to modify as86.
What *will* need modification is the kernel code that allocates segments
and sets up the segment registers for the user processes, and
unfortunately I don't know anything about how that works. It's entirely
feasible that all you would need to do is to change a few small chunks
of assembly.
- --
+- David Given --McQ-+
| dg@cowlark.com | "Those that repeat truisms, are also forced to
| (dg@tao-group.com) | repeat them." --- Anonymous from Slashdot
+- www.cowlark.com --+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEI8xvf9E0noFvlzgRAh01AKC8FolbR6c3tUWN/HLK5Bm01na6dQCgyxXv
wYk7yV8D8LtzEosc1zTUsKM=
=9a2+
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-03-24 10:39 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
2006-03-23 19:53 ` Jody
2006-03-23 23:00 ` Eric des Courtis
2006-03-24 10:39 ` David Given [this message]
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=4423CC6F.2020800@cowlark.com \
--to=dg@cowlark.com \
--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 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.