From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mario Premke" Subject: AW: AW: [Fwd: Re: EDE - Personal Suggestions and Ideas] Date: Wed, 26 May 2004 14:39:44 +0200 Sender: linux-8086-owner@vger.kernel.org Message-ID: References: <20040526115733.GQ12951@vega.vega.lgb.hu> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20040526115733.GQ12951@vega.vega.lgb.hu> List-Id: Content-Type: text/plain; charset="us-ascii" To: lgb@lgb.hu Cc: David Given , linux-8086@vger.kernel.org > > Ehhm, I see. Sorry I did not understand your point. > Don't excuse, there might not be much point in my writing ... ;-) > OK, now I see, but I haven't got the point. I mean, if you have a > syscall or > whatever to allocate a memory as a separate segment, you would > get a 16 bit > ID which can be load in the segment register. And this is NOTHING > for a user > space application that this is real mode segment register contant (so real > address divided by 16) or a selector in pmode, user app should only load > this number into the segment register. In this way (if we don't If a stupid real mode program can't recognize being run in pmode it could be possible to develop 286-pmode for ELKS without changing the rest of the system (user space programs) in the first place (anyway there are only 64k data + 64k text programs currently) When it comes to far pointers you must use a selector which number correspondens to the segment adress of the far pointer in the real mode program independly of the actual memory position the descriptor points to - if I get it right ... Mario