From: David Brownell <david-b@pacbell.net>
To: ncunningham@cyclades.com
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: Re: freeze_processes questions
Date: Wed, 6 Apr 2005 15:20:42 -0700 [thread overview]
Message-ID: <200504061520.42917.david-b@pacbell.net> (raw)
In-Reply-To: <1112825000.3757.77.camel@desktop.cunningham.myip.net.au>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
On Wednesday 06 April 2005 3:03 pm, Nigel Cunningham wrote:
> Hi David.
>
> On Thu, 2005-04-07 at 07:34, David Brownell wrote:
> > On Tuesday 05 April 2005 4:10 pm, Nigel Cunningham wrote:
> > >
> > > In this way, I handle kseriod and anything else uninterruptible without
> > > any problems.
> >
> > This may be off-topic for this thread ... but does anyone
> > have system wakeup from PS/2 keyboard/mouse working?
>
> Never tried it, I'm afraid. My keyboard has 'Power', 'Sleep' and 'Wake'
> buttons, but they seem to be directly connected to /dev/null.
>
> There's a /proc/acpi entry that controls the enabling wake events. Have
> you tried fiddling with it?
That's what didn't work. (Combined with entering S1 then trying
to use the relevant buttons ... or for that matter, any buttons.)
- Dave
> Regards,
>
> Nigel
>
> > Last time I tried to use it, it didn't work. Not clear where
> > the problem was, but I suspect it was a case of ACPI support
> > not having anything to hook up to in the driver.
> >
> > Hence the (potential) relevance on this thread: the current
> > approach to suspend/resume in serio drivers needing updating,
> > which may interact with how kseriod is used.
> >
> > - Dave
> >
> >
> --
> Nigel Cunningham
> Software Engineer, Canberra, Australia
> http://www.cyclades.com
> Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028; Mob: +61 (417) 100 574
>
> Maintainer of Suspend2 Kernel Patches http://suspend2.net
>
>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-04-06 22:20 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 9:20 freeze_processes questions Rafael J. Wysocki
2005-04-05 9:27 ` Pavel Machek
2005-04-05 9:53 ` Rafael J. Wysocki
2005-04-05 18:02 ` Rafael J. Wysocki
2005-04-05 18:17 ` Alan Stern
2005-04-05 18:33 ` Rafael J. Wysocki
2005-04-05 20:37 ` Pavel Machek
2005-04-05 22:46 ` Rafael J. Wysocki
2005-04-05 22:57 ` Pavel Machek
2005-04-05 23:10 ` Nigel Cunningham
2005-04-06 6:41 ` Rafael J. Wysocki
2005-04-06 19:06 ` Alan Stern
2005-04-06 20:52 ` Rafael J. Wysocki
2005-04-06 21:03 ` Alan Stern
2005-04-06 21:26 ` David Brownell
2005-04-06 21:17 ` Pavel Machek
2005-04-06 21:35 ` Rafael J. Wysocki
2005-04-06 22:07 ` Nigel Cunningham
2005-04-06 22:41 ` Rafael J. Wysocki
2005-04-07 14:41 ` Alan Stern
2005-04-07 17:17 ` Rafael J. Wysocki
2005-04-07 14:43 ` Alan Stern
2005-04-07 17:26 ` Rafael J. Wysocki
2005-04-07 9:11 ` Pavel Machek
2005-04-07 12:29 ` Rafael J. Wysocki
2005-04-07 12:47 ` Nigel Cunningham
2005-04-07 14:36 ` Alan Stern
2005-04-07 18:03 ` Rafael J. Wysocki
2005-04-07 20:00 ` Alan Stern
2005-04-07 20:59 ` Rafael J. Wysocki
2005-04-07 22:09 ` Alan Stern
2005-04-08 6:20 ` Pavel Machek
2005-04-08 9:13 ` Rafael J. Wysocki
2005-04-07 21:03 ` Rafael J. Wysocki
2005-04-08 6:23 ` Pavel Machek
2005-04-08 11:23 ` Rafael J. Wysocki
2005-04-11 23:59 ` Pavel Machek
2005-04-27 9:30 ` Li Shaohua
2005-04-27 9:53 ` Nigel Cunningham
2005-04-28 4:48 ` Li Shaohua
2005-04-28 5:05 ` Nigel Cunningham
2005-04-28 5:21 ` Li Shaohua
2005-04-28 5:49 ` Nigel Cunningham
2005-04-28 6:01 ` Li Shaohua
2005-04-28 6:21 ` Nigel Cunningham
2005-04-28 8:15 ` Pavel Machek
2005-04-28 8:14 ` Pavel Machek
2005-04-28 15:19 ` Stefan Seyfried
2005-04-28 18:47 ` Pavel Machek
2005-04-08 7:20 ` Pavel Machek
2005-04-06 21:34 ` David Brownell
2005-04-06 22:03 ` Nigel Cunningham
2005-04-06 22:20 ` David Brownell [this message]
2005-04-07 9:09 ` Pavel Machek
2005-04-08 6:23 ` Pavel Machek
2005-04-08 7:18 ` Nigel Cunningham
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=200504061520.42917.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-pm@lists.osdl.org \
--cc=ncunningham@cyclades.com \
--cc=pavel@ucw.cz \
/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