Date: Sun, 5 Feb 95 13:17:36 MST From: terry@cs.weber.edu (Terry Lambert) To: wilko@yedi.iaf.nl (Wilko Bulte) Cc: gibbs@estienne.CS.Berkeley.EDU, bugs@warlock.win.net, freebsd-hackers@FreeBSD.org Subject: Re: FIX FOR CACHE/DMA RANGE PROBLEMS (was Re: new SNAP) Message-ID: <9502052017.AA02886@cs.weber.edu> In-Reply-To: <199502041750.SAA00591@yedi.iaf.nl> from "Wilko Bulte" at Feb 4, 95 06:50:54 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9502052017.AA02886>