Are you at least on the RPi payroll?
>The firmware blob on the Pi5 (and now earlier models as well) does very little.
There is not just one proprietary program - there are several.
As per README.md as I linked - there are several proprietary programs (or proprietary patches); start*.elf, fixup*.dat and bootcode.bin
cd boot ; ls -lah start*.elf fixup*.dat bootcode.bin | awk '{print $5 " " $9}'
52K bootcode.bin
3.2K fixup4cd.dat
5.4K fixup4.dat
8.3K fixup4db.dat
8.3K fixup4x.dat
3.2K fixup_cd.dat
7.2K fixup.dat
11K fixup_db.dat
11K fixup_x.dat
827K start4cd.elf
3.7M start4db.elf
2.2M start4.elf
3.0M start4x.elf
827K start_cd.elf
4.7M start_db.elf
2.9M start.elf
3.6M start_x.elf
There's even a few copies of a proprietary version of Linux there; kernel_2712.img, kernel7.img, kernel7l.img, kernel8.img, kernel8_rt.img, kernel.img and the proprietary software couldn't be anything but a derivative work of Linux (it doesn't boot or interface with anything else) and therefore intentional GPLv2 infringement is occurring (but of course the Linux developers are happy for the users freedom to be taken in that way).
~22MiB is quite a lot of proprietary software, which certainly doesn't do very little (although certain programs are only for certain Pi's).
4.7MiB of proprietary OS that uses threadx can do and does quite a lot; strings start*.elf |grep threadx
Apparently the RPi5 doesn't use that version of such software and instead the relevant version is included in the SPI flash instead - but I'd bet that the programs stored on the SPI flash are larger than the relevant files for the RPi4; https://forums.raspberrypi.com/viewtopic.php?t=373222
>Nowadays, it's really just thermal control and boot, it's there to get the system up and running, and to make sure the SoC doesn't overheat.
A free version of u-boot could get the system init'd just fine - but Broadcom says no.
Thermal control can and must be done with free software.
>Most of what used to be in the firmware (you know, 12 years ago) is now all open source Arm side code (3D, codec, cameras, display etc)
"open source" misses the point.
"most" is not "all".
It doesn't seem "most" is correct - rather "little" seems more correct.
>Pi have put a lot of effort into getting as much out of the firmware and open-sourced as possible.
As far as I can tell, the RPi's have only gotten more proprietary, as for any function moved into a source-available driver, the size of the proprietary software has increased as well?
As the correct amount of proprietary software is 0 - it is totally unacceptable that RPi has increased the amount of proprietary software.
>This is a good thing and means if Linux (or its own thernal control) crashes, the firmware can still stop the device overheating.
Wow, proprietary software is a good thing?
Overheating protection must not only be implemented in any software if you don't want the hardware to fail from overheating - rather the hardware should contain a function that responds to overheating by throttling and triggers a reset if excessive overheating still occurs (AMD64 CPUs do that).
Such hardware safety feature means it doesn't matter if any of the thermal control software crashes or is bugged - as the device will just go and reset itself (which would automatically deal with the overheating, as crashed-on-a-loop software would stop running).
If overheating is a concern, clearly the device needs cooling fans and the free software fancontrol can handle PWM fans no problem.
>your comment on Debian, is, well, a bit weird.
It's not weird at all as Debian is proprietary software now - the installer contains proprietary software and goes and permanently installs it without asking the user or telling them what was installed!