From: Paul Walmsley <pjw@kernel.org>
To: Nam Cao <namcao@linutronix.de>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Frederik Haxel <haxel@fzi.de>,
Vitaly Wool <vitaly.wool@konsulko.com>
Subject: Re: [PATCH] riscv: Remove support for XIP kernel
Date: Thu, 12 Feb 2026 17:17:15 -0700 (MST) [thread overview]
Message-ID: <14f964c0-c4e1-c8c7-2a04-6cd5d0cee64e@kernel.org> (raw)
In-Reply-To: <20260202115403.2119218-1-namcao@linutronix.de>
On Mon, 2 Feb 2026, Nam Cao wrote:
> XIP has a history of being broken for long periods of time. In 2023, it was
> broken for 18 months before getting fixed [1]. In 2024 it was 4 months [2].
>
> And now it is broken again since commit a44fb5722199 ("riscv: Add runtime
> constant support"), 10 months ago.
>
> These are clear signs that XIP feature is not being used.
>
> I occasionally looked after XIP, but mostly because I was bored and had
> nothing better to do.
>
> Remove XIP support. Revert is possible if someone shows up complaining.
>
> Link: https://lore.kernel.org/linux-riscv/20231212-customary-hardcover-e19462bf8e75@wendy/ [1]
> Link: https://lore.kernel.org/linux-riscv/20240526110104.470429-1-namcao@linutronix.de/ [2]
> Signed-off-by: Nam Cao <namcao@linutronix.de>
> Cc: Frederik Haxel <haxel@fzi.de>
> Cc: Vitaly Wool <vitaly.wool@konsulko.com>
Thanks, queued here - first for an experimental branch, and ultimately for
v7.1.
- Paul
next prev parent reply other threads:[~2026-02-13 0:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 11:54 [PATCH] riscv: Remove support for XIP kernel Nam Cao
2026-02-13 0:17 ` Paul Walmsley [this message]
2026-02-13 0:22 ` Conor Dooley
2026-02-13 9:37 ` Kunwu Chan
[not found] ` <CAM4kBBK=b73LZQesfypJ95+68aM_oAp3-VZ2BcGNm2NK6UpK7w@mail.gmail.com>
2026-02-13 9:48 ` igor.b
2026-02-13 10:43 ` Conor Dooley
2026-02-20 15:16 ` Jisheng Zhang
2026-02-20 15:20 ` Jisheng Zhang
2026-03-20 16:04 ` Charles Mirabile
2026-03-26 16:45 ` Nam Cao
2026-03-26 17:37 ` Charles Mirabile
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=14f964c0-c4e1-c8c7-2a04-6cd5d0cee64e@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=haxel@fzi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=namcao@linutronix.de \
--cc=palmer@dabbelt.com \
--cc=vitaly.wool@konsulko.com \
/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