From owner-freebsd-current@FreeBSD.ORG  Sun Feb 26 03:10:45 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8A61516A420
	for <freebsd-current@freebsd.org>; Sun, 26 Feb 2006 03:10:45 +0000 (GMT)
	(envelope-from iedowse@iedowse.com)
Received: from nowhere.iedowse.com (nowhere.iedowse.com [82.195.144.75])
	by mx1.FreeBSD.org (Postfix) with SMTP id CA39D43D45
	for <freebsd-current@freebsd.org>; Sun, 26 Feb 2006 03:10:44 +0000 (GMT)
	(envelope-from iedowse@iedowse.com)
Received: from localhost  ([127.0.0.1] helo=iedowse.com)
	by nowhere.iedowse.com via local-iedowse id <aa36064@nowhere>;
	26 Feb 2006 03:10:40 +0000 (GMT)
To: Fredrik Lindberg <fli+freebsd-current@shapeshifter.se>
In-Reply-To: Your message of "Sun, 19 Feb 2006 15:00:12 GMT."
	<200602191500.aa87886@nowhere.iedowse.com> 
Date: Sun, 26 Feb 2006 03:10:36 +0000
From: Ian Dowse <iedowse@iedowse.com>
Message-ID: <200602260310.aa36064@nowhere.iedowse.com>
Cc: freebsd-current@freebsd.org
Subject: Re: USB and clear endpoint stall 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2006 03:10:45 -0000

In message <200602191500.aa87886@nowhere.iedowse.com>, Ian Dowse writes:
>In message <43F87155.3050103@shapeshifter.se>, Fredrik Lindberg writes:
>>I've attached a patch that works for me, it's basicly the same
>>as before Jan 8, but with the quirk reversed.
>>My USB-foo isn't that good so people with better understanding
>>of the USB stack might have a better fix for this.
>
>Committed, thanks! I wasn't sure if such devices would exist, but
>that's exactly the right way to handle them.

There was another issue found with removal of the stall-clearing
code, which was that data toggle values were not preserved if a
pipe was closed and then reopened. I wonder could you try updating
to the latest -current USB code but remove your quirk to see if it
is still necessary?

Thanks,

Ian