Add links to firmware and rpi-eeprom repos #4130
Conversation
| * https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README[Device tree overlay README] | ||
|
|
||
| https://github.com/raspberrypi/rpi-eeprom:: | ||
| Installation scripts and binaries for the Raspberry Pi 4 and Raspberry Pi 5 bootloader EEPROMs including the https://github.com/raspberrypi/rpi-eeprom/releases[releases] |
There was a problem hiding this comment.
Instead of the github Releases page, I use the page at https://github.com/raspberrypi/rpi-eeprom/blob/master/releases.md to access release notes for the EEPROM firmware for BCM2711 and BCM2712-based devices separately. The releases for 2711-based devices don't say '2711' anywhere in the name of each release, and are mixed in with the 2712 releases on the github Releases page, so it's harder to keep track of which release is for which device family (i.e. 2711 versus 2712-based).
| @@ -46,6 +46,14 @@ The following is a curated list of repositories which most people are interested | |||
| https://github.com/raspberrypi/linux:: | |||
| This repository contains the source code for the downstream Linux kernel supported and working on all versions of Raspberry Pi from Pi 1 to Pi 5. | |||
|
|
|||
| https://github.com/raspberrypi/firmware:: | |||
| This repository contains the closed source firmware, although the following two links are useful: | |||
There was a problem hiding this comment.
I think this repo supplies the data for rpi-update? It might be worth adding something along those lines to give a better understanding of what the repo is actually for.
There was a problem hiding this comment.
Nah, rpi-update gets its data from https://github.com/raspberrypi/rpi-firmware
There used to be a big difference between what's in https://github.com/raspberrypi/firmware and what's in https://github.com/raspberrypi/rpi-firmware (the latter used to also contain a bunch of files from the old userland repo), but these days the difference is much smaller.
There was a problem hiding this comment.
Perhaps you could add a statement to the rpi-firmware repo's readme that states explicitly that it is the repo that rpi-update fetches firmware and kernel from?
No description provided.