Re: RPi4B: modern firmware vs. Device tree loaded to 0x4000 (size 0xbe0c) [fails] vs. to 0x1f0000 (size 0xbd90) [works]?
Robert Crowston via freebsd-arm <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <KSZxiPnKfwb4gGW77I3QVM3vobwI6gTW7OdZ7KqhEh21H0y0cu3RW4mG7HYAz9fEeVv7oI1vuLtf7ToOZdvrEWvi_oZnDFbLk-B3z7MFJhI=@protonmail.com> |
We have a patched version of armstub8-gic. We use it to install some code in a highly privileged context that we later call from supervisor mode to start the secondary CPUs. Linux uses a different approach to spin up the other CPUs. I haven’t followed this thread in huge detail, but it seems like the raspberry pi people changed everything again? On Sun, Oct 11, 2020 at 01:21, Klaus Cucinauomo <[email protected]> wrote: >> Am 10.10.2020 um 08:53 schrieb Mark Millard <[email protected]>: >> >> ….. a lot…. >> > > ...yes, very good catch and absolutely true …. > you can avoid the rainbow-hang in u-boot 2020.10 with a brutal : > -------$ rm /Volumes/MSDOSBOOT/armstub8-gic.bin------- > modern firmware of https://github.com/raspberrypi/firmware/tree/master/boot > should no longer depend on armstub8(-gic).bin, > that’s why it is removed in ubuntu. > > but for some reason we will now panic in : > — > Starting CPU 1 (1) > panic: No PSCI/SMCCC call function set > — > the reason seems to be here : > https://kernelnomicon.org/?p=718 > > Regards > K. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "[email protected]"