From: Tom Rini <trini@kernel.crashing.org>
To: Steven Hein <ssh@sgi.com>
Cc: Dan Malek <dan@mvista.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: 860 RTC support
Date: Thu, 19 Apr 2001 13:08:42 -0700 [thread overview]
Message-ID: <20010419130842.Q13403@opus.bloom.county> (raw)
In-Reply-To: <3ADF426A.5E9C0EBD@sgi.com>; from ssh@sgi.com on Thu, Apr 19, 2001 at 02:54:18PM -0500
On Thu, Apr 19, 2001 at 02:54:18PM -0500, Steven Hein wrote:
> Tom Rini wrote:
> >
> > I think I understand the question/problem too. We'll see what else I've
> > got to work on as well. :) Just checking, Steven have you tried to
> > enable the "PPC_RTC" driver and gotten this same incorrect behavior?
>
> The only place I see references to PPC_RTC is in some of the PPC
> "defconfig" files. I don't see any other places where that is
> references in the 2.4.3 kernel.....
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. :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-19 20:08 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 [this message]
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=20010419130842.Q13403@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=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).