There is a github repo that has details of the changes.
Ref: https://www.raspberrypi.org/forums/view ... 8#p1520896When its done it will be broadly announced in the blog.
It also won't be enabled via sudo apt upgrade, since it requires an upgraded EEPROM firmware. They've said already that for EEPROM updates these will need to be applied using a different procedure. No EEPROM updates have been released yet, and they have not announced what tool will be used to perform those updates.B.Goode wrote: ↑Mon Aug 19, 2019 10:06 pm
This statement from a Moderator as recently as two days ago, in response to the question "When can we expect USB boot for the Pi 4? " seems relevant...Ref: https://www.raspberrypi.org/forums/view ... 8#p1520896When its done it will be broadly announced in the blog.
There is an Pi 4 bootcode EEPROM update but it is still a release candidate.
The current method is via the bootcode EEPROM recovery system that runs recovery.bin from the card at startup. The problem with this is that you need to physically remove the card afterwards to delete recovery.bin as it halts after the update so you can't do it from Linux.
I am not sure exactly what components "rpi-bootloader" consists of but that is not the code which runs in the Pi 4B Boot Eeprom.
I don't see why it couldn't be. I can see no reason there could not be a completely automated Boot Eeprom upgrade process
I agree but the restriction isn't for technical reasons. They don't want to force an update for people who don't need one. Plans may have changed now though.
The configuration options are included in the binary. If you are not satisfied with the default settings (old and/or new ones), currently the upgrade process is requiring some manual sed commands. So there is a pre-customization on the EEPROM. But sure, some of the settings can be read from the current bootloader, and the users can be asked about the new ones. However, there is no silent, completely automated upgrade option.
Not at present, no. But there could be, and hopefully will be, in the future. I can also understand why they currently aren't forcing firmware upgrades on people when there's not a complete framework for Boot Eeprom upgrades in place yet.
This is also that I read from the blog: a new procedure to update the eeprom firmware. However here and there on the forum I can see people telling to use rpi-update on the Pi4. Since rpi-update is a firmware update tool is this a nonsense or what?
Different firmware. rpi-update updates the firmware and kernel in /boot. For all older Pi boards, that was the only firmware. The Pi 4 added an EEPROM to store bootcode.bin on the Pi itself and an EEPROM to store the USB controller firmware. rpi-update doesn't touch either of those.
Probably nonsense. There is a lot of confusion over what "firmware" is on the Pi.