Date: Wed, 14 Oct 2020 07:34:09 +0200 From: Klaus Cucinauomo <maciphone2@googlemail.com> To: Mark Millard <marklmi@yahoo.com>, freebsd-arm@freebsd.org Subject: Re: 64-bit RPi4B u-boot hangup with modern rpi firmware: some information (but investigative-toolbox limited) Message-ID: <D63E3FD9-72AD-4C61-BBA6-323D8FCA5775@googlemail.com> In-Reply-To: <F439DCA4-481E-4918-9ED4-2D9ECB2DD03F@yahoo.com> References: <290E51C0-0AF5-4C75-AA7B-BA56DF1AFDFB.ref@yahoo.com> <290E51C0-0AF5-4C75-AA7B-BA56DF1AFDFB@yahoo.com> <4114B1A0-03ED-4268-BA87-8CF196A935A4@googlemail.com> <F439DCA4-481E-4918-9ED4-2D9ECB2DD03F@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 14.10.2020 um 06:43 schrieb Mark Millard <marklmi@yahoo.com>: >=20 >> =E2=80=A6... >=20 > By contrast, what I've done can > not even show that u-boot ever was started after it was loaded=E2=80=A6 I showed that even FreeBSD was started by u-boot with the modernFirmware = loaded (when the armstubs are NOT loaded) : https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5702 That finding is of course not a bugfix in the armstub but enough to say: = u-boot(at least that version shown in dmesg) doesn`t hang up with the = modernFirmware=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D63E3FD9-72AD-4C61-BBA6-323D8FCA5775>