Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 599934 - sys-boot/raspberrypi-firmware-1.20161020 et all bump request
Summary: sys-boot/raspberrypi-firmware-1.20161020 et all bump request
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords: PMASKED
Depends on:
Blocks:
 
Reported: 2016-11-16 01:45 UTC by Ian Leonard
Modified: 2019-03-24 19:37 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Leonard 2016-11-16 01:45:35 UTC 
This is a request to version bump raspberrypi-firmware, raspberrypi-image, and raspberrypi-userland-bin to 1.20161020.

Raspberrypi-image is likely vulnerable to DirtyCOW (CVE-2016-5195). Upstream released a new image in response. The new image needs new firmware to boot. Userland-bin should match the firmware.

I version bumped the 3 packages, just changing the version number to 20161020 where relevant, and adding the ".tar.gz" ending to the raspberrypi-image packagename for download.

Note if using the Raspberry Pi's hardware RNG, the module name changed from bcm2708_rng to bcm2835_rng, at least for the 1st gen Pi.
Comment 1 David Flogeras 2017-03-28 21:26:50 UTC 
Bump, could we get a recent version?  I hit a bug with the RPi sources now that they are based on 4.9.y kernel, which requires recent firmware files to work correctly with device trees (specifically 1wire-gpio in my case).
Comment 2 tt_1 2017-09-12 22:11:14 UTC 
At the moment one has to use the live ebuild, or in case not having a fast internet connection, download a recent relase from their github and extract the files accordingly to what is written in the ebuild + the config files. The default kernel won't boot with the 2016 something firmware, nada.