Date: Thu, 4 Jan 1996 21:30:18 +0100 (MET) From: Wilko Bulte <wilko@yedi.iaf.nl> To: terry@lambert.org (Terry Lambert) Cc: gibbs@freefall.freebsd.org, phk@critter.tfs.com, jkh@time.cdrom.com, obrien@cs.ucdavis.edu, freebsd-hackers@freebsd.org Subject: Re: X for install Message-ID: <199601042030.VAA01717@yedi.iaf.nl> In-Reply-To: <199601031852.LAA15173@phaeton.artisoft.com> from "Terry Lambert" at Jan 3, 96 11:52:10 am
next in thread | previous in thread | raw e-mail | index | archive | help
> You want an INT 13 VM86() disk driver to get the controller specific > driver loaded (a medium persistance object, since you will want to > discard it once it has done this). This is also a "fallback" driver, > since it means you can use any disk DOS can use, if you have no native > protected mode driver avilable. > > > The INT 15 EISA problem is annoying, but I think you can use signature > tagging to do memory size probing (the reason you need the EISA BIOS > is that the per slot memory is not necessarily a fixed range and can > vary from box to box, though most have pretty much standardized). > > > Terry Lambert > terry@lambert.org In our (=at a former 'work') most of the EISA mainboards only survive calling the EISA INT from things like DOS. The 32 bit equivalent in the BIOS most of the times simply crashed the Unix. I lost the details but I think counting on this to work is optimistic BTW we where using this to 'autoconfig' a ATT V.3 based system. You still had to do a kernel link but it was based on the info in the EISA config NVRAM. Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands --------------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601042030.VAA01717>