From owner-freebsd-hackers Wed Jan 10 23:01:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA06451 for hackers-outgoing; Wed, 10 Jan 1996 23:01:58 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA06445 for ; Wed, 10 Jan 1996 23:01:51 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id RAA12528; Thu, 11 Jan 1996 17:32:07 +1030 From: Michael Smith Message-Id: <199601110702.RAA12528@genesis.atrad.adelaide.edu.au> Subject: Re: DOS File system fixes To: rnordier@iafrica.com (Robert Nordier) Date: Thu, 11 Jan 1996 17:32:06 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org In-Reply-To: <199601102141.XAA00185@eac.iafrica.com> from "Robert Nordier" at Jan 10, 96 11:41:12 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org Precedence: bulk Robert Nordier stands accused of saying: > Looking at it now, though, there is something that needs considering. > I'm assuming the typical situation of, "It works under dos/win, so why > can't I use it under FreeBSD?" The reason it works under dos may be an > OEM device driver which fixes bugs in the firmware/adds features to the > firmware (eg. SCSI controller cards which are not VDS compliant running > under mswin). If all that is holding things together is the device driver > (being that it is cheaper to revise than the firmware), leaving out the > driver and just going after the *ROM stuff isn't going to be "totally > successful." So we may need to look at the dos device driver layer for > the device support package. Hmm. I guess I'm looking at this from the perspective of "it works under vanilla DOS", because it's fairly rare that something will be shipped that's _that_ bad, and going for the least sophisticated approach. Having said that of course there are plenty of things that don't have BIOS support at all, so you need some way of getting around that. *sigh* 8) For a disk BIOS, you'd then have (effectively) a bounce out of the penalty box to the read's real buffer, or whatever. Interrupt delivery may well be an issue; I'm not at all clear on that side of the issue. > Robert Nordier -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "Who does BSD?" "We do Chucky, we do." [[