public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Olson <dano@agora.rdrop.com>
To: ELKS <Linux-8086@vger.kernel.org>
Subject: Re: Ram , Flash requirements?
Date: Tue, 11 Jun 2002 11:15:30 -0700 (PDT)	[thread overview]
Message-ID: <20020611110903.Q20181-100000@agora.rdrop.com> (raw)
In-Reply-To: <000e01c21172$dc876580$5abd580c@who>

> Hello from Gregg C Levine normally with Jedi Knight Computers
> I do not know. I simply asked whose design this unit was. It happens that I
> asked that question early on, and Alan Cox sent me one that says that ELKS
> would need work to run on the 80186 family. I suggest you search the
> archives of this list to find his answer. I am interested in doing this as
> well.

Are you suggesting that ELKS wouldn't run on the 186 family for some
reason?  As a test, a V30 is code compatible with the 186, as the V20 is
with the 188.  As I understand it, the only thing that's special about the
186 is that it has some hardware integrated that the 8086 and other
CPUs would have outboard.

Does this board have the 512 flash memory mapped, or is it accessed though
an I/O port or by some other means?  If you have it memory mapped, then
you'd probably have enough of the memory address range used that you'd be
lacking a BIOS area.  Don't get me wrong, ELKS doesn't need to have PC
compatible hardware to run, but it would take a lot of hacking to modify
it as it seems like it relies on BIOS calls for most of it's I/O
currently.

	Dan


  reply	other threads:[~2002-06-11 18:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020611125006.57604.qmail@web13506.mail.yahoo.com>
2002-06-11 18:07 ` Ram , Flash requirements? Gregg C Levine
2002-06-11 18:15   ` Dan Olson [this message]
2002-06-12  1:28     ` Gregg C Levine
2002-06-12 20:08       ` Dan Olson
2002-06-13  5:57         ` Alan Cox
2002-06-12  3:05     ` Blaz Antonic
2002-06-11 19:45       ` Dan Olson
2002-06-12  5:43       ` Vidhiyadharan
2002-06-12  6:51     ` Alan Cox
2002-06-12 20:25       ` Dan Olson
2002-06-13  5:56         ` Alan Cox
2002-07-04 22:13           ` Bdale Garbee
2002-06-11  5:43 Vidhiyadharan
2002-06-11  9:32 ` Gregg C Levine

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=20020611110903.Q20181-100000@agora.rdrop.com \
    --to=dano@agora.rdrop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox