Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!uunet!mcsun!sun4nl!philapd!apdnews!spoetnix.idca.tds.philips.nl!wilko From: wilko@idca.tds.philips.nl (Wilko Bulte) Newsgroups: comp.os.386bsd.development Subject: Re: EISA CONFIG (was: AHA1742) Message-ID: <wilko.742661051@spoetnix.idca.tds.philips.nl> Date: 14 Jul 93 14:44:11 GMT References: <21gt98$kuk@obelix.uni-muenster.de> <1993Jul13.172743.15441@fcom.cc.utah.edu> Sender: news@idca.tds.philips.nl Lines: 33 terry@cs.weber.edu (A Wizard of Earth C) writes: >In article <21gt98$kuk@obelix.uni-muenster.de> stefanb@cygnus.uni-muenster.de (Stefan Bohm) writes: >> >>I bought an AHA1742, but unfortunately can't get any documentation. >>May someone send me the two files !ADP0000.CFG and ADP0000.OVL via e-mail? >>I would also be nice to know something about the 7 jumpers on the 1742 board. >In this same vein, isn't it about time that we got some EISA configuration >code ported to something other than DOS? >I don't think the data files would be required to change at all, and we >could use the PCFS to get them off their distribution floppies on demand >like the DOS-based EISA configurators. >Anyone else think this is a good idea? There is one snag: the config info is written into the EISA config CMOS memory by the system BIOS. Although the EISA spec defines 32bit BIOS calls to do this in 32bit mode, they generally DON'T work. Most machines we've tested here (Digital that is) simply implement the BIOS calls incorrectly. And there were definitely brand-name machines involved that don't work. My opinion: don't bother, there are better (and less frustrating) things to be done. Wilko -- | / o / / _ Wilko Bulte mail: wilko@idca.tds.philips.nl |/|/ / / /( (_) |d|i|g|i|t|a|l| Equipment Corporation voice: +3155-432062 fax: +3155-432103 DTN: 829 2062 PO Box 245 - 7300 AE Apeldoorn - The Netherlands