Since I've been using rpi-update per sarpi and not doing kernels slackware way,

when ChangeLog.txt says something like
a/kernel-firmware-20180518_2a9b2cf-noarch-1.txz: Upgraded.
a/kernel-modules-armv7-4.16.11_armv7-arm-1.txz: Upgraded.
a/kernel_armv7-4.16.11-arm-1.txz: Upgraded.

does slackpkg do the copying over the new firmware, overlays, dtbs, kernel, etc?

I've looked, maybe not hard enough, for how slackwarearm kernel update gets installed.

Thanks

Slackware ARM does not support the RPis, and those kernels have no support for them (so you don't need to use those packages).
You need to follow the instructions for what ever separate project you followed.

2 members found this post helpful.

... and Raspberry Pi (Trading) Ltd does not seem to support, or acknowledge Slackware ARM; because they like pointy-n-clicky things for NOOBS.

I'll buILD ONE!


Good advice!

1 members found this post helpful.

Let me rephrase, if using Slackware ARM on a Slackware ARM supported device

when ChangeLog.txt says something like
a/kernel-firmware-20180518_2a9b2cf-noarch-1.txz: Upgraded.
a/kernel-modules-armv7-4.16.11_armv7-arm-1.txz: Upgraded.
a/kernel_armv7-4.16.11-arm-1.txz: Upgraded.

does slackpkg do the copying over the new firmware, overlays, dtbs, kernel, etc?


I'm not interested in doing this with my rpi3.

To upgrade these packages, you run upgradepkg and it's all taken care of -- but _only_ on supported devices where /boot is on a Linux file system (NOT 'FAT' or some variant of), and where you followed the installation instructions (which means that the u-boot configuration has hard coded DTB, initrd and kernel image file names, and the above packages are able to make symlinks (hence why no FAT) to point those static file names to the versioned files).

slackpkg runs upgradepkg, so it's all taken care of (unless you black listed kernel packages, which I don't suggest doing if you're using a supported device).

"Overlays" is solely a RPi concept.

1 members found this post helpful.

That's great Stuart, exactly what I wanted to know, thank you.

latest SARPi installer image for Slackware ARM -current on a Raspberry Pi 3 uses kernel 4.14.43 and was built on Sun, 27 May 2018

Current (pre-release) ChangeLog for ARM Thu May 24 08:08:08 UTC 2018 says
a/kernel_armv7-4.16.11-arm-1.txz: Upgraded.

The difference in kernel versions means there might be some mileage variance when rebuilding whatever? Like something SBo might work for slackwarearm-current but not SARPi?

I stopped fussing with kernels a while back and may build something SBo so I'm not up on kernel stuffs.

Thanks

As far as I know, as long as the kernel-headers are the same as the running Kernel, it's fine.

1 members found this post helpful.

The reason why SARPi uses the 4.14.x kernel is mainly because of this reason: https://www.raspberrypi.org/forums/v...06400#p1279141

1 members found this post helpful.

drmozes, Penthux, thank you both!