All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gregg C Levine" <obiwanthejediknight@worldnet.att.net>
To: ELKS <Linux-8086@vger.kernel.org>
Subject: Re: Ram , Flash requirements?
Date: Tue, 11 Jun 2002 21:28:31 -0400	[thread overview]
Message-ID: <002401c211b0$76fb6b60$9460580c@who> (raw)
In-Reply-To: 20020611110903.Q20181-100000@agora.rdrop.com

Hello from Gregg C Levine
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. 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. 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.
Gregg C Levine obiwanthejediknight@att.net
<This signature will be replaced, pending an approval from the Jedi Council.
>
----- Original Message -----
From: "Dan Olson" <dano@agora.rdrop.com>
To: "ELKS" <Linux-8086@vger.kernel.org>
Sent: Tuesday, June 11, 2002 2:15 PM
Subject: Re: Ram , Flash requirements?


> > 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
>
> -
> 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
>


  reply	other threads:[~2002-06-12  1:28 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 [this message]
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='002401c211b0$76fb6b60$9460580c@who' \
    --to=obiwanthejediknight@worldnet.att.net \
    --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.