From owner-freebsd-hackers Sun Feb 5 18:32:25 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA02723 for hackers-outgoing; Sun, 5 Feb 1995 18:32:25 -0800 Received: from ns.gte.com (ns.gte.com [132.197.8.9]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id SAA02698 for ; Sun, 5 Feb 1995 18:32:23 -0800 Received: from bunny.gte.com by ns.gte.com (5.65c/IDA-1.4.4) id AA24555; Sun, 5 Feb 1995 20:04:39 -0500 Received: by bunny.gte.com (8.6.9/GTEL2.19) id UAA14882; Sun, 5 Feb 1995 20:02:01 -0500 Received: from localhost by genesis.nred.ma.us (8.3/genesis0.0) id RAA14930; Sun, 5 Feb 1995 17:41:17 -0800 Date: Sun, 5 Feb 1995 17:41:17 -0800 From: steve2@genesis.nred.ma.us (Steve Gerakines) Message-Id: <199502060141.RAA14930@genesis.nred.ma.us> To: freebsd-hackers@FreeBSD.org Subject: Re: FIX FOR CACHE/DMA RANGE PROBLEMS Sender: hackers-owner@FreeBSD.org Precedence: bulk > Yes. The Ultrastor is a problem; I was trying to be a bit more generic. > The start of this thread was condemning generic problems with DMA, of > which the Ultrastor identification problem is only one (small) example. What exactly is the problem with the Ultrastor probe?? Please be specific. I wrote the 24F (EISA) probe virtually line by line from the spec. The only problem I know of which is now fixed, is that there was a faulty test to see if a 24F card was in wd emulation mode. >From what I can follow in this thread you're talking about two different things here. The driver will certainly detect a 24F and use the proper card settings. It does not (and as far as I know no driver does) check test to see if the EISA chipset is buggy. I'm not sure what changed in 2.x but it would be nice to have config support for all the different bus types rather than hardcoding all the different methods in each driver. Better yet, it would be nice to just nuke config entirely. - Steve steve2@genesis.nred.ma.us