[PATCH] riscv: Remove support for XIP kernel

[Jesse Taube-Perrotta]

 > 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