(modified the cc-list somewhat) On Sat, 18 Oct 2008, Rogério Brito wrote:
> systems. Here is something that I get with a vanilla linkstation_defconfig: > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > This gets me (with bootlogd enabled): > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Wed Dec 31 21:00:15 1969: Cannot access the Hardware Clock via any known > method. > Wed Dec 31 21:00:15 1969: Use the --debug option to see the details of our > search for an access method. > Wed Dec 31 21:00:15 1969: Unable to set System Clock to: Thu Jan 1 00:00:15 > UTC 1970 ^[[33m(warning).^[[39;49m > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Yes, there seems to be a problem here now. The i2c adapter does not get probed, i.e., of-matching doesn't work. A quick look through other device-trees, using the same i2c driver, through git-logs of the i2c driver and the dts didn't bring me to a solution. Can anyone spot what's wrong with kuroboxHG.dts? lsprop output looks reasonable. Last working kernel was 2.6.25-rc6-ish. > I just saw that in the default config: > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > # CONFIG_PPC_CLOCK is not set > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - No, kurobox uses generic RTC class. Thanks for the report Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
