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: Wed, 12 Jun 2002 13:08:04 -0700 (PDT)	[thread overview]
Message-ID: <20020612130029.W40423-100000@agora.rdrop.com> (raw)
In-Reply-To: <002401c211b0$76fb6b60$9460580c@who>

> Actually that may have been what I posted, but I think you've not read it
> correctly. I said that it would run on that processor, but that according to
> Alan Cox, a worker in the field of regular Linux whose opinions I value
> strongly, suggested that the onchip peripherals of the 80186 family would
> only be supported with work. Or something like that.

That could very well be, I was under the impression that the 186 was just
an 8086 but with some the other outboard chips used on the PC integrated.
I was at one point hoping to try to build my own 186 board.....but that
hasn't happened :)  It looked perty straight forward, if a large static
RAM is used, then the memory, RAM, and BIOS ROM would be a large portion
of a motherboard!  Maybe that's wishfull thinking.  Maybe someone will try
and and report back.  Anyone have a spair Tandy TRS-80 2000 laying around?

 I then suggested that
> the original poster should check the archives of the list for Alan's actual
> answer. I copied my answer to the list, because the original poster of the
> question replied only to me. I suspect he didn't realize that when you click
> reply on most Microsoft mailer programs it goes the to name on the message,
> not to the list.

That's actually because the "reply to" field isn't the list, but the
sender.  None of the other lists I'm on are that way.

 And yes, I don't doubt that normal ELKS code will run
> natively on all 8086 based hardware. The 80186 is a special case because it
> was designed for embedded applications. I think the sibo code would run on
> it, but I don't know. That's what I am suggesting. Have you yourself tried
> it? I haven't. I am basing this on my many years of experience in the field.

I don't know, I'm just basing this on what I read in a giant PDF I found
on the intel web site that includes the data sheet for the 188 and 186.
Like I say, maybe someone else out there will be able to give it a try.  I
might even donate a CPU to the cause :)

	Dan


  reply	other threads:[~2002-06-12 20:08 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
2002-06-12  1:28     ` Gregg C Levine
2002-06-12 20:08       ` Dan Olson [this message]
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=20020612130029.W40423-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