Hi Ethan, hi Wolfram, Thank you for your thoughtful responses.
On Mon, May 18, 2026 at 05:13:58PM -0700, Ethan Nelson-Moore wrote: > Your reasoning makes complete sense. However, there is an alternative > to maintaining the architecture in mainline. > > The Civil Infrastructure Platform project maintains super-LTS kernels > (and a set of base Debian packages) for 10 years. They are intended to > be used for exactly these kinds of devices. > See here: > https://wiki.linuxfoundation.org/civilinfrastructureplatform/start#kernel_maintainership > and here: https://cip-project.org/about/linux-kernel-core-packages > > CIP will maintain kernel 6.12 until 2035. Is this long enough for your > lifecycle? What kernel are you currently using? If it's newer than > 6.12, we can easily wait until the next CIP SLTS release to remove > Nios II support to avoid a downgrade. This depends. For released/maintained firmware revisions we already track CIP SLTS versions (candidates) to be prepared, the majority of which is currently still running 6.1.x with 6.12.x up-and-coming. But for the reasons outlined by you regarding architectural and feature support in CIP SLTS, we do not, however, use the extended support duration SLTS releases in production, and instead upgrade with the kernel.org LTS branch release schedule and track these internally alongside mainline to prevent major obstacles during version jumps. 2035 is still a rather tight timeframe for our typical support/phase-out period (we would hope to get close to 2040 with the SLTS extensions), which is also the reason for our targeted 'lifetime extension' for the nios2 architecture for approximately 5 years, or more precisely ~2-3 SLTS kernels assuming the usual cadence of 2 years between SLTS versions (+ some safety margin). > Also, CIP focuses on architectures used by CIP members - currently I > think they are x86 (32 and 64-bit), ARM (32 and 64-bit) and RISC-V. > Since Siemens is already a CIP member, you can simply ask them to add > Nios II to the list, and you can assist them with testing and directly > submit patches to them once the standard 6.12 LTS period ends. We have already been in contact with the CIP team (even though the contact has unfortunately lapsed a bit, mostly our fault), but adding an additional architecture seemed to be a more substantial effort. N.B.: Due to past circumstances, we are a completely distinct business entity from Siemens AG that merely shares the trademark and a common history; but of course this should not hinder us from getting directly involved in CIP (quite the opposite!). But this also requires some setup time. On Mon, May 18, 2026 at 10:46:55PM +0200, Wolfram Sang wrote: > > If desired, we also would be happy to intensify our support regarding > > reviews or testing to share the maintnance burden if it helps to keep > > nios2 in mainline a bit longer. > > ... but given this, you might want to get added in MAINTAINERS as > reviewer (or even maintainer) for nios2? Besides that your efforts are > already worth it in my book, it would also ensure you get CCed on > patches like this. Then, you are not depending on people like Arnd > putting you in the loop manually. Sure, I'd be glad to do so, but so far I refrained from it as I was a bit unsure about the netiquette (can I simply do so by self-proclamation? At least the git history seems to suggest so...). Best regards, Simon
