There is an updated pull request by Piraty against master on the void-packages repository https://github.com/Piraty/void-packages rpi-kernel-split https://github.com/void-linux/void-packages/pull/29139 [NOMERGE] rpi-kernel: split into rpi, rpi2, rpi3, add rpi4 This is my second approach to the rpi4 problem (first try: https://github.com/void-linux/void-packages/pull/26000) The problem is: how to not break existing systems while having a consistent naming scheme for rpi-kernel / rpi-base. As ~demanded~ suggested by @the-maldridge , `rpi-kernel` continues to provide the kernel for rpi0/rpi1 and becomes a meta package that pulls `rpi{2,3}-kernel` (based on target arch) so legacy pull the new update systems. This may be optional though and we could require users to manually install the new kernel package, possibly posting a new post on the website for that. To support legacy systems, rpi-base is split into rpiN-base which all ship the same udev rule and depend on the respective kernel. This (still) allows to have a single entry-point to raspberry related packages. I performed (offline) testing of the package transition process, seems fine. Script [here](https://gist.github.com/Piraty/2b0bd709c58ca2e8dd2240cc5b1141c9) ### How to 1. checkout this branch 2. build one of `rpi4-base` (aarch64*) or `rpi-base` (`armv6*`, `armv7l*` or `aarch64*`) 3. update your pi with the new packages or build fresh images: see https://github.com/void-linux/void-mklive/pull/153 --- @pbui @Duncaen @ahesford A patch file from https://github.com/void-linux/void-packages/pull/29139.patch is attached