$ sudo dpkg --add-architecture armhf
$ sudo add-apt-repository ppa:ubuntu-raspi2/ppa
$ sudo perl -pi -e 's/eoan/bionic' /etc/apt/sources.list.d/ubuntu-raspi2-ubuntu-ppa-eoan.list
$ sudo apt update
$ sudo apt install libraspberrypi-bin:armhf
$ git clone https://github.com/raspberrypi/rpi-eeprom
$ cd rpi-eeprom
$ cat > from-ubuntu <<EOF
# Seems to want the vl805 executable from within $FIRMWARE_ROOT to be in the
. $(pwd)/rpi-eeprom-update "$@"
$ sudo ./from-ubuntu -a
*** INSTALLING EEPROM UPDATES ***
BOOTLOADER: update required
CURRENT: Fri May 10 18:40:36 UTC 2019 (1557513636)
LATEST: Mon Nov 18 11:06:55 UTC 2019 (1574075215)
VL805: update required
EEPROM updates pending. Please reboot to apply the update.
You need the following files from https://github.com/raspberrypi/rpi-eeprom/tree/master/firmwa...:
* One of the pieeprom files. Rename it to pieeprom.upd
* One of the vl805 files. Rename it to vl805.bin
* Generate the SHA256 sums of both files and place them in pieeprom.sig and vl805.sig
The key here is the name of the pieeprom.upd file. You can also name it pieeprom.bin, but in that case the recovery.bin isn't renaming itself and you'll have to manually delete the files from the SD card.
Another thing I haven't tried yet is the network/USB booting support in the beta firmware. It doesn't help you with the initial upgrade of course, but once you've done that it gives you two more alternatives to the second microSD card.
 https://www.raspberrypi.org/documentation/hardware/raspberry... says "The current schedule is to release network boot first, then USB boot."
I updated 4 RPi4's recently by just inserting the card; renaming recovery.000 to recovery.bin; and repeating for each device.
As an aside, the reality is that the Raspberry Pi is not a particularly speedy computer even when not thermally throttled. It is close in non-graphics performance to x86 computers from the 2000s. Though using only 5W to do that is a huge improvement; that was the era when CPU heatsinks started getting so big they broke the CPU socket off the motherboard ;)
There are some clear improvements.
“What is the raspberry pi? What defines it? What is its purpose,place and soul?”
Is it to be a hot machine that requires thermal management or is it something else?
Leaving mine overnight, while running a few server applications mostly idling. In my room it hit an equilibrium temperature of 53C. If I recall correctly, without running anything at all, Raspbian would hit over 50C. This was back in August.
I heard conflicting reports from other people - that their Pi was idling in the same case at 35-40C. The thing is, as far as I was able to determine, they were all reporting the temperature of the Pi within a few minutes of a cold boot. This doesn't make sense because the Pi takes time to reach equilibrium, especially with a case.
Right now, having been idling in the heatsink case for over 24 hours, my Pi is at 45C. That suggests a maximum of about 5C improvement on idle since August. (Probably less though, it's a few degrees colder in this room than it was in August.)
To be clear, they don't even report idle CPU temperatures anywhere as far as I can tell (other than implicitly in the thermal camera pictures), so they're not lying about anything. But it would be nice to see what "idle" is supposed to mean specified more clearly in benchmarks like these.
Nice work, guys!
The long-term outcome should have been 1GHz, not 600MHz, in most of the plots. The Pi jumps back-and-forth between 1GHz and 1.5GHz until it overheats, and then throttles all the way down.
The vertical orientation made a small difference in temperature but a huge difference in how long the Pi took to throttle precisely because of poor clocking schedule.
Unless it's also doing other stuff (e.g. shutting down cores), 1GHz isn't a huge throttle.
Everything runs fine at these temperatures, but all of the ports are hot to the touch. Under stress the SoC seems to reach 80C+, which I imagine would make connecting and disconnecting USB devices a fairly unpleasant experience.
Not sure if this was before or after these fw updates but it was two weeks ago on stable raspbian. I don’t actively monitor the temp as it is remote.
> Compilation finished in 5097 seconds – one hour, 24 minutes, and 57 seconds.
> Compilation finished in 2660 seconds – 44 minutes and 20 seconds.
It went ok the last few years as at least the CPU improves as the foundation makes an effort to release new SoC revision with updated ARM cores.
However the GPU is in a dead end since quite some time and most likely this will never change.
The actual HW didn't change much and the reason is because they got all fired.  I will give you a few links but this happened in 2014/2015 so it's not so easy to find a lot of relevant things (James who commented in the forum worked for them):
Edit: Back then I was a bit involved into QPU programming with the assembler which was written based on the open source documentation of the VC4. That's why I have seen all this discussion.  I doubt that Broadcom has done much more then maintenance on the GPU IP in the last few years because Raspberry Pi are their only customers.