All of lore.kernel.org
 help / color / mirror / Atom feed
* RTC question
@ 2002-04-15 21:52 Lanny DeVaney
  2002-04-16  0:18 ` Jun Sun
  0 siblings, 1 reply; 2+ messages in thread
From: Lanny DeVaney @ 2002-04-15 21:52 UTC (permalink / raw)
  To: linux-mips

I've used the NEW_TIME_C method to implement support for the Dallas 1501 
RTC in my MIPS port .  I now successfully read the hw clock, and the 
date program works, and I can change the time.

However, the hwclock program tells me that it can't access the Hardware 
Clock and tells me that /dev/rtc doesn't exist (although it actually 
does) when running hwclock --debug.  Also, I see an oddity that may be 
related - ping reports zero (as in 0 msec) round trip times always.  I 
configured CONFIG_RTC into the kernel, and checked the major, minor of 
/dev/rtc on my embedded ramdisk.  Also, I don't see /proc/driver/rtc.  

Is this normal behavior with NEW_TIME_C  configurations?  I've checked 
my rtc_get_time and rtc_set_time, ..., like I said, the 'date' program 
works, reading and writing to the clock.

Thanks,
Lanny DeVaney

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RTC question
  2002-04-15 21:52 RTC question Lanny DeVaney
@ 2002-04-16  0:18 ` Jun Sun
  0 siblings, 0 replies; 2+ messages in thread
From: Jun Sun @ 2002-04-16  0:18 UTC (permalink / raw)
  To: Lanny DeVaney


Ralf has not checked in the higher-level RTC driver yet.  You can either
build a kernel from the linux-mips project on sourceforge.net, where the driver
is included, or try to apply the outdated patch from

http://linux.junsun.net/patches/oss.sgi.com/submitted/011110.mips-rtc.011110.1900.patch

It was created on Nov 11, 2001.

Jun

On Mon, Apr 15, 2002 at 04:52:39PM -0500, Lanny DeVaney wrote:
> I've used the NEW_TIME_C method to implement support for the Dallas 1501 
> RTC in my MIPS port .  I now successfully read the hw clock, and the 
> date program works, and I can change the time.
> 
> However, the hwclock program tells me that it can't access the Hardware 
> Clock and tells me that /dev/rtc doesn't exist (although it actually 
> does) when running hwclock --debug.  Also, I see an oddity that may be 
> related - ping reports zero (as in 0 msec) round trip times always.  I 
> configured CONFIG_RTC into the kernel, and checked the major, minor of 
> /dev/rtc on my embedded ramdisk.  Also, I don't see /proc/driver/rtc.  
> 
> Is this normal behavior with NEW_TIME_C  configurations?  I've checked 
> my rtc_get_time and rtc_set_time, ..., like I said, the 'date' program 
> works, reading and writing to the clock.
> 
> Thanks,
> Lanny DeVaney
> 
> 
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-04-16  0:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-04-15 21:52 RTC question Lanny DeVaney
2002-04-16  0:18 ` Jun Sun

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.