rpi5b: drop LINUXFAMILY=bcm2712 as it is exactly the same as bcm2711

[rpardini]

rpi5b: drop LINUXFAMILY=bcm2712 as it is exactly the same as bcm2711

• rpi5b: drop LINUXFAMILY=bcm2712 as it is exactly the same as bcm2711
  • in f3f10a9 the 16k-page stuff was dropped
    • and that was the only reason for a separate kernel
    • thus drop the change and unify; 2 less kernels to build and same result

[pyavitz]

The problem if I recall correctly? had something to do with the armbian-ramlog service making the unit run wonky. The unit would freeze up, not reboot, apt upgrade didn't work. Stuff like this... The only solution found at the time was disabling the service.

So it was decided to drop 16K.

[rpardini]

Yeah that makes sense, thanks for the context.

In practice, changing the LINUXFAMILY (with no other changes) just forces a separate kernel build and .deb's to be created (and since both current and edge are enabled, 2x)

[pyavitz]

Yeah that makes sense, thanks for the context.

In practice, changing the LINUXFAMILY (with no other changes) just forces a separate kernel build and .deb's to be created (and since both current and edge are enabled, 2x)

The idea at the time was that a solution would present itself. Since no one has complained about it and the behaviour hasn't occurred since, it has been forgotten about.

#6461

[igorpecovnik]

What to do here? Proceed with merging?

[rpardini]

It's 2 less kernels/.debs to build, with exactly the same result, so I'd say we can merge.