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 | <OrVZo1i7_mab5U20umZB8WNvrJEesT6yMPL8uzg-FKbcppGvLJEOPZqW_XIs3iyoqvmcQ9OA2oLJpBGU0FEc0kFi387k9v9DzMcwSDzZhfY=@protonmail.com> |
What problem does it cause? You’ve described it as incompatible, but what does that mean? If it isn’t used, why did the RPi foundation update the armstub source code only 3 days ago? — RHC. On Sun, Oct 11, 2020 at 20:46, Klaus Cucinauomo <[email protected]> wrote: >> Am 11.10.2020 um 21:37 schrieb Mark Millard <[email protected]>: >> >> MESS:00:00:20.241899:0: brfs: File read: /mfs/sd/armstub8-gic.bin >> MESS:00:00:20.244930:0: Loading 'armstub8-gic.bin' to 0x0 size 0x1700 > > You have to DELETE the armstub from the MSDOS-partition, > it loads automatically if available. > Regards > K. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "[email protected]"