3 ms·
> In mainline linux, XIP support on RISC-V was removed, so 6.12 was used instead which has proper XIP support. Doesn't that put it in an awkward position relyi
by yjftsjthsd-h 3mo ago
> In mainline linux, XIP support on RISC-V was removed, so 6.12 was used instead which has proper XIP support.
Doesn't that put it in an awkward position relying on a dead end feature?
- Neywiny 3mo agoWhat I remember was they said it could come back if people needed it but it was broken for looking (months, years) at a time. So even if they didn't remove it, 6.12 might be the last working version with it anyway
- iririririr 3mo agoit's common to move "unused" code to patches
- grieferpig 3mo agoThere are other ports that uses newer kernels (iirc annoyedmilk/esp32-s31-linux used 7.1). XIP saves me RAM, and on a device with 16mib ram I need to squeeze as much ram as possible. Besides I couldn't think of any use cases where you really need a newer kernel
- yjftsjthsd-h 3mo agoI absolutely see the appeal for XIP here! I just have been sufficiently traumatized by Android devices that anything that breaks the ability to follow upstream makes me nervous. I'm sure it's workable here, both because this is a recent enough version that it'll be supported for a long time and because I expect it can be ported forward if really needed. (And of course, at this point it's not like this is a real production thing so as an experiment who cares.)