From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 22:38:40 2004 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 0E40516A4CE for ; Mon, 27 Dec 2004 22:38:40 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E325543D55 for ; Mon, 27 Dec 2004 22:38:39 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id BCC257A403; Mon, 27 Dec 2004 14:38:39 -0800 (PST) Message-ID: <41D08EEF.50807@elischer.org> Date: Mon, 27 Dec 2004 14:38:39 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: hselasky@c2i.net References: <41CB38A7.5020700@vicor.com> <200412261747.36555.hselasky@c2i.net> <41CFB6AE.1080705@elischer.org> <200412271242.43441.hselasky@c2i.net> In-Reply-To: <200412271242.43441.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: USB vendore designations.. 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: Mon, 27 Dec 2004 22:38:40 -0000 Hans Petter Selasky wrote: >On Monday 27 December 2004 08:15, Julian Elischer wrote: > > >>Now, when you do the "doobell trick" as descibed in the spec, >>there is one little part of it.. that is the catch. >> >>The spec says: >>"Software should first deactivate all active qTDs, wait for the >>queue head to go inactive, then remove the queue head from >>the asynchronous list." >> >>Note the word "all" >> >>Ok, so since we want to remove only SOME of the qTDs from the queue >>(those corresponding to the aborting command), and we need to read >>the status word to see which has been completed by whether the >>active bit is set, and since we are in a race with the hardware >>to clear the active bit, which of the qTDs, not in the list of >>qTDs we want to remove, was completed? >> >> >> >Maybe the EHCI driver should not reuse the QH's for transfers on the same >pipe, but instead like I did, have one QH for each transfer, insterted into >the asynchronous schedule after that the last QH has been removed? > It's an interesting idea.. where did you do this? In a new driver? sorry to be stupid but qa pointer would be good? s this the driver in _usb I think I saw from you earlier? It has the good point of being "clean" It has the bad point of only allowing one transaction per interrupt cycle. > >Yours >--HPS >_______________________________________________ >freebsd-usb@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-usb >To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > >