From owner-freebsd-usb@FreeBSD.ORG Sat Aug 3 00:16:57 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 1356DCE6 for ; Sat, 3 Aug 2013 00:16:57 +0000 (UTC) (envelope-from aseem.jolly@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EBA41207E for ; Sat, 3 Aug 2013 00:16:56 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1V5PWh-0004QL-C2 for freebsd-usb@freebsd.org; Fri, 02 Aug 2013 17:16:55 -0700 Date: Fri, 2 Aug 2013 17:16:55 -0700 (PDT) From: "aseem.jolly" To: freebsd-usb@freebsd.org Message-ID: <1375489015367-5833506.post@n5.nabble.com> Subject: USB DMA memory Allocation MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Sat, 03 Aug 2013 00:16:57 -0000 It seems to me that Intel ehci controller supports 64 DMA address lines (HCCPARAMS register's 0 bit is set hardwired) then why do force DMA allocation from [0 4GB] range. I tried to enable 64 bit DMA allocations by modifying call to 'usb_dma_tag_setup' in usb_controller.c and usb_transfer.c but got a device disconnect after we preallocated DMA memory for USB transfers. Would be really great if someone could guide me on this. -- View this message in context: http://freebsd.1045724.n5.nabble.com/USB-DMA-memory-Allocation-tp5833506.html Sent from the freebsd-usb mailing list archive at Nabble.com.