Date: Mon, 3 Feb 2025 21:22:59 +0100 From: Klaus Cucinauomo <maciphone2@googlemail.com> To: Mark Millard <marklmi@yahoo.com>, Ronald Klop <ronald-lists@klop.ws>, freebsd-arm@freebsd.org Subject: Re: RPI5 16GB panic on boot Message-ID: <968FEC88-04F3-45E0-B6AC-77029AB3BFC2@googlemail.com> In-Reply-To: <19B2FAF2-4656-4D0D-B8D4-713BFCC75372@yahoo.com> References: <19B2FAF2-4656-4D0D-B8D4-713BFCC75372@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mark, I hope you`re well=E2=80=A6. > Am 03.02.2025 um 20:05 schrieb Mark Millard <marklmi@yahoo.com>: >=20 > it could probably be used > to get a textual "print" (serial console capture) of the device > tree that it hands off. with Ronald`s help we could e.g build an independent(experimental) Port=20 of u-boot(-rpi-arm64) which follows current upstream-patches . This would make sense for driver developers (although we don`t have much of t= hem here;-) to start working =E2=80=A6. manu@ will not accept any =E2=80=9Ewild hacks=E2=80=9C which are not pristin= e upstreamed, for good reason. But since bcm2712 bootloader support is in development we should not stay =E2= =80=9Elightyears behind=E2=80=9C=E2=80=A6=20 So what I want to say is: currently integrating dts-files and document it instead of reading .dtb fil= es is what would really help. However,=20 since I`m currently using the emmc of the cm5 I would be very interested=20= in yours uboot`s-logs from RPI5b-machines. Regards K.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?968FEC88-04F3-45E0-B6AC-77029AB3BFC2>