From: Jody <jbruchon@nc.rr.com>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: BCC, ELKS 24 Bit addressing mode
Date: Fri, 24 Mar 2006 00:17:30 -0500 [thread overview]
Message-ID: <442380EA.5050807@nc.rr.com> (raw)
In-Reply-To: <20060323210950.G88845@agora.rdrop.com>
186 CPUs have various non-CPU functionality integrated into the chip
itself, which is one reason it's popular in some embedded designs.
Dan Olson wrote:
>>> 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.
>
>
> 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
> -
> 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
>
next prev parent reply other threads:[~2006-03-24 5:17 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 [this message]
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=442380EA.5050807@nc.rr.com \
--to=jbruchon@nc.rr.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.