From owner-freebsd-current@FreeBSD.ORG Tue Apr 15 07:25:41 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36F7D37B401; Tue, 15 Apr 2003 07:25:41 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35EDB43FA3; Tue, 15 Apr 2003 07:25:40 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h3FEPcA7062919; Tue, 15 Apr 2003 08:25:38 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 15 Apr 2003 08:25:15 -0600 (MDT) Message-Id: <20030415.082515.38326093.imp@bsdimp.com> To: sobomax@portaone.com From: "M. Warner Losh" In-Reply-To: <20030414155915.GB23374@vega.vega.com> References: <20030414120327.GA22561@vega.vega.com> <200304141415.h3EEFhuv075007@spider.deepcore.dk> <20030414155915.GB23374@vega.vega.com> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: sos@spider.deepcore.dk cc: current@freebsd.org Subject: Re: Workaround for some broken BIOSes that forgot to enable ATAchannels [patch] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2003 14:25:41 -0000 In message: <20030414155915.GB23374@vega.vega.com> Maxim Sobolev writes: : Many other drivers don't rely on BIOS to do the right job and : enable ports, memory space and busmastering explicitly. And those drivers are wrong. : And : this is the right thing (IMO), since most modern operating : systems including FreeBSD don't give a shit to BIOS settings : anyway. If device is probed and user didn't disable the driver : explicitly, it should do everything to attach to device, no : matter in which weird state the BIOS left it. I agree, but the right place for this is in the bus layer, not the driver layer. See my other post for code that does this, as well as the work around that most people use: hw.pci.enable_io_modes=1 Warner