From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: Request for testing remote wakeup during STD
Date: Sun, 11 Feb 2007 07:52:10 +1100 [thread overview]
Message-ID: <1171140730.30705.28.camel@nigel.suspend2.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0702101143090.12146-100000@netrider.rowland.org>
Hi.
On Sat, 2007-02-10 at 12:08 -0500, Alan Stern wrote:
> On Sat, 10 Feb 2007, Nigel Cunningham wrote:
>
> > Hi Alan.
>
> > I'd love to be able to help you. My lappy loads ehci and lsusb shows the
> > controller, but I'll be darned if I can find the socket! I have other
> > things to get done right now, but if no-one beats me to it, I'll try the
> > desktop I have - I think that has ehci somewhere.
>
> Thanks, Nigel. You mean your laptop has an EHCI controller but no USB
> ports? That's odd...
Yeah. I have three USB ports on it, but two of them seem to be connected
to one controller (going by lsusb after plugging my Palm into each of
them).
> Anyway, here are instructions for you or anyone else who can do the test.
> (I forgot to include them in the original message.) Running the test
> involves two steps.
>
> The first step is to check that an unpatched system supports Wake-on-USB.
> This means enabling it in the BIOS and/or in ACPI (whatever that might
> entail; I have no idea what's needed) and actually trying it out. Either
> plugging or unplugging a USB device while the system is in STD should wake
> the machine up.
>
> The second step is to see whether Wake-on-USB continues to work after
> applying the patch mentioned previously. That's the real question.
>
> It may turn out that _nobody_ has Wake-on-USB working at all... in which
> case we'd have a different problem to solve.
Thanks!
Nigel
next prev parent reply other threads:[~2007-02-10 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-10 3:59 Request for testing remote wakeup during STD Alan Stern
2007-02-10 4:50 ` Nigel Cunningham
2007-02-10 17:08 ` Alan Stern
2007-02-10 20:52 ` Nigel Cunningham [this message]
2007-02-11 19:44 ` Alan Stern
2007-02-11 20:28 ` Nigel Cunningham
2007-02-11 21:43 ` Rafael J. Wysocki
2007-02-13 11:35 ` Pavel Machek
2007-02-13 15:52 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1171140730.30705.28.camel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=linux-pm@lists.osdl.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox