From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>, Nicolas Pitre <nico@cam.org>
Subject: Re: spitz: Real time clock?
Date: Sat, 10 Dec 2005 01:43:16 +0000 [thread overview]
Message-ID: <1134178996.8092.124.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0512091915090.26663@localhost.localdomain>
On Fri, 2005-12-09 at 19:19 -0500, Nicolas Pitre wrote:
> The RTC count is lost on a hard reset. It survives sleep mode though.
>
> The fact is that PocketPC/WinCE is not meant to be "rebooted" and the
> RTC on the PXA was probably designed with that fact. The normal usage
> pattern is to go into sleep mode all the time.
Which is the aim of the Zaurus kernel although it doesn't help when
developing...
> > could we do something like storing time on system shutdown and
> > restoring it on bootup? That way at least time will be monotonic...
> > Ok, that's userland problem.
>
> I'd say so.
OpenZaurus/OE did have code to try and do this built into its images.
I'm not sure what its status is at the moment.
> > Is there way to reboot without "really" rebooting? That would help at
> > least in my usage case.
>
> You should be able to "soft" reboot which will also preserve the RTC
> count.
Based on past performance, the bootloader (in ROM) will probably
corrupt/reset the RTC but I'd like to be proved wrong.
Russell posted some rough code to linux-arm-kernel recently that allowed
you load a new kernel in a kexec sort of manner and that is probably the
best bet to preserve the RTC. This functionality would be useful on the
Zaurus in general.
Richard
prev parent reply other threads:[~2005-12-10 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 21:28 Pavel Machek
2005-12-09 22:39 ` Richard Purdie
2005-12-09 22:53 ` Pavel Machek
2005-12-10 0:19 ` Nicolas Pitre
2005-12-10 1:43 ` Richard Purdie [this message]
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=1134178996.8092.124.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.org \
--cc=pavel@suse.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
all inboxes | Powered by JetHome®