From owner-freebsd-usb@FreeBSD.ORG Mon May 28 06:53:30 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 862E516A47E for ; Mon, 28 May 2007 06:53:30 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id 23C3F13C45E for ; Mon, 28 May 2007 06:53:29 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [88.88.46.79] (account mc467741@c2i.net HELO [192.168.0.102]) by mailfe02.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 505682896; Mon, 28 May 2007 08:53:28 +0200 From: Hans Petter Selasky To: John-Mark Gurney Date: Mon, 28 May 2007 08:53:18 +0200 User-Agent: KMail/1.9.5 References: <200705272235.46048.hselasky@c2i.net> <20070527215329.GY4602@funkthat.com> In-Reply-To: <20070527215329.GY4602@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705280853.18551.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: 31st address line sometimes not used on EHCI/UHCI/OHCI X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2007 06:53:30 -0000 On Sunday 27 May 2007 23:53, John-Mark Gurney wrote: > Hans Petter Selasky wrote this message on Sun, May 27, 2007 at 22:35 +0200: > > I've got some reports back that some USB host controllers do not support > > transferring memory from a location higher than 2GB. > > > > What should we do about this? > > > > Should we limit all USB DMA allocations to the lower 2GB of the memory? > > No, a quirk table should be setup and pass the restriction to bus_dma > at tag initalization time when a broken controller is detected.. Yes, I can do that. But I am also thinking about a static quirk, like a sysctl you can set at boot time. I hope that this is not a wide-spread problem. And I am not surprised that hardware manufacturers are not specification compliant, which really makes me wonder if they support a true 64-bit address bus on the EHCI controller at all. I would maybe cost too much money? And therefore we should just stick with 32-bit addressing on 32-bit platforms aswell. --HPS