Rasclock (PCF2127 ) Hardware Clock FreeBSD 12.0

[Ian Lepore]

On Thu, 2019-07-18 at 23:33 +0300, Stefan Parvu wrote:
> hang on. something is odd. Take a look: after copying the new
> nxprtc.ko do I need to 
> regenrate the linker.hints file ?
> 
> root at k1:~ # dmesg | grep nxp
> nxprtc0: <NXP PCF2129 RTC> at addr 0xa2 on iicbus0
> nxprtc0: WARNING: RTC battery failed; time is invalid
> nxprtc0: registered as a time-of-day clock, resolution 0.015625s
> nxprtc0: RTC clock not running
> nxprtc0: detached
> warning: KLD '/boot/kernel/nxprtc.ko' is newer than the linker.hints
> file
> nxprtc0: <NXP PCF2129 RTC> at addr 0xa2 on iicbus0
> nxprtc0: registered as a time-of-day clock, resolution 0.015625s
> 
> What I did was:
> 
> 
> 1. Boot system, which had wrong time. RTC present.
> 
> 2. Fixed the time using date command, Started NTPD
> 
> 3. kldunload and kldload again nxprtc driver which dumped this
> warning:
> 

I don't think it's important in this case that you rebuild the hints
file, because the module doesn't export any new symbols or have a
changed version or anything else that would affect the hints.

-- Ian

> 
> 
> Stefan Parvu
> sparvu at kronometrix.org
> 
> 
> 
> > On 18 Jul 2019, at 23.29, Stefan Parvu <sparvu at kronometrix.org>
> > wrote:
> > 
> > check. all good. battery installation is all good.
> > 
> > In fact the clock functions but for very short periods of time.
> > thats what I have seen. Its like 
> > keeping the time for 5-10 minutes or so. If I stop the system for
> > 1hr+ time is lost. I can check
> > again
> > 
> > 
> > Stefan Parvu
> > sparvu at kronometrix.org
> > 
> > 
> > 
> > > On 18 Jul 2019, at 23.25, Stefan Parvu <sparvu at kronometrix.org>
> > > wrote:
> > > 
> > > LOL . Well u never know that. Let me check. With 2 kids around
> > > everything is 
> > > possible. 
> > > 
> > > Stefan Parvu
> > > sparvu at kronometrix.org
> > > 
> > > 
> > > 
> > > > On 18 Jul 2019, at 23.22, Ian Lepore <ian at freebsd.org> wrote:
> > > > 
> > > > On Thu, 2019-07-18 at 23:16 +0300, Stefan Parvu wrote:
> > > > > I think after your latest commit I see a function from nxprtc
> > > > > module
> > > > > which does not 
> > > > > exist in the original module. Take a look:
> > > > > 
> > > > > root at k1:/var/tmp # nm -A -a /boot/kernel/nxprtc.ko | grep
> > > > > readfrom
> > > > > /boot/kernel/nxprtc.ko:0000000000010ab8 t nxprtc_readfrom
> > > > > 
> > > > > which I do not see under original nxprtc module such thing. 
> > > > > 
> > > > > root at k1:/var/tmp # nm -A -a /var/tmp/nxprtc.original.ko |
> > > > > grep
> > > > > readfrom
> > > > > /var/tmp/nxprtc.original.ko:                 U
> > > > > iicdev_readfrom
> > > > > 
> > > > > Is this right ? Is this something you have fixed on the
> > > > > latest and
> > > > > the greatest
> > > > > nxprtc version ?
> > > > > 
> > > > > 
> > > > 
> > > > Yep, that is good confirmation that the fix is in that module.
> > > > 
> > > > I almost hesitate to say it, but... the symptoms you're seeing
> > > > are
> > > > exactly what would happen if the battery was installed upside-
> > > > down. :)
> > > > 
> > > > -- Ian
> > > 
> > > _______________________________________________
> > > freebsd-arm at freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > > To unsubscribe, send any mail to "
> > > freebsd-arm-unsubscribe at freebsd.org"
> > 
> > _______________________________________________
> > freebsd-arm at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > To unsubscribe, send any mail to "
> > freebsd-arm-unsubscribe at freebsd.org"
> 
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org
> "