From: "Arnd Bergmann" <arnd@arndb.de>
To: "Pintu Kumar Agarwal" <pintu.ping@gmail.com>
Cc: "Siddh Raman Pant" <sanganaka@siddh.me>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>,
"Neil Armstrong" <neil.armstrong@linaro.org>
Subject: Re: Query: Y2038 patch series for 3.18 Kernel
Date: Thu, 06 Nov 2025 09:17:21 +0100 [thread overview]
Message-ID: <0fe1ce84-b7b2-4c37-a94a-80ddd7339105@app.fastmail.com> (raw)
In-Reply-To: <CAOuPNLh5O0YuRi6=oOSCbaH0zy-kkKUcD__G0Ncw5yAFtko7=Q@mail.gmail.com>
On Wed, Nov 5, 2025, at 10:47, Pintu Kumar Agarwal wrote:
> On Tue, 4 Nov 2025 at 15:18, Arnd Bergmann <arnd@arndb.de> wrote:
>
>> Which chip exactly are you using?
> This request is for one of the legacy QC MDM 9K chipset.
Ah, I see. Support for those was never fully merged, so it's
much harder to upgrade than other platforms, especially
if you need the modem driver to work.
We do have some support for the newer sdx55/sdxx65 chips,
and much more rudimentary support for mdm9607 and mdm9615
(without modem) in mainline, but since we've never had a
fully supported board use the older chips I would not expect
them to work without additional bugfixes and a rebase of
the missing drivers.
There is of course a chance that you may get them to work
in a way that does not rely on knowing the time. If you
don't have (or use) and RTC and the system time is always
set to Jan 1 1970 on boot, this would technically work
indefinitely. Running a 3.18 kernel is obviously a bad idea
for a number of other reasons.
Arnd
next prev parent reply other threads:[~2025-11-06 8:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 4:27 Pintu Kumar Agarwal
2025-11-03 5:04 ` Siddh Raman Pant
2025-11-04 5:02 ` Pintu Kumar Agarwal
2025-11-04 5:08 ` Greg KH
2025-11-04 9:47 ` Arnd Bergmann
2025-11-05 9:47 ` Pintu Kumar Agarwal
2025-11-06 8:17 ` Arnd Bergmann [this message]
2025-12-17 4:53 ` Pintu Kumar Agarwal
2026-01-20 1:05 ` syrus
2026-01-20 9:03 ` Arnd Bergmann
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=0fe1ce84-b7b2-4c37-a94a-80ddd7339105@app.fastmail.com \
--to=arnd@arndb.de \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=pintu.ping@gmail.com \
--cc=sanganaka@siddh.me \
/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
all inboxes | Powered by JetHome®