From: Paul S. <pa...@cl...> - 2010-02-17 06:05:33
|
Hi Steve, Thanks for the reply, the reason I ended up on a 2.6.33 is probably due to my inexperience with git. I was looking to maintain a kernel tree outside the open embedded environment and so I did a git clone of the kernel tree for omap-linux and ended up with 2.6.33rc6. Is there any easy way I can get the current 2.6.32 source from the same git repository? I am using the following source: git://gitorious.org/linux-omap/mainline.git also is this the correct place to get the kernel from as I have also seen this source being thrown about: git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git Regards, Paul -----Original Message----- From: Steve Sakoman [mailto:sa...@gm...] Sent: Wednesday, 17 February 2010 4:50 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Overo RTC with kernel 2.6.33rc6 On Tue, Feb 16, 2010 at 4:14 PM, Paul Solomon <pa...@cl...> wrote: > Hi All, > > I am running the 2.6.33 on my Gumstix Overo and I have just noticed that the > RTC driver is not working. It times out. It appears that between 2.6.32 and > 2.6.33 the driver has been made more generic and changed from rtc_twl4030.c > to rtc_twl.c. Does anyone know why this new driver would not work with a > standard Overo. I have looked through the code and it is very similar, it > just has additional supported added for another similar chipset. Using 2.6.33 prior to final release is playing with fire! There is a reason that there isn't a 2.6.33 recipe in the repository :-) I would advise that you use 2.6.32, especially if you are using it for product development. The command line utilities work on my 2.6.32 based image. Steve > The actual issue that I am having is the RTC driver appears to load > correctly and the time is read out of the chip correctly. However the > command line tools such as hwclock just timeout. > > > > I managed to set the clock to 2010-01-01 using a 2.6.32 image, so this shows > the hardware is ok, and also that the 2.6.33 driver is reading the time out > at boot time. It is just the hwclock is not working so I have no way of > setting the hwclock to the real time in 2.6.33 > > > > Additional debug info below! > > > > :~# dmesg | grep rtc > > twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 > > twl_rtc twl_rtc: setting system clock to 2010-01-01 02:02:06 UTC > (1262311326) > > > > :~# uname -a > > Linux ncontrol2 2.6.33-rc6 #2 Thu Feb 11 17:21:43 EST 2010 armv7l GNU/Linux > > > > :~# hwclock > > select() to /dev/rtc0 to wait for clock tick timed out > > > > > > > > -------------------------------------------------------------------------- ---- > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -------------------------------------------------------------------------- ---- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |