Date: Mon, 3 Nov 1997 19:59:18 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: David Greenman <dg@root.com> Cc: Phil Gilley <pgilley@metronet.com>, hackers@FreeBSD.ORG Subject: Re: Problem with ed driver in 2.2.5 Message-ID: <Pine.BSF.3.96.971103195806.26439F-100000@gdi.uoregon.edu> In-Reply-To: <199711010758.XAA28986@implode.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 31 Oct 1997, David Greenman wrote: > Hmmm. Not sure how to deal with this. The reason why 0WS was turned on > was to 'fix' a serious ISA shared-memory performance problem that a lot of > newer motherboards have - the 8K RAM cards are almost useless without it. > It turned out to cause problems with reading the EEPROM on the '790 based > cards, so I killed the option for those prior to the 2.2.5 release...I'm > surprised to hear that you're having troubles with a '690 based board. > It shouldn't be a problem on most systems - this might indicate that your > ISA bus speed is set too fast. I was monitoring this discussion on -hackers and wanted to submit a suggestion: How about make this a device flag? Since it seems to break people one way or the other, make it a flag so if it's breaking someone they can fix it. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971103195806.26439F-100000>