Rasclock (PCF2127 ) Hardware Clock FreeBSD 12.0

[Stefan Parvu]

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 ?


Stefan Parvu
sparvu at kronometrix.org



> On 18 Jul 2019, at 23.01, Stefan Parvu <sparvu at kronometrix.org> wrote:
> 
> Sone differences between our systems
> 
> * Im using Rasclock 4.0, you are in 4.2 
> 
> * Im using RBPI3B+, you are in RBPI2
> 
> Not sure if these really matter but just in case Im mentioning.
> 
>> 
>> It occurred to me: are you sure you're using the fixed driver?  One of
>> the problems before the fix was that a read would succeed, but return
>> the wrong values.  So the status register reads might be getting a
>> wrong value and interpretting that as the "battery failed bit is set”.
>> One thing that comes to mind:  you're using this as a module, but is
>> the nxprtc driver already built in to the kernel?  I think if it is and
>> you added nxprtc_load=YES to loader.conf, it'll load the module but
>> then still use the driver already in the kernel.
> 
> huh. Are you saying the nxprtc driver is already built-in the kernel ? 
> Why ? Shouldn’t that be just a driver what you can load on demand,
> if users need ?
> 
> Yes, I do have under loader.conf nxprtc_load=“YES”. But still some questions 
> here:
> 
> * if I do not load the driver under loader.conf, nothing works, I cannot see the
> clock or use it anyhow 
> 
> * how can I make sure there is NO nxprtc within kernel ? Can I see the routines
> function calls somehow, if i kldunlod the nxprtc driver ?
> 
> I do believe Im using the right thing after your commit. I can again double check that
> 
> Stefan
> _______________________________________________
> 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"
>