On Fri, May 15, 2009 at 11:31:12AM +0200, Andreas Schwab wrote: > Lance Tagliapietra <[email protected]> writes: > > > Now, there is a /dev/rtc device of type 10 135. Interestingly, though is > > that the > > kernel is looking for an "rtc0" device based on the kernel config. So I'll > > make > > that change to the kernel config and re-build and see what I get -- or > > would it > > be a better approach to add a /dev/rtc0 c 10 135? > > I think you need a c 254 0 device if you use rtc-generic. > > Andreas. > > -- > Andreas Schwab, [email protected] > GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 > "And now for something completely different." > -- > To unsubscribe from this list: send the line "unsubscribe linux-m68k" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html
I beleive I made a mistake here. I compiled my kernel (and the other 2.6.xx kernels I have tried) were compiled with CONFIG_RTC_CLASS=y instead of CONFIG_GEN_RTC=Y and CONFIG_GEN_RTC_X=y which I have now determined are the defaults for the m68k arch, and also the options used in my properly working 2.4.30 kernel. That is why the "/dev/rtc0" showed up in the .config. I am re-building my kernel to test. Thanks, --Lance -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
