From owner-freebsd-hackers Sun Feb 5 12:23:48 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA02087 for hackers-outgoing; Sun, 5 Feb 1995 12:23:48 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id MAA02079 for ; Sun, 5 Feb 1995 12:23:47 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA02886; Sun, 5 Feb 95 13:17:37 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9502052017.AA02886@cs.weber.edu> Subject: Re: FIX FOR CACHE/DMA RANGE PROBLEMS (was Re: new SNAP) To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sun, 5 Feb 95 13:17:36 MST Cc: gibbs@estienne.CS.Berkeley.EDU, bugs@warlock.win.net, freebsd-hackers@FreeBSD.org In-Reply-To: <199502041750.SAA00591@yedi.iaf.nl> from "Wilko Bulte" at Feb 4, 95 06:50:54 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > The other cache problems are based on a succeptability code for the > > driver, or on global succeptability. A driver that can't tell an ISA > > card from an EISA card *must* either note that it can screw up on DMA > > How about checking for the EISA ID ? The EISA standard doesn't provide a requirement for the amount of per slot CMOS memory (I found this out when trying to write a UNIX EISA config utility, it being my opinion that requiring DOS to configure a machine is an abortion). This may be something that requires VM86() to allow us to call the EISA BIOS for it to work properly. I think it's a move in the right direction, and at least would resolve the ISA card in an EISA slot issue. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.