From: Nicolas Pitre <nico@cam.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Richard Purdie <rpurdie@rpsys.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: spitz: Real time clock?
Date: Fri, 09 Dec 2005 19:19:19 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0512091915090.26663@localhost.localdomain> (raw)
In-Reply-To: <20051209225312.GF4658@elf.ucw.cz>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1236 bytes --]
On Fri, 9 Dec 2005, Pavel Machek wrote:
> On Pá 09-12-05 22:39:06, Richard Purdie wrote:
> > On Fri, 2005-12-09 at 22:28 +0100, Pavel Machek wrote:
> > > Is there driver for real time clock for spitz? I seem to get default
> > > time each time I boot. (And thats bad because means fsck "too much time
> > > since last check, check forced).
> >
> > There is but its already included with the kernels you have. It doesn't
> > survive reboots and this is a limitation of the PXA processor. There's
> > not a lot we can do about it I'm afraid.
>
> Ouch, that's bad :-(. So PXA can't keep time properly...
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.
> 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.
> 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.
Nicolas
next prev parent reply other threads:[~2005-12-10 0:19 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 [this message]
2005-12-10 1:43 ` Richard Purdie
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=Pine.LNX.4.64.0512091915090.26663@localhost.localdomain \
--to=nico@cam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rpurdie@rpsys.net \
/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®