public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RTC Question
Date: Fri, 08 Oct 2004 20:17:37 +0200	[thread overview]
Message-ID: <20041008181742.B27ADC1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 08 Oct 2004 09:27:21 PDT." <6.1.1.1.0.20041008090220.01e07ec0@wheresmymailserver.com>

In message <6.1.1.1.0.20041008090220.01e07ec0@wheresmymailserver.com> you wrote:
> 
> General question, in the specific processor (Blackfin BF533) that I am 
> using, the on-board RTC can have a 32768 days, and defaults to starting at 
> 01Jan1970. This means that RTC rollover will occur around Fri, 19-Sep-2059 
> 11:59pm. On Sat 20-Sep-2059, the date will be displayed as Thur 01-Jan-1970.
> 
> Should I add extra complexity, to extend things past this?

Hou could you fix this? U-Boot will probably not even be running when
the rollover happens, so it has zero chance to notice. Of course  you
can  assume that no board will ever show a legal time before 2004, so
you could always add of offset equivalent to 34 years to  your  RTC's
date,  shifting  the  problem until 2093 ... The offset is trivial to
implement, and probably all you ever need.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Microsoft Compatibility:
     your old Windows 3.11 application crash exactly as the new ones.

  reply	other threads:[~2004-10-08 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 16:27 [U-Boot-Users] RTC Question Robin Getz
2004-10-08 18:17 ` Wolfgang Denk [this message]
2004-10-08 21:55   ` Frank
2004-10-08 22:10     ` Wolfgang Denk
2004-10-08 19:49 ` Victor Wren
  -- strict thread matches above, loose matches on Subject: below --
2004-10-08 23:37 Robin Getz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041008181742.B27ADC1430@atlas.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox