Date: Mon, 14 Jan 2008 16:38:36 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: wblock@wonkity.com Cc: usb@freebsd.org, freebsd-usb@freebsd.org Subject: Re: umass troubleshooting FAQ Message-ID: <20080114.163836.58456912.imp@bsdimp.com> In-Reply-To: <20080114162333.A26271@wonkity.com> References: <200801141747.37052.hselasky@c2i.net> <20080114.120058.74704237.imp@bsdimp.com> <20080114162333.A26271@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20080114162333.A26271@wonkity.com>
Warren Block <wblock@wonkity.com> writes:
: On Mon, 14 Jan 2008, Warner Losh wrote:
: >
: > This item is about telling people how to fix N well known problems
: > with devices that need quirks.
: >
: > Eg, if your new device sees a 'No Sync Supported' message, then do
: > XYZ.
: >
: > If you see stalls in with these messages, do ABC.
: >
: > If you see a stall with those messages, do DEF.
:
: Is there a test suite that could detect and report these situations?
Well, ideally one would code defensively if one could detect the
problems. Many of them are 'and then the device locks up solid' kind
of failure modes :-( Once you've touched the problem, you lose.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080114.163836.58456912.imp>