From owner-freebsd-hackers Tue Mar 21 10:10:53 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA29169 for hackers-outgoing; Tue, 21 Mar 1995 10:10:53 -0800 Received: from uhura (slip5.edvz.uni-linz.ac.at [140.78.5.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA29163 for ; Tue, 21 Mar 1995 10:10:39 -0800 Received: from scotty (scotty [192.168.1.1]) by uhura (8.6.8/8.6.6) with ESMTP id TAA00221; Tue, 21 Mar 1995 19:09:49 +0100 Received: (from cg@localhost) by scotty (8.6.11/8.6.9) id TAA00210; Tue, 21 Mar 1995 19:09:44 +0100 Date: Tue, 21 Mar 1995 19:09:44 +0100 (MET) From: "DI. Christian Gusenbauer" Reply-To: cg@FIMP01.fim.uni-linz.ac.at To: Bruce Evans cc: hackers@freefall.cdrom.com Subject: Re: SVNET Meeting? In-Reply-To: <199503211316.XAA15950@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Tue, 21 Mar 1995, Bruce Evans wrote: > >Oh man.... Hmmm... The firmware is < 2k. Its basically an array of > >byte values that the driver dumps to the card. The current setup > >is the best setup except that it contaminates the GENERIC kernel > >(ie, if someone decides its okay for them to use this driver, it works > >without haveing to do anything special on their part except configure > >for the controller.) If you can think of a way for the driver to > >read in an additional file during boot, then we can distribute the > >firmware separately. > > There will have to be a another stage in the boot for 2.1. This > is not hard to implement, except for the dosboot and possibly the > netboot. The dosboot and the netboot are already out of date. > The netboot lacks support for BIOS drive geometries (which is > essential for correct operation of fdisk and sysinstall) and both > lack support for BIOS memory sizes. Yes, I know that the dosboot is out of date. But there were so many changes to the boot code, that I stopped updating dosboot. Every time I started updating I received changes for the boot code (have you ever heard from a guy called "Sisyphos" ;-) Bruce, just send me mail and I start updating again! The BIOS memory support is a special problem for dosboot, because memory managers like 386max don't give me the right values. 386max for example tells me that there is *no high mem* available! > > Bruce > -- Christian. cg@fimp01.fim.uni-linz.ac.at