From owner-freebsd-current@FreeBSD.ORG Sat Jan 17 12:34:25 2004 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 8612116A4CE for ; Sat, 17 Jan 2004 12:34:25 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66EAD43D53 for ; Sat, 17 Jan 2004 12:34:24 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0HKYFET038027; Sat, 17 Jan 2004 13:34:15 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 17 Jan 2004 13:34:10 -0700 (MST) Message-Id: <20040117.133410.17267747.imp@bsdimp.com> To: pete@altadena.net From: "M. Warner Losh" In-Reply-To: <20040117141129.GA28446@users.altadena.net> References: <20040117141129.GA28446@users.altadena.net> 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: current@freebsd.org Subject: Re: allow_unsupported_io_range 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: Sat, 17 Jan 2004 20:34:25 -0000 In message: <20040117141129.GA28446@users.altadena.net> Pete Carah writes: : Someone removed (or changed) "hw.pci.allow_unsupported_io_range". This breaks : LOTS of laptops, in particular the pccard hardware. Causes a hang after : init is started... That was me. Before, we handled bridges incorrectly. I did add one item to the allocation stuff. We now have a higher chance of collision of resources, which causes the problems. Warner