From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: Newbie Question Date: 17 Jul 2003 16:08:43 +0100 Sender: linux-8086-owner@vger.kernel.org Message-ID: <1058454523.9048.17.camel@dhcp22.swansea.linux.org.uk> References: <1058373491.578.32.camel@nemesis> <003a01c34c04$c8d7ec80$ebcb9ac8@master> <1058439756.8620.7.camel@dhcp22.swansea.linux.org.uk> <20030717074901.B5771@agora.rdrop.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20030717074901.B5771@agora.rdrop.com> List-Id: Content-Type: text/plain; charset="us-ascii" To: Dan Olson Cc: linux-8086@vger.kernel.org On Iau, 2003-07-17 at 15:55, Dan Olson wrote: > the 80186/88 will run ELKS as-is. I raised this question a while back and > the answer I got was that those CPUs have integrated hardware that was > externally connected on the PC, 80186EC does, 80186 is near enough an 8086 drop in replacement with some extra instructions - just nothing worth the effort so only a few people used them in PC's. > and that hardware isn't quite connected > the same on the two. I think it's definetly possible to get ELKS running > on the 186, but does it need to be conpiled for such? Actually, if > someone has a schematic for a simple 186 based homebrew, I'd like to see > it. Does ELKS support having the console on a serial terminal yet? Just replace the vt52 console driver with the serial driver and it'll be happy