diff options
| author | Stijn Tintel <stijn@linux-ipv6.be> | 2020-06-07 09:18:39 +0300 |
|---|---|---|
| committer | Stijn Tintel <stijn@linux-ipv6.be> | 2020-06-07 10:25:50 +0300 |
| commit | afdc413d9d8103c4cc96a3b8e33292b814b12782 (patch) | |
| tree | 014e86a6d00b5ecfa2cfda5f8901a542d0a5313f /.github | |
| parent | 050c31fa268461fbc0a61dc04eda1424c5542151 (diff) | |
| download | upstream-afdc413d9d8103c4cc96a3b8e33292b814b12782.tar.gz upstream-afdc413d9d8103c4cc96a3b8e33292b814b12782.tar.bz2 upstream-afdc413d9d8103c4cc96a3b8e33292b814b12782.zip | |
Revert "bcm27xx-gpu-fw: update to latest version"
This reverts commit 9e467a764b4e30a04dd0431ea277f6acd26babe0.
The Raspberry Pi firmware recently switched to building from the common
firmware branch. This introduces changes in the core clock handling,
causing various issues.
E.g. enable_uart=1 no longer fixes the core clock frequency to 250MHz.
When the disable-bt DT overlay is not loaded, the core clock frequency
is increased to 400MHz. As a result, the UART baud rate is no longer
correct, and this causes garbled serial console, or communication
problems with HATs that use the UART.
As a workaround, the core clock could be fixed to 250MHz by adding
'core_freq=250' in /boot/config.txt, but as there appear to be other
issues than just the UART being broken, the safer bet is to revert the
firmware for now.
Upstream bug: https://github.com/raspberrypi/firmware/issues/1376
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Acked-by: Álvaro Fernández Rojas <noltari@gmail.com>
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions