From owner-cvs-all@FreeBSD.ORG Fri Feb 18 22:40:24 2005 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5084A16A4CE; Fri, 18 Feb 2005 22:40:24 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A91BA43D5D; Fri, 18 Feb 2005 22:40:23 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j1IMdG3Q049696; Fri, 18 Feb 2005 15:39:16 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 18 Feb 2005 15:39:16 -0700 (MST) Message-Id: <20050218.153916.39202890.imp@bsdimp.com> To: ticso@cicely.de, ticso@cicely12.cicely.de From: Warner Losh In-Reply-To: <20050218214654.GD14312@cicely12.cicely.de> References: <200502181735.j1IHZ3Ch032038@repoman.freebsd.org> <20050218214654.GD14312@cicely12.cicely.de> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/pci pci_pci.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 22:40:24 -0000 > Does that mean we do check ranges on pci bridges? > I can remember having troubles with alpha systems where io ranges in > PCI chips behind PCI-PCI bridges looked valid by themself, but in fact > no IO range is configured on bridges. And if there are problems with alpha, of course I'll fix them. The last commit was just a minor tweak to allow a range we'd selected as being good to make it through rather than being considered bad. Warner