From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: Suspended devices and drivers Date: Sun, 11 Sep 2005 21:33:30 -0500 Message-ID: <200509112133.30359.dtor_core@ameritech.net> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4092715110352303==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: linux-pm@lists.osdl.org Cc: David Brownell List-Id: linux-pm@vger.kernel.org --===============4092715110352303== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Sunday 11 September 2005 14:16, Alan Stern wrote: > > So yes, Windows did behave inconsistently with respect to interruptions of > Vbus. But it did not behave inconsistently (to within the limits of its > knowledge) with respect to plugging and unplugging. > FWIW it is not inconsistency in windows world it seems. Quite a few docking stations only support J3 so the normal course of cation is to suspend, unpug and then, at resume, rfe-enumerate all devices to pick up the new one and remove ones that were disconnected. -- Dmitry --===============4092715110352303== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============4092715110352303==--