From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Michel Dänzer" <michel@tungstengraphics.com>
Cc: linuxppc-dev@ozlabs.org, Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH 2/3] powermac: proper time of day after resume
Date: Thu, 25 Jan 2007 19:06:16 +1100 [thread overview]
Message-ID: <1169712376.24996.87.camel@localhost.localdomain> (raw)
In-Reply-To: <1169710754.24087.36.camel@thor.sulgenrain.local>
On Thu, 2007-01-25 at 08:39 +0100, Michel Dänzer wrote:
> On Thu, 2007-01-25 at 08:44 +1100, Benjamin Herrenschmidt wrote:
> > > > The best solution may require informing the user space ntp code of
> > > > such events. This requires very likely modifications to ntp itself
> > > > (I may be wrong, I've not looked at NTP code for 5 years or so).
> > >
> > > Doesn't the kernel send signals to init on suspend/resume
> > > events, just like with power fail events? You can hook on
> > > that.
> >
> > I don't think it does... at least not on powerbooks.
>
> It could be handled by scripts invoked from pbbuttonsd or pmud on wakeup
> though, couldn't it? I thought there used to be one for that
> in /etc/apm/, but I can't find it now...
Well, I'm not sure I've fully followed how these things changed over the
last couple of years but yes, there used to be one called by pmud and
possibly pbbuttonsd too in /etc/power/pwrctl but distro I think -also-
hook that top APM stuffs among others.
Ben.
next prev parent reply other threads:[~2007-01-25 8:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 12:38 [PATCH 0/3] some preparations for suspend on G5 powermac Johannes Berg
2006-12-13 12:38 ` [PATCH 1/3] windfarm: dont die on suspend thread signal Johannes Berg
2007-01-24 6:32 ` Benjamin Herrenschmidt
2006-12-13 12:38 ` [PATCH 2/3] powermac: proper time of day after resume Johannes Berg
2007-01-24 6:34 ` Benjamin Herrenschmidt
2007-01-24 8:46 ` Johannes Berg
2007-01-24 8:51 ` Benjamin Herrenschmidt
2007-01-24 8:54 ` Gabriel Paubert
2007-01-24 9:32 ` Benjamin Herrenschmidt
2007-01-24 10:36 ` Gabriel Paubert
2007-01-24 14:23 ` Segher Boessenkool
2007-01-24 21:44 ` Benjamin Herrenschmidt
2007-01-24 22:24 ` Segher Boessenkool
2007-01-24 22:35 ` Benjamin Herrenschmidt
2007-01-24 23:21 ` Segher Boessenkool
2007-01-25 7:39 ` Michel Dänzer
2007-01-25 8:06 ` Benjamin Herrenschmidt [this message]
2007-01-25 8:10 ` Michel Dänzer
2007-01-25 11:09 ` Gabriel Paubert
2007-01-25 12:54 ` Johannes Berg
2007-01-26 14:35 ` Johannes Berg
2007-02-01 19:16 ` [PATCH] " Johannes Berg
2007-02-02 12:19 ` Johannes Berg
2007-02-03 2:41 ` Michael Ellerman
2007-02-03 17:37 ` Johannes Berg
2007-05-02 4:45 ` Paul Mackerras
2007-05-02 4:47 ` Paul Mackerras
2007-05-02 8:26 ` Johannes Berg
2007-05-02 14:25 ` [PATCH] powerpc timer sysdev: use mktime Johannes Berg
2007-05-23 15:28 ` Johannes Berg
2007-05-28 4:33 ` Paul Mackerras
2006-12-13 12:38 ` [PATCH 3/3] powerpc: fix comment in kernel/irq.c Johannes Berg
2006-12-13 13:13 ` Johannes Berg
2006-12-19 5:40 ` Paul Mackerras
2006-12-19 18:29 ` Johannes Berg
2007-01-24 6:35 ` Benjamin Herrenschmidt
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=1169712376.24996.87.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=michel@tungstengraphics.com \
/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;
as well as URLs for NNTP newsgroup(s).