From owner-freebsd-usb@FreeBSD.ORG  Wed Dec 29 10:45:30 2004
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
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 3E0F716A4CE
	for <usb@freebsd.org>; Wed, 29 Dec 2004 10:45:30 +0000 (GMT)
Received: from csmisc91.cs.chalmers.se (csmisc91.cs.chalmers.se
	[129.16.225.91])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9290443D54
	for <usb@freebsd.org>; Wed, 29 Dec 2004 10:45:29 +0000 (GMT)
	(envelope-from lennart@augustsson.net)
Received: from [IPv6:::1] (localhost [IPv6:::1])iBOAeNbu000366;
	Fri, 24 Dec 2004 11:40:24 +0100 (CET)
Message-ID: <41CBF217.3000708@augustsson.net>
Date: Fri, 24 Dec 2004 11:40:23 +0100
From: Lennart Augustsson <lennart@augustsson.net>
User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.7.3) Gecko/20041004
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Julian Elischer <julian@elischer.org>
References: <41CB38A7.5020700@vicor.com> <41CB4BCB.1080708@elischer.org>
In-Reply-To: <41CB4BCB.1080708@elischer.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: usb@freebsd.org
cc: Matthew Dillon <dillon@apollo.backplane.com>
cc: Julian Elischer <julian@vicor.com>
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 <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Dec 2004 10:45:30 -0000

I think the EHCI design has some bad flaws.
It was too long since I looked at it, so I can't remember if the ones
you mention are problematic.

Merry Chrisrmas!

	-- Lennart

Julian Elischer wrote:
> 
> EHCI is almost ok.. except for where it REALLY SUCKS!
> 
> Is there anyone who really understands it?
> It seems to me that there is almost no way to remove a pipe's queue from 
> the
> async active schedule without losing information as to whether the 
> transfers
> on it were completed or not. (other than halting the entire async schedule,
> removing the queue, and then restarting the async schedule. Similarly,
> there doesn't seen to be a really safe way to remove transfer items from
> said queue (i,e. cancel/abort them), without losing statet information for
> other items on the same queue.
> 
> Anyone with any thoughts on this, speak up! :-)
> 
> 
> 
> 
>