From owner-freebsd-current@FreeBSD.ORG Thu Dec 11 00:42:12 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 69EEE16A4CE for ; Thu, 11 Dec 2003 00:42:12 -0800 (PST) Received: from guldan.demon.nl (cust.13.38.adsl.cistron.nl [62.216.13.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7E8043D33 for ; Thu, 11 Dec 2003 00:42:10 -0800 (PST) (envelope-from robert@guldan.demon.nl) Received: from bombur.guldan.demon.nl ([192.168.1.3] helo=localhost) by guldan.demon.nl with esmtp (Exim 4.24; FreeBSD) id 1AUMOf-00088Z-F3; Thu, 11 Dec 2003 09:42:09 +0100 Date: Thu, 11 Dec 2003 09:42:12 +0100 From: Robert Blacquiere To: Andrew Marks Message-ID: <20031211084212.GA67420@bombur.guldan.demon.nl> References: <200312091706.hB9H6BLu007332@ns1.san.rr.com> <200312091512.15849.mistry.7@osu.edu> <20031211062553.GA95845@mail.san.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031211062553.GA95845@mail.san.rr.com> User-Agent: Mutt/1.4.1i X-Disclaimer: running FreeBSD X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "thorin.guldan.demon.nl", hasmessageblock similar future email. If you have any questions, see the administrator of that system for details.Markssamepci to use "other" io memory ranges? setting hw.pci.allow_unsupported_io_range=1 during boot and later on in /boot/loader.conf? [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description -------------------------------------------------- cc: current@freebsd.org Subject: Re: NEC uPD 9210 USB controller not working, Could not map memory 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: Thu, 11 Dec 2003 08:42:12 -0000 On Wed, Dec 10, 2003 at 10:25:53PM -0800, Andrew Marks wrote: > I also tried with just ohci and just ehci and the same error messages > occured. > > -Andrew Marks > Did you try to allow pci to use "other" io memory ranges? setting hw.pci.allow_unsupported_io_range=1 during boot and later on in /boot/loader.conf? Robert -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: Hey guys you left some holes out there!