Skip to content
Firmware files for the Raspberry Pi
C C++ Other
Find file
Failed to load latest commit information.
modules kernel: Rebuild with dtb that uses mmc sdcard driver
overlays kernel: Rebuild with dtb that uses mmc sdcard driver
vc kernel: Bump to 4.1.17
COPYING.linux Rebuild with PAL resolution fix.
LICENCE.broadcom licence: Add Raspberry Pi copyright
Module.symvers kernel: Bump to 4.1.17
Module7.symvers kernel: Bump to 4.1.17
NOTICE.md notice: Downgrade the warning to notice as 4.1 kernel is considered s…
README.md Fixed a typo.
bcm2708-rpi-b-plus.dtb kernel: Rebuild with dtb that uses mmc sdcard driver
bcm2708-rpi-b.dtb kernel: Rebuild with dtb that uses mmc sdcard driver
bcm2708-rpi-cm.dtb kernel: Rebuild with dtb that uses mmc sdcard driver
bcm2709-rpi-2-b.dtb kernel: Rebuild with dtb that uses mmc sdcard driver
bootcode.bin kernel: Bump to 4.1.17
fixup.dat firmware: video_render: Support non-default vertical stride
fixup_cd.dat kernel: Bump to 4.1.17
fixup_db.dat firmware: video_render: Support non-default vertical stride
fixup_x.dat firmware: video_render: Support non-default vertical stride
git_hash kernel: Rebuild with dtb that uses mmc sdcard driver
kernel.img kernel: Rebuild with dtb that uses mmc sdcard driver
kernel7.img kernel: Rebuild with dtb that uses mmc sdcard driver
start.elf firmware: video_render: Support non-default vertical stride
start_cd.elf firmware: video_render: Support non-default vertical stride
start_db.elf firmware: video_render: Support non-default vertical stride
start_x.elf firmware: video_render: Support non-default vertical stride

README.md

rpi-firmware

Firmware files for the Raspberry Pi. These are mirrored in a seperate repo from the official one, because for updating the firmware, we're only interested in the files in the boot folder of the official repo. Git doesn't provide a way to clone only a single subfolder of a repo, and downloading the entire repo including the sample code and VC libs would take too long.

If the boot firmware files are split off into a seperate repo, then the tool could be pointed at that repo instead of this one, as long as the firmware files are in the root of the repo.

Something went wrong with that request. Please try again.