From owner-freebsd-usb@FreeBSD.ORG Tue Aug 6 06:58:35 2013 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 92975679 for ; Tue, 6 Aug 2013 06:58:35 +0000 (UTC) (envelope-from hps@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 4D02E2BB7 for ; Tue, 6 Aug 2013 06:58:35 +0000 (UTC) Received: from mail.lockless.no (mail.lockless.no [46.29.221.38]) by mta.bitpro.no (Postfix) with ESMTP id 460327A233; Tue, 6 Aug 2013 08:58:28 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.lockless.no (Postfix) with ESMTP id 5DE808F170C; Tue, 6 Aug 2013 08:58:35 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at lockless.no Received: from mail.lockless.no ([127.0.0.1]) by localhost (mail.lockless.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ysyFZTMHXEY; Tue, 6 Aug 2013 08:58:34 +0200 (CEST) Received: from laptop015.hselasky.homeunix.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) by mail.lockless.no (Postfix) with ESMTPSA id 2E03E8F1709; Tue, 6 Aug 2013 08:58:34 +0200 (CEST) Message-ID: <52009EEB.1040404@bitfrost.no> Date: Tue, 06 Aug 2013 08:59:55 +0200 From: Hans Petter Selasky Organization: Bitfrost A/S User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130522 Thunderbird/17.0.6 MIME-Version: 1.0 To: "aseem.jolly" Subject: Re: USB DMA memory Allocation References: <1375489015367-5833506.post@n5.nabble.com> <1375551235535-5833585.post@n5.nabble.com> <1375752286864-5834206.post@n5.nabble.com> In-Reply-To: <1375752286864-5834206.post@n5.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2013 06:58:35 -0000 On 08/06/13 03:24, aseem.jolly wrote: > I don't want to play around with 'kern.maxbcache', can we actually allow > driver to support 64 bit DMA? > In future we can use a bootarg/sysctl to enable this support if someone > comes across this issue else we will use 32 bit DMA allocations. > > I am willing to enable this support, please guide me. > Hi, You can start with the EHCI driver, if you like. Download the EHCI PDF from INTEL's site. Figure out all the 32-bit HIGH fields and put valid data in them. For all 32-bit address there is a corresponding 32-bit high field. Thank you! --HPS