From owner-freebsd-usb@FreeBSD.ORG Sun Jan 16 11:24:10 2005 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07C5F16A4CE for ; Sun, 16 Jan 2005 11:24:10 +0000 (GMT) Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4E2E43D1F for ; Sun, 16 Jan 2005 11:24:09 +0000 (GMT) (envelope-from irchat@free.fr) Received: from imp6-q.free.fr (imp6-q.free.fr [212.27.42.6]) by postfix4-1.free.fr (Postfix) with ESMTP id 77392257C15; Sun, 16 Jan 2005 12:24:08 +0100 (CET) Received: by imp6-q.free.fr (Postfix, from userid 33) id 1857771BF; Sun, 16 Jan 2005 12:24:08 +0100 (MET) Received: from AAmiens-152-1-32-57.w83-192.abo.wanadoo.fr (AAmiens-152-1-32-57.w83-192.abo.wanadoo.fr [83.192.206.57]) by imp6-q.free.fr (IMP) with HTTP for ; Sun, 16 Jan 2005 12:24:07 +0100 Message-ID: <1105874647.41ea4ed7f035f@imp6-q.free.fr> Date: Sun, 16 Jan 2005 12:24:07 +0100 From: irchat@free.fr To: Ian Dowse MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.5 X-Originating-IP: 83.192.206.57 cc: freebsd-usb@freebsd.org Subject: Re: Prism54 USB Wireless Adapters X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 11:24:10 -0000 On Sunday 16 January 2005 02:46, Ian Dowse wrote: > Try removing the USBD_NO_COPY flag from all the transfer setups. I > happen to have a USB Prism54 device here, and removing that flag > appears to cause the p54u_int_rx_cb function to get called. It worked. But I had to disable EHCI support in my kernel, is that a bug in FreeBSD ? I'm running the 5.3 version, which seems to have support for interrupt pipes on EHCI controllers. Testing my driver with or without USBD_NO_COPY and the EHCI makes the interrupt callback never called. With UHCI and without USBD_NO_COPY, my code fails when the xfers using the buffers that don't support DMA are submitted. > As far as I can tell, the USBD_NO_COPY flag should only ever be > used in conjunction with the usbd_alloc_buffer() function. Normally > the USB code copies data into a DMA buffer for writes and copies > it back after reads, but if you have set up your own buffer then > it is more efficient to access the buffer directly to avoid the > copying. Done. Thanks ! Sebastien