[OM2009] Testing 2009-06-11: Misreading hardware clock

[Joerg Reisenweber]

Am Sa  13. Juni 2009 schrieb David Fokkema:
> On Sat, 2009-06-13 at 18:02 +0200, Rask Ingemann Lambertsen wrote:
> > Out of curiosity, I had a look at OM2009:
> > 
> > # flash_eraseall /dev/mtd6
> > # wget --no-verbose \
> >   
http://downloads.openmoko.org/distro/testing/daily/NeoFreerunner/fso-paroli-image-om-gta02.jffs2 
\
> >   -O - | nandwrite -p /dev/mtd6 -
> > 
> > # flash_eraseall /dev/mtd3
> > # wget --no-verbose \
> >   
http://downloads.openmoko.org/distro/testing/daily/NeoFreerunner/uImage-2.6.28-stable+gitr0+f19f259d3c1afde8eae53983fd19f61831927413-r2-om-gta02.bin 
\
> >   -O - | nandwrite -p /dev/mtd3 -
> > 
> >    The screen says "16:53 Monday, July 13, 2009". That makes it exactly 
one
> > month ahead of time. The 2.6.28 kernel needs a backport of these two
> > patches:
> > 
> > 
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=60c66130a4467ca2a2994a6e3d7d5ac63839eefb
> > 
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=cc1663fc922c03feb0d7bbb8b18d62fbac0128de
> > 
> 
> How strange. I've never seen that with Om2009. But, to tell the truth,
> I'm not using any other distro on my phone. It might be the case that
> Om2009 gets the current datetime from the GSM network after a few
> minutes and will set the clock 'correctly' after that.

If setting hwclock is done with same "month off by 1" algo you use for reading 
it, you probably only will notice your months have wrong number of days (RTC 
counting to 31. for July (May?), readout algo says June 31.)

/j
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.openmoko.org/pipermail/support/attachments/20090614/1105b148/attachment.pgp