mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Taube-Perrotta <jtaubepe@redhat.com>
To: cmirabil@redhat.com
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, haxel@fzi.de,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	namcao@linutronix.de, palmer@dabbelt.com, pjw@kernel.org,
	vitaly.wool@konsulko.com, Kunwu Chan <kunwu.chan@linux.dev>,
	Zhouyi Zhou zhou <zhouyi@gmail.com>,
	igor.b@beldev.am, Jisheng Zhang <jszhang@kernel.org>,
	Albert Ou <aou@eecs.berkeley.edu>, Frederik Haxel <haxel@fzi.de>,
	charlie@rivosinc.com
Subject: Re: [PATCH] riscv: Remove support for XIP kernel
Date: Fri, 29 May 2026 13:20:48 -0400	[thread overview]
Message-ID: <05290c17-d55f-4e60-a77e-c36c3f14a89a@redhat.com> (raw)
In-Reply-To: <CABe3_aH6jYyoC=Jx91qATP2kOoY42NUtesyZpGbWGoQTw75OAA@mail.gmail.com>

 > It is true, though I would like it to continue to be possible
 > upstream. When I wrote this I didn't realize that XIP is currently not
 > compatible with M-mode linux. I think that would be a really useful
 > combination that might actually make XIP something that people
 > se/test since both m-mode / nommu linux and xip are more common in
 > embedded usecases.

IIRC there was a patch that made XIP work on M-mode no-mmu linux for 
only 64bit.

I unfortunately missed this email, i should check the mailing list 
folder more,

but I am one of the few people that is interested in XIP riscv linux,

quite a few of my personal projects use it. My interest is mostly in the 
no-mmu rv32 use case.

I'm curious if re-adding back XIP,  or i guess just adding,

XIP to no-mmu rv32 would be acceptable as I have some patches

that have been in the works sense 2024 LMFAO.


I now have a job at redhat so maintaining XIP risc-v is a genuine 
possibility especially as

I have quite a bit of experience with it. Ironically charlie sits near 
me in the office. Hi charlie!

 > I was hoping to develop patches for that functionality too and prove
 > that it works on real hardware. But in order to do that I would need
 > to figure out m-mode linux on unleashed/qemu sifive_u (almost
 > certainly possible, but I haven't really tested it) and also XIP linux
 > on unleased/sifive_u (which as I said is close, but with at least one
 > more issue) and then combine them simultaneously (unclear how hard
 > lol).

I also have hardware and a FPGA soft-core i can test this on.

TLDR: Is re-adding XIP to no-mmu rv32 a possibility

Sorry if i messed up the reply i just setup this email client.

Thanks,
Jesse Taube


  reply	other threads:[~2026-05-29 17:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 11:54 Nam Cao
2026-02-13  0:17 ` Paul Walmsley
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
2026-05-29 17:20       ` Jesse Taube-Perrotta [this message]
2026-06-01  8:26         ` Nam Cao

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=05290c17-d55f-4e60-a77e-c36c3f14a89a@redhat.com \
    --to=jtaubepe@redhat.com \
    --cc=CABe3_aH6jYyoC=Jx91qATP2kOoY42NUtesyZpGbWGoQTw75OAA@mail.gmail.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=cmirabil@redhat.com \
    --cc=haxel@fzi.de \
    --cc=igor.b@beldev.am \
    --cc=jszhang@kernel.org \
    --cc=kunwu.chan@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=vitaly.wool@konsulko.com \
    --cc=zhouyi@gmail.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

Powered by JetHome