From: Steven Hein <ssh@sgi.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Dan Malek <dan@mvista.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: 860 RTC support
Date: Fri, 20 Apr 2001 10:51:01 -0500 [thread overview]
Message-ID: <3AE05AE5.1AA8DFA2@sgi.com> (raw)
In-Reply-To: 20010419130842.Q13403@opus.bloom.county
Tom Rini wrote:
>
>
> Okay, it doesn't _quite_ work (hwclock will oops) but hopefully it
> won't be too hard to track down. I'll try and get to it this afternoon
> or tomorrow, or when time permits (!+@$*ing classes). Patches greatly
> appreciated. :)
>
I don't have a patch put together yet, but I found the problem:
m8xx_get_rtc_time is an __init function in the 2.4.x tree.
Remove the __init and it works great!
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Hein (ssh@sgi.com) Engineering Diagnostics/Software
Silicon Graphics, Inc.
1168 Industrial Blvd. Phone: (715) 726-8410
Chippewa Falls, WI 54729 Fax: (715) 726-6715
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-20 15:51 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
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 [this message]
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=3AE05AE5.1AA8DFA2@sgi.com \
--to=ssh@sgi.com \
--cc=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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.