From owner-freebsd-mobile@FreeBSD.ORG Wed Apr 21 02:56:41 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDCE516A4CE for ; Wed, 21 Apr 2004 02:56:41 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D2FD43D5A for ; Wed, 21 Apr 2004 02:56: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.10/8.12.9) with ESMTP id i3L9ucgr044422; Wed, 21 Apr 2004 03:56:38 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 21 Apr 2004 03:56:41 -0600 (MDT) Message-Id: <20040421.035641.105105735.imp@bsdimp.com> To: marcov@stack.nl From: "M. Warner Losh" In-Reply-To: <20040420164920.24EE2D7@toad.stack.nl> References: <20040420164920.24EE2D7@toad.stack.nl> 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: freebsd-mobile@freebsd.org Subject: Re: unsupported io range problem X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2004 09:56:42 -0000 In message: <20040420164920.24EE2D7@toad.stack.nl> marcov@stack.nl (Marco van de Voort) writes: : Could it be related to the fact that these devises are attached to bus PCI1 ? It is related to the fact that the pci bridge really passes all addresses back upstream, rather than the addresses listed in the pci bridge registers. newer versions handle this correctly, completely eliminating the allow_unsupported_io_ranage option. You should try a number higher than 0x20000000 since that's kind of low... Warner