From: "H. Peter Anvin" <hpa@zytor.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Pavel Machek <pavel@ucw.cz>
Cc: ksummit-discuss@lists.linuxfoundation.org,
lkml <linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [Ksummit-discuss] (Resend) 2038 Kernel Summit Discussion Fodder
Date: Mon, 08 Sep 2014 11:07:52 -0700 [thread overview]
Message-ID: <540DF078.3030601@zytor.com> (raw)
In-Reply-To: <20140908185544.621022b6@alan.etchedpixels.co.uk>
On 09/08/2014 10:55 AM, One Thousand Gnomes wrote:
>> Today, there's good chance there's linux somewhere in your car. (Dashboard,
>> entertainment system). People like to keep cars from 1910 working, and I suspect
>> that is not going to change.
>>
>> So yes, in 2038 people will be running 32bit linux.
>>
>> Whether there will be people putting 32bit linux into new devices is a question,
>> but I suspect answer is still yes.
>
> I'm currently trying to add 64bit longlong support to an initial PCC 8086
> compiler port so I can fix that for some 16bit projects 8-)
>
> My 8bit machines are mostly 2038 safe already.
>
Back in 1985 I decided to Y2K-test my ABC800 8-bit computer. It passed
(they had implemented a windowed year solution which breaks in 2070 or
2080, as I recall.)
-hpa
prev parent reply other threads:[~2014-09-08 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 0:08 John Stultz
2014-08-13 1:33 ` josh
2014-08-13 1:37 ` Andy Lutomirski
2014-08-13 9:18 ` Catalin Marinas
2014-08-13 3:45 ` John Stultz
2014-08-13 20:27 ` Arnd Bergmann
2014-08-13 21:35 ` Arnd Bergmann
2014-08-27 18:34 ` John Stultz
2014-08-23 22:26 ` Pavel Machek
2014-09-08 17:55 ` One Thousand Gnomes
2014-09-08 18:07 ` H. Peter Anvin [this message]
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=540DF078.3030601@zytor.com \
--to=hpa@zytor.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=john.stultz@linaro.org \
--cc=joseph@codesourcery.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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