Date: Mon, 03 Nov 1997 20:48:11 -0800 From: David Greenman <dg@root.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: hackers@FreeBSD.ORG Subject: Re: Problem with ed driver in 2.2.5 Message-ID: <199711040448.UAA16661@implode.root.com> In-Reply-To: Your message of "Mon, 03 Nov 1997 19:59:18 PST." <Pine.BSF.3.96.971103195806.26439F-100000@gdi.uoregon.edu>
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. Device flags that fix/cause system crashes are a bad idea. If I were to preserve the feature at all, it would best take the form of a compile time option. For now, I'm happy to go back to the way it has been in FreeBSD since the beginning - no 0WS. Thanks for the suggestion though. :-) -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711040448.UAA16661>