From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Given Subject: Re: BCC, ELKS 24 Bit addressing mode Date: Fri, 24 Mar 2006 10:39:43 +0000 Message-ID: <4423CC6F.2020800@cowlark.com> References: <4422801D.2000006@sentvion.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4422801D.2000006@sentvion.com> Sender: linux-8086-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii" To: Linux-8086@Vger.Kernel.Org -----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-----