public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Serdar Sutay <serdar.sutay@sentvion.com>
To: Segin <segin2005@gmail.com>
Cc: Linux-8086@Vger.Kernel.Org
Subject: Re: BCC, ELKS 24 Bit addressing mode
Date: Thu, 23 Mar 2006 20:22:58 +0200	[thread overview]
Message-ID: <4422E782.1030302@sentvion.com> (raw)
In-Reply-To: <4422EF6B.20804@gmail.com>

Segin wrote:
> Serdar Sutay wrote:
>
>> Dear All,
>>
>> I am porting ELKS to a special version of 80186 to be used in 
>> embedded devices. This special version known as Turbo186 is using 24 
>> bit addressing using a special addressing scheme. So I need to modify 
>> bcc or as86 to support 24 bit addressing mode.
>>
>> This type of operation is common in embedded usage. 24 bit addressing 
>> is working like this,
>>
>> In normal 20 bit addressing when far jumps are used, two 16 bit 
>> operands are given for address calculation. First operand is left 
>> shifted 4 bits and added to second operand, then 20 bit address is 
>> calculated.
>>
>> In 24 bit addressing mode, first operand is left shifted 8 bits and 
>> added to second operand, resulting in 24 bit address.
>>
>> 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?
>>
>> Thank you for your consideration and help.
>>
>> Kindest regards,
>>
>> Serdar Sutay
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> Basically you're working with a 286 that's been lobotmized down to a 
> 186 with the addressing features in place?
>
>
yes, but I need to address 16 Mbytes of RAM so I need to use 24 bit 
addressing mode.

Can Bcc compiler handle this automatically?

  reply	other threads:[~2006-03-23 18:22 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 [this message]
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

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=4422E782.1030302@sentvion.com \
    --to=serdar.sutay@sentvion.com \
    --cc=Linux-8086@Vger.Kernel.Org \
    --cc=segin2005@gmail.com \
    /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