Re: RPi4B: modern firmware vs. Device tree loaded to 0x4000 (size 0xbe0c) [fails] vs. to 0x1f0000 (size 0xbd90) [works]?
Mark Murray <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
Hi folks, > On 11 Oct 2020, at 14:17, Klaus Cucinauomo via freebsd-arm <[email protected]> wrote: > > > >> Am 11.10.2020 um 15:11 schrieb Robert Crowston <[email protected]>: >> >>> That’s the problem, armstub8-gic should have been removed when using modern firmware because it no longer depends on it. >> >> So are you telling me that I could rip out all the startup logic from the armstub and just leave our CPU spin up logic? >> >> — RHC. > > yes, exactly, even : > $rm /Volumes/MSDOSBOOT/armstub8-gic.bin > > ( while I wouldn't swear that the initialization of your pcie driver from fdt will continue to run smoothly in the boot-process directly from SSD, > I expect necessary adjustments..) I'm watching progress with a very interested half-an-eye. There seems to be a lot of progress in understanding the RPI4B+, which excites me a lot! Is there a single summary/script/blog that I could go to to get up to speed with you all, please? Keep it up! :-) M --
signature.asc
(application/pgp-signature, 556 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 Comment: GPGTools - http://gpgtools.org iQEzBAEBCgAdFiEEyzPHvybPbOpU9MCxQlsJDh9CUqAFAl+DByEACgkQQlsJDh9C UqBahgf/YGouRYVqgxeUhsHftD5L84dYS1i6ED8mEVQP6TX882qfAToG2L6mp02P lbgmJZzsnfI2eVUpqZINl1ymqwOGCuFnWGKUr2EpuICjzGuAIOirWpkmwo6rWYj5 evSyhr95Wn1JPaUlFk9GLOQVhV1bU/ClLgUrSFhRL9f3dM8tq39tcVw3qemKVCLO pgLNpwMSOBcGMIGFTbDVJZqo3jRLUqcAQocgyVje3uKaaK6pv5uJbJ9SY/mhkjA0 HsXbmjJDODBqtgS0d7Exc1MmD9nPRWmrLVvg5eTvqZHYsSQRiYtR5q6Du9oHccEh 4IpBmUMelUheSpWglsesI1qqhh40zA== =mnnx -----END PGP SIGNATURE-----