From: Robert Reif <reif@earthlink.net>
To: sparclinux@vger.kernel.org
Subject: Re: [PATHC 0/2] sparc32: convert to RTC subsystem
Date: Thu, 04 Sep 2008 01:42:54 +0000 [thread overview]
Message-ID: <48BF3D1E.503@earthlink.net> (raw)
In-Reply-To: <20080903183232.b57f5a05.krzysztof.h1@wp.pl>
Krzysztof Helt wrote:
> Robert, please test it on as many machine as you can.
>
>
With latest sparc-next, my ss20 boots now but the clock is suspect.
Time is initially set to Dec 31, 1969 but ntp fixes it.
I'm using debian etch so I'm not sure it's setup for generic rtc.
I had to make a link for /dev/rtc to get things somewhat working.
This could be a bad NVRAM but openboot doesn't complain.
ss20-1:/dev# ln -s rtc0 rtc
ss20-1:/dev# /sbin/hwclock --debug
hwclock from util-linux-2.12r
Using /dev/rtc interface to clock.
Last drift adjustment done at 1220490623 seconds after 1969
Last calibration done at 1220490623 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time
from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2108/09/04 01:30:25
Invalid values in hardware clock: 2108/09/04 01:30:25
The Hardware Clock registers contain values that are either invalid
(e.g. 50th day of month) or beyond the range we can handle (e.g. Year 2095).
ss20-1:/dev# date
Wed Sep 3 21:30:52 EDT 2008
next prev parent reply other threads:[~2008-09-04 1:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 16:32 [PATHC 0/2] sparc32: convert to RTC subsystem Krzysztof Helt
2008-09-03 21:41 ` David Miller
2008-09-03 21:54 ` Andrew Morton
2008-09-03 22:12 ` David Miller
2008-09-04 1:42 ` Robert Reif [this message]
2008-09-04 1:49 ` David Miller
2008-09-04 2:15 ` Robert Reif
2008-09-08 3:50 ` Robert Reif
2008-09-08 4:26 ` Robert Reif
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=48BF3D1E.503@earthlink.net \
--to=reif@earthlink.net \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.