Peter Stuge wrote: > On Wed, May 09, 2007 at 04:56:03PM -0400, Gregg C Levine wrote: >>> I seem to recall that the IMS boards went into a robot that was >>> sent on a space trip? >> I indeed recall the same thing. However... I can not properly >> remember where the robot was sent to, or what it was programmed to >> find, or what. > > I may have confused it with the iRobot PackBot. (v1 440bx) > > http://osdir.com/ml/linux.bios/2002-07/msg00385.html > > > //Peter >
Well, from what I can gather this is the IMS, which I think was produced for Lockheed Martin, so it may have gone into space: http://web.archive.org/web/20041020025059/www.bitworks.com/bitworks/html/projects/celeron.htm See the attached email that google dug up. It essentially states the IMS code isn't really useful, especially since he's left out the video init stuff, it's just mainly for reference. So I think it's safe to remove, as we now have the tyan and asus boards to work from. -Corey
>From [EMAIL PROTECTED] Tue Jun 24 20:27:01 2003 From: [EMAIL PROTECTED] (Richard Smith) Date: Tue Jun 24 19:27:01 2003 Subject: 440bx patches In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> This is a multi-part message in MIME format. --------------080608060305040407040705 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Here's my patches for syncing up with my tree This is a 'diff -u -N -r --exclude=CVS --exclude=ADLO' of my tree synced to cvs vs the current cvs tree. 'cvs diff -u -N' keep hanging on me. I excluded my ADLO dual head video init since it's specific to our board and hardcoded. Includes: - Config file for the bitworks IMS board. (Not really usefull to anyone execept for example. - Rework of raminit.inc for the 440bx. Current CVS is broken and will not work in the general case. New code works for every different DIMM I had here at Bitworks. - Support for the NSC PC87351 superIO - Addition of 'mouse' into new superIO struct - Various mods to piix4e to enable/disable some features and some fixes - A sprinkleing of printk_debugs that helped me figure out what code was being called where. Most everything I did I tried to wrap with some sort of Config option except in bug fix or incorrect settings cases. Some of the stuff in the PC87351 superIO is kinda specific to our motherboard and not truly generic but I imagine that anyone else using this superIO would have it setup the same way. In the timeframe between 1.x and 2.x I doubt there will be any need for additional config options. -- Richard A. Smith [EMAIL PROTECTED]
-- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
