From owner-freebsd-current@FreeBSD.ORG Mon Apr 14 09:39:19 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 DD31B37B407 for ; Mon, 14 Apr 2003 09:39:19 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E096343F85 for ; Mon, 14 Apr 2003 09:39:17 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.8p1/8.12.8) id h3EGdGF6003933; Mon, 14 Apr 2003 18:39:16 +0200 (CEST) (envelope-from sos) From: Soeren Schmidt Message-Id: <200304141639.h3EGdGF6003933@spider.deepcore.dk> In-Reply-To: <20030414155915.GB23374@vega.vega.com> To: Maxim Sobolev Date: Mon, 14 Apr 2003 18:39:16 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 cc: current@FreeBSD.ORG Subject: Re: Workaround for some broken BIOSes that forgot to enableATAchannels [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: Mon, 14 Apr 2003 16:39:20 -0000 It seems Maxim Sobolev wrote: > > > This is BIOS on my new vprMatrix 175B4 notebook (P4M-1.7GHz). > > > Along with ATA, it "forgets" to enable ports on network card > > > (fxp driver), I've already committed patch for it. Funny thing > > > is that the problem doesn't exists on 4.7 - both ata and fxp > > > work here OOB. This might be somehow related to ACPI, but > > > forcefully disabling it in 5-CURRENT doesn't help. > > > > I heard BIOSes, and now its just one :) > > > > I'll wait and see if there is more of this, before committing code that > > might be just a one off... > > :((( > > I am really wonder why ata driver is so strict in this area. > Many other drivers don't rely on BIOS to do the right job and > enable ports, memory space and busmastering explicitly. 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. The current way of things are implemented because: 1. Users wanted our driver to honor the BIOS setting an ATA channel on or off 2. If the BIOS doesn't enable the port, it most likely hasn't setup interrupt routing etc as well.. So as long as this is a problem on 1 machine only, the hack is best kept in your local tree. Now if this shows up on a significant amount of machines, I'll think about a way to deal with this. -Søren