From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: David Brownell <david-b@pacbell.net>
Cc: linuxppc-dev@ozlabs.org, Paul Mundt <lethal@linux-sh.org>,
David Woodhouse <dwmw2@infradead.org>,
rtc-linux@googlegroups.com
Subject: Re: [RFC PATCH] rtc: add rtc_systohc for ntp use
Date: Tue, 11 Nov 2008 00:05:56 +0100 [thread overview]
Message-ID: <20081111000556.0ae8323c@i1501.lan.towertech.it> (raw)
In-Reply-To: <200811101457.29051.david-b@pacbell.net>
On Mon, 10 Nov 2008 14:57:28 -0800
David Brownell <david-b@pacbell.net> wrote:
> Yeah, we should have one of these. :)
:) great! now let's see if we can get others
to agree!
> A better default might be to update all the RTCs on the system.
>
> I'm thinking of my trusty test-case here: rtc0 is highly functional
> (including wake from RTC alarm) but not battery backed, while rtc1
> is battery backed but only tracks time. NTP really needs to update
> both of them ... rtc0 since that's what's used most of the time,
> and also rtc1 since that's what actually *stores* the time during
> power off cycles.
well, let's start with one... we all lived with one rtc until
a couple of year ago :)
> > +static int rtc_systohc(struct rtc_time *tm)
>
> I think "static" will lose, especially since ...
wooops!
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2008-11-10 23:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 15:40 [RFC PATCH] rtc: add rtc_systohc for ntp use Alessandro Zummo
2008-11-10 22:57 ` David Brownell
2008-11-10 23:05 ` Alessandro Zummo [this message]
2008-11-11 14:10 ` David Woodhouse
2008-11-11 17:17 ` Gabriel Paubert
2008-11-11 18:11 ` [rtc-linux] " Alessandro Zummo
2008-11-11 20:58 ` David Brownell
2008-11-12 8:05 ` Gabriel Paubert
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=20081111000556.0ae8323c@i1501.lan.towertech.it \
--to=alessandro.zummo@towertech.it \
--cc=david-b@pacbell.net \
--cc=dwmw2@infradead.org \
--cc=lethal@linux-sh.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rtc-linux@googlegroups.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).