Re: 64-bit RPi4B u-boot hangup with modern rpi firmware: some information (but investigative-toolbox limited)
Mark Millard via freebsd-arm <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
On 2020-Oct-15, at 02:52, Robert Crowston <crowston at protonmail.com> wrote: > My suspicion is that the latest firmware is interfering with a block of memory somewhere above the 0x0, that we and others are relying on being able to use or having some content. There were multiple issues for firmware commits after the 2020-07-17 firmware commits (either place's copies). The good 2020-07-17 materials were from: https://github.com/raspberrypi/firmware/commits/542aceb and: https://github.com/Hexxeh/rpi-firmware/commits/7059841 A big issue over much of the recent time was that the firmware was handling over corrupted Device Tree content. This is one thing covered by the fix released today: https://github.com/raspberrypi/firmware/commits/2d83e2c and: https://github.com/Hexxeh/rpi-firmware/commits/98d9079 uefi/ACPI and fedora (no armstub*.bin use, uses u-boot and grub2) were also seeing problems with the firmware from commits after the 2020-07-17 commits. The problems were not specific to the armstub*.bin files that FreeBSD uses. If I understand right, the serial console baud rate change problem seen on, for example, RPi3*'s is still an issue. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "[email protected]"