Prev: RDF_CARD_TRACKING
Next: How expose multiple MBN interfaces?
From: Pavel A. on 3 Dec 2009 00:24
Hannes,

In addition to reply of Tim, maybe the Windows Logo program document
can give you more clues.

For example, see in the recent updates:

<quote>
CONNECT-0126: All USB devices and host controllers work properly upon resume
from sleep,
hibernation or restart without a forced reset of the USB host controller.
Clarified wording, added justification to design notes.
</quote>

Regards,
--pa



"Hannes" <hannes.news(a)newsgroup.nospam> wrote in message
news:A4227441-B0FD-4F44-B518-172DB6BCCA20(a)microsoft.com...
> Excuse me gentlemen, for I must be having a blond moment here.
>
> 1. Let's assume that while the PC sleeps, the embedded USB devices are
> completely powered off. Dead. Supply voltage, USB bus voltage, everything.
> 2. Someone then presses the power button to resume the PC.
> 3. All embedded USB devices are powered on.
> 4. Windows resumes
> 5. At some point, Windows, or each device stack, checks if a device is
> still
> present.
> I see 2 possible outcomes:
>> 5a. The device is present (i.e. speaks USB), and the driver remains
>> loaded.
>> 5b. The device is NOT present (i.e. does not respond to USB
>> communication) and its driver gets unloaded. Bing-bong.
>
> On Windows 7, what is the minimum time step-3-to-step-5 ?
> (i.e. for how long can a USB device boot without getting unloaded?)
>
> Please let me know if:
> - I have gotten it all completely backwards
> - we should direct this question to a different newsgroup or forum
> - we should open a support case to get this time figure
>
> Thanks a lot for your efforts this far.
>
> / Hannes.

First  |  Prev  | 
Pages: 1 2 3 4 5 6
Prev: RDF_CARD_TRACKING
Next: How expose multiple MBN interfaces?