Yes. No. Maybe. You answer, and I'll go with whatever you decide.

Thanks for the offer.

It isn't an offer. It is a question. Your efforts to provide Raspberry Pi support to Slackware ARM were useful. Now the goal is for the community to provide hardware model contributions directly.

Thanks for the question.

I know my efforts were, and still are, useful to this day. I love doing what I do with the SARPi Project and how I do it. Not wanting a prestigious title or recognition. Or to embrace any delusions of grandeur that it means anything. I'm fine where I am, for now.

You're doing a great job for the Slackware ARM community. Keep on doing it. Well done you.

I am not disputing your efforts or how useful sarpi is/was/will be. I have been respectfully sharing my opinion. There is a build script that takes forked or modified kernel source and puts it all into Slackware packages for consumption. This includes the Raspberry Pi (and other boards) kernel and other bits.

• slackwarearm/slackwareaarch64-current/source/k/build_altsrc_kernel.sh
• slackwarearm/slackwareaarch64-current/source/k/build_altsrc_kernel.conf/rpi

My earlier comments are not solely directed at you, or a criticism of your work. My intention is to encourage others to contribute to Slackware. There is nothing prestigious. Recognition is not required. If not interested, ignore. I apologize for any frustrations.

With that said, Sarpi is still useful for those who do not wish to build a Raspberry Pi foundation kernel on their own. However, occasionally there are experimental packages generated for Raspberry Pi consumption, found here: slackwarearm/experimental/slackwareaarch64-current/rpi-kernel-fork/

I'm far too busy or unconcerned for this Brent. If you want to rally support for Slackware ARM perhaps making your own thread would be a prositive first step. We're going way off topic here.