From owner-freebsd-usb@FreeBSD.ORG  Fri Mar  7 15:03:15 2008
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
Delivered-To: usb@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 312F8106566C
	for <usb@freebsd.org>; Fri,  7 Mar 2008 15:03:15 +0000 (UTC)
	(envelope-from raj@semihalf.com)
Received: from semihalf.com (semihalf.com [206.130.101.55])
	by mx1.freebsd.org (Postfix) with ESMTP id EDE5A8FC19
	for <usb@freebsd.org>; Fri,  7 Mar 2008 15:03:14 +0000 (UTC)
	(envelope-from raj@semihalf.com)
Received: from mail.semihalf.com (mail.semihalf.com [83.15.139.206])
	by semihalf.com (8.13.1/8.13.1) with ESMTP id m27EPId4022199
	for <usb@freebsd.org>; Fri, 7 Mar 2008 07:25:19 -0700
Received: from localhost (unknown [127.0.0.1])
	by mail.semihalf.com (Postfix) with ESMTP id BEECC142B9
	for <usb@freebsd.org>; Fri,  7 Mar 2008 15:35:22 +0100 (CET)
Received: from mail.semihalf.com ([127.0.0.1])
	by localhost (mail.semihalf.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 20136-06 for <usb@freebsd.org>;
	Fri,  7 Mar 2008 15:35:21 +0100 (CET)
Message-ID: <47D15050.3010809@semihalf.com>
Date: Fri, 07 Mar 2008 15:25:20 +0100
From: Rafal Jaworowski <raj@semihalf.com>
MIME-Version: 1.0
To: usb@freebsd.org
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at semihalf.com
Cc: 
Subject: Workarounds in generic EHCI code
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.5
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: Fri, 07 Mar 2008 15:03:15 -0000

Greetings,

I'd like to hear comments on the proper way of handling non-standard behaviour
of a host controller when a workaround needs to be aplied at the shared code
level. In the following I followed an example of existing VIA/ATI chip workaround:

http://people.freebsd.org/~raj/patches/misc/usb-workarounds.diff

The respective flags are potentially set in platform-specific attachment
driver code, which knows if they apply etc.

Does anybody see a better way to handle such cases?

Rafal