From: Victor Wren <vwren@timension.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RTC Question
Date: Fri, 08 Oct 2004 11:49:46 -0800 [thread overview]
Message-ID: <41667EDA.27154.23412A@localhost> (raw)
In-Reply-To: <6.1.1.1.0.20041008090220.01e07ec0@wheresmymailserver.com>
> 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?
> I see issues in other code that will roll over around 19Jan2038, so I would
> expect that others are not concerned about it?
This is a common discussion on many boards. Actually, most variants of Linux
will roll over in 2038. Eventually (within the next five years, I'm guessing)
the move will probably be made to 64-bit clocks. It's not a matter of 32768
days, but 2^31-1 seconds (for signed int), so a 64-bit clock will push out
the rollover to the year 292,271,025,015 (roughly), or about 50 times the age
of our solar system.
Considering that 2038 is 34 years away, though (remember that 34 years ago
was 1970) it's pretty likely that hardware is going to be considerably
different by then, and anything made today will be a distant memory. I could
be wrong. Anybody still running embedded devices made in 1970?
Victor Wren
next prev parent reply other threads:[~2004-10-08 19:49 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
2004-10-08 21:55 ` Frank
2004-10-08 22:10 ` Wolfgang Denk
2004-10-08 19:49 ` Victor Wren [this message]
-- 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=41667EDA.27154.23412A@localhost \
--to=vwren@timension.com \
--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