From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <25a05bf128c91ed5659d2a83679970ef@terzarima.net>
From: Charles Forsyth <forsyth@terzarima.net>
Date: Sun, 19 Jul 2009 12:41:33 +0100
To: 9fans@9fans.net
In-Reply-To: <8ccc8ba40907190207n2bd97032ra267bff7e45f7813@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] new usb stack and implicit timeouts
Topicbox-Message-UUID: 270d06f6-ead5-11e9-9d60-3106f5b1d025

disconnecting a usb device should result (eventually)
in a suitable status on the relevant hub, and thus
shouldn't require a timeout to get an error back to the user.

devices that don't respond because they are in a bad
state can be unplugged (if removeable).

built-in devices on built-in hubs that get into a
bad state probably need a usb or system reset,
but some higher-level application (or human) timeout
can interrupt a too-long delayed request.

so far, i'd argue that a per-request timeout wasn't needed.