Re: rtc and chrony on Ultra 1 and Ultra 5

["David S. Miller" <davem@davemloft.net>]

On Tue, 19 Apr 2005 21:07:34 +0200
Frans Pop <aragorn@tiscali.nl> wrote:

> I've added a debug statement in this code, which gives the following output:
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus auxio
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus power
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus SUNW,pll
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus se
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus su
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus su
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus ecpp
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus fdthree
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus eeprom
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus flashprom
> Apr 19 20:39:22 localhost kernel: rtc_init: ebus SUNW,CS4231
> Apr 19 20:39:22 localhost kernel: rtc_init: no PC rtc found
>
> So, apparently __sparc__ is defined for my U10. I also added a similar
> statement in the isa bus scan, so __sparc_v9__ is not set.
> 
> Any ideas where the RTC could be hiding?

__sparc_v9__ should be set when compiling 64-bit code...
Can you add a "#error OK it is set" or something right under
the "#ifdef __sparc_v9__" to make sure?

If you added debugging to the ISA loop and it didn't print out,
this just means that your box lacks that  bus type.

Anyways, "/usr/sbin/prtconf -pv" output would shed more light
on this problem.

Thanks for your debugging so far.