linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Steven Hein <ssh@sgi.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 860 RTC support
Date: Wed, 18 Apr 2001 17:20:01 -0400	[thread overview]
Message-ID: <3ADE0501.321052F9@mvista.com> (raw)
In-Reply-To: 3ADE0222.BF7F539C@sgi.com


Steven Hein wrote:

> Is there a working method (to read the RTC value at boot-time)?

The MPC8xx real-time clock is implicitly managed in the kernel.
At boot time, the register is read and stored in the kernel
time.  Whenever the kernel time is updated, the hardware register
is also updated.  Since the 8xx is simply a 32-bit register
access with an update rate that matches the kernel time, I
chose to do it this way.

If you provide the appropriate crystal and battery to the 8xx,
you get a non-volatile time of day clock.

Most implementations seem to choose an external time of day clock
that is already managed by one of the RTC drivers.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-04-18 21:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 21:07 860 RTC support Steven Hein
2001-04-18 21:20 ` Dan Malek [this message]
2001-04-19 16:33   ` Steven Hein
2001-04-19 19:16     ` Dan Malek
2001-04-19 19:38       ` Dan Malek
2001-04-19 19:59         ` Steven Hein
2001-04-20  9:46           ` Gabriel Paubert
2001-04-19 19:40       ` Steven Hein
2001-04-20  3:27         ` Gabriel Paubert
2001-04-20  9:10         ` Gabriel Paubert
2001-04-19 19:44       ` Tom Rini
2001-04-19 19:54         ` Steven Hein
2001-04-19 20:06           ` Tom Rini
2001-04-19 20:22             ` Steven Hein
2001-04-19 22:40               ` Tom Rini
2001-04-20  2:20                 ` Steve Hein
2001-04-19 20:08           ` Tom Rini
2001-04-20 15:51             ` Steven Hein
2001-04-20 15:55               ` Tom Rini
2001-04-19 20:01         ` Dan Malek

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=3ADE0501.321052F9@mvista.com \
    --to=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=ssh@sgi.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).