That means when common bug fixes or new features are added they need to be cherry-picked to each tree.
This can get overlooked and bugs we believe were fixed on Pi4 can be found to be present on earlier Pi models.
We've long had a goal to switch to the newer tree for everything and would like to get moving forward.
We've been running for a while regression tests on older Pi models using the new tree and they are passing.
But it's basic testing - we'd like to get more users helping.
The "master" branch of rpi-update is now being built from the new tree. You can update to this with:
Code: Select all
If you are on an earlier model, then you'll now be running different firmware code. Ideally everything that used to work will continue to do so.
We'd like volunteers to try this. As there could be bugs, then only run on a non-critical install, or one with a recent backup.
The main areas of change relate to clocks and voltages, hardware (usb/ethernet/HATs), the fkms driver.
Testing on older models is most useful (Pi0, Pi1, Pi2, Pi3, CM). A sanity check that Pi4 still works is also helpful.
Just test what you normally use the Pi for. Let us know if you have any custom hardware (HATs) or custom config.txt settings (e.g. overclock).
If it all works, let us know. If you spot any regression compared to your previous firmware, then let us know.
As usual, if testing is positive the firmware will move from next branch to master branch of rpi-update and later to apt.
EDIT: Common firmware is now on the master branch of rpi-update. next branch is still being used for 5.4 kernel testing.