> I'll try to review and evaluate both solution by the end of the week (no
> guarantee though).
To summarize, it's a pretty simple trade-off. Do you:
a) try to detect every time the RTC deviated from the real-world time
and correct it instantly? This can be done most of the time but there
are edg
Hi Julius, Doug,
On 09/12/2015 at 13:32:52 -0800, Julius Werner wrote :
> > Thinking about all this: these's actually a totally different
> > alternative approach we could take if you wanted. It would fix S5 and
> > avoid all the anchor stuff, unless I'm crazy.
> >
> > Basically totally give up o
> Thinking about all this: these's actually a totally different
> alternative approach we could take if you wanted. It would fix S5 and
> avoid all the anchor stuff, unless I'm crazy.
>
> Basically totally give up on the RTC time reflecting reality. Add a
> "real time to rk808" and "rk808 time to
Julius,
On Mon, Dec 7, 2015 at 9:21 PM, Julius Werner wrote:
> In Fuzhou, China, the month of November seems to be having 31 days.
> That's nice and all (I'm sure you can get a lot more done in a year that
> way), but back here in other parts of the world we are not so lucky.
> Therefore, we need
In Fuzhou, China, the month of November seems to be having 31 days.
That's nice and all (I'm sure you can get a lot more done in a year that
way), but back here in other parts of the world we are not so lucky.
Therefore, we need to compensate for these extra days existing only in
the RTC's imaginat
5 matches
Mail list logo
