From owner-freebsd-hackers Mon Nov 3 20:02:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA05637 for hackers-outgoing; Mon, 3 Nov 1997 20:02:57 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA05631 for ; Mon, 3 Nov 1997 20:02:54 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id TAA26498; Mon, 3 Nov 1997 19:59:19 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 3 Nov 1997 19:59:18 -0800 (PST) From: Doug White Reply-To: Doug White To: David Greenman cc: Phil Gilley , hackers@FreeBSD.ORG Subject: Re: Problem with ed driver in 2.2.5 In-Reply-To: <199711010758.XAA28986@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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