linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: kevin diggs <diggskevin38@gmail.com>
Cc: Linux PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: RTC on 2.6.36 for PowerMac 8600
Date: Tue, 31 Jan 2012 20:06:09 +1100	[thread overview]
Message-ID: <1328000769.28487.72.camel@pasglop> (raw)
In-Reply-To: <CAKTLLVQTt8aRFb2QpXkUUikTJshnV_ytTWJ778MZ1ACyoD8aOw@mail.gmail.com>

On Sat, 2012-01-28 at 21:08 -0600, kevin diggs wrote:
> Hi,
> 
> What will give me access to the RTC hardware on an old PowerMac 8600?
> I modload rtc-generic. /proc/devices has:

should work with rtc generic, not sure what's up.

You can check with printk ... rtc_generic should call into get_rtc_time
which should go via ppc_md. into some powermac specific variants,
themselves calling into the cuda driver.

Cheers,
Ben.

> 254 rtc
> 
> and ls -l /dev/rtc*:
> 
> crw-r--r--  2 root root 254,   0 Sep  2  2010 /dev/rtc
> crw-r--r--  2 root root 254,   0 Sep  2  2010 /dev/rtc0
> crw-r--r--  1 root root  10, 135 Aug 10  2004 /dev/rtc.old
> 
> Trying to run hwclock gives:
> 
> [root@PowerMac8600B root]# hwclock --debug
> hwclock from util-linux-2.12pre
> Using /dev/rtc interface to clock.
> Last drift adjustment done at 1317444443 seconds after 1969
> Last calibration done at 1317444443 seconds after 1969
> Hardware clock is on local time
> Assuming hardware clock is kept in local time.
> Waiting for clock tick...
> /dev/rtc does not have interrupt functions. Waiting in loop for time
> from /dev/rtc to change
> RTC_RD_TIME: Invalid argument
> ioctl() to /dev/rtc to read the time failed.
> 
> I could have sworn this used to work on this system???
> 
> What am I forgetting?
> 
> gzip -dc /proc/config.gz|grep -i rtc lists:
> 
> CONFIG_RTC_LIB=m
> CONFIG_RTC_CLASS=m
> # RTC interfaces
> CONFIG_RTC_INTF_SYSFS=y
> CONFIG_RTC_INTF_PROC=y
> CONFIG_RTC_INTF_DEV=y
> # Platform RTC drivers
> CONFIG_RTC_DRV_CMOS=m
> # on-CPU RTC drivers
> CONFIG_RTC_DRV_GENERIC=m
> 
> Thanks!
> 
> kevin
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

  reply	other threads:[~2012-01-31  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29  3:08 RTC on 2.6.36 for PowerMac 8600 kevin diggs
2012-01-31  9:06 ` Benjamin Herrenschmidt [this message]
     [not found] <CAKTLLVQTt8aRFb2QpXkUUikTJshnV_ytTWJ778MZ1ACyoD8aOw__43210.997261531$1327806577$gmane$org@mail.gmail.com>
2012-01-29  8:29 ` Andreas Schwab
2012-01-31 19:31   ` kevin diggs

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=1328000769.28487.72.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=diggskevin38@gmail.com \
    --cc=linuxppc-dev@ozlabs.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 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).