All of lore.kernel.org
 help / color / mirror / Atom feed
From: JBRUCHON <jbruchon@nc.rr.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Has anyone gotten ELKS to run on an I80186 based system?
Date: Sun, 27 Apr 2008 17:17:22 -0400	[thread overview]
Message-ID: <4814ED62.1020305@nc.rr.com> (raw)
In-Reply-To: <234567.12942.qm@web50511.mail.re2.yahoo.com>

I had an old D-link wireless router that used an embedded 80186, had a 
PCMCIA card slot, a PRISM I PC card, and some useful ports on the back. 
Shame that it failed; running ELKS on that would have been like gold.  A 
very lucrative device to develop ELKS on for sure, but the point is that it 
had the 80186 CPU (the 186 was/is an embedded-only CPU, never really used in 
any general-purpose computers to my knowledge).  The COM, LPT, and more than 
one Realtek RTL8019, as well as the PCMCIA interface make it quite possibly 
the most modern-peripheral-laden 16-bit Intel CPU in existence.

Jody

Ben Weiss wrote:
> Hi Gregg,
> 
> What machine even has a 186? I now it exist[s|ed], but never knew what it was used in, always guessed some embedded stuff.
> Instruction set-wise, the 186 is compatible with 8086/88 (I think it may have one or 2 more instructions), you should be good there. 
> The 8086 is the "lowest common denominator" of the x86 line, so really ELKS will ((should)) boot on any x86.
> I'm pretty sure I downloaded some datasheets for the 186 off the net a while back. 
> If the machine doesn't make use of PC or SIBO architecture, then you'll need to do some hacking, but it sounds like you know that already.
> 
> -Ben
> 
> --- On Sat, 4/26/08, Gregg Levine <gregg.drwho8@gmail.com> wrote:
> 
>> From: Gregg Levine <gregg.drwho8@gmail.com>
>> Subject: Has anyone gotten ELKS to run on an I80186 based system?
>> To: "ELKS" <linux-8086@vger.kernel.org>
>> Date: Saturday, April 26, 2008, 10:05 AM
>> Hello!
>> I am looking to make use of the basic items that are part
>> of an I80186
>> based system here. (I for Intel, even though that firm made
>> the bad
>> decision to EOL and probably discontinue that line sometime
>> ago.)
>>
>> I thought it would be appropriate to make use of ELKS for
>> it as
>> opposed to fabricating an RTOS for it from scratch. Granted
>> this is
>> asking a heck of a lot of the features found on one such
>> device, but
>> given the special nature of the I80186 and what ELKS is, it
>> does make
>> sense in a strange sort of way.
>>
>> -- 
>> Gregg C Levine gregg.drwho8@gmail.com
>> "This signature was once found posting rude
>>  messages in English in the Moscow subway."
>> --
>> 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
> 
> 
>       ____________________________________________________________________________________
> Be a better friend, newshound, and 
> know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> --
> 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:[~2008-04-27 21:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26 15:05 Has anyone gotten ELKS to run on an I80186 based system? Gregg Levine
2008-04-27 20:02 ` Ben Weiss
2008-04-27 21:17   ` JBRUCHON [this message]
2008-04-28  3:36     ` Grant Stockly
2008-04-28  4:50       ` Gregg Levine
     [not found]         ` <278883.32747.qm@web65501.mail.ac4.yahoo.com>
2008-04-30  1:41           ` Gregg Levine
2008-04-28  4:51       ` Dan Olson
2008-04-28 22:08 ` Juanjo Marin
2008-04-29  8:54   ` Brad Normand
2008-04-29 22:29     ` Chris M
2008-04-30  1:29       ` Denis Brown
2008-05-01 23:30         ` Chris M
2008-04-29 22:19 ` Chris M

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=4814ED62.1020305@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.