4a02207f57
Until now, rpi-kernel served rpi0/rpi1 + rpi2 + rpi3 all at once. The variants were solely distiguished by the target architecture; it was nice while it lasted, but now that rpi4 is on its way, we need to split things up a little. With the split, * rpi-kernel serves rpi0 + rpi1, armv6l* only * rpi2-kernel serves rpi2, armv7l* only * rpi3-kernel serves rpi3, aarch64* only To help migrate existing devices to the new kernel packages, rpi-kernel will be an empty mega package for !armv6l* and depend on rpi2-kernel or rpi3-kernel (depending on target architecture) for the foreseeable future, thus resolving like this: * rpi-kernel -> rpi2-kernel (armv7l*) * rpi-kernel -> rpi3-kernel (aarch64*) Relates to: #29139 Acked-by: Duncaen <duncaen@voidlinux.org>
Symbolic link
1 line
11 B
Plaintext
Symbolic link
1 line
11 B
Plaintext
rpi3-kernel |