Date: Sun, 6 Jun 2021 11:24:39 -0700 From: Mark Millard via freebsd-arm <freebsd-arm@freebsd.org> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: Strange u-boot behavior Message-ID: <39531089-701F-4A5C-B60E-0D9262DF8B78@yahoo.com> In-Reply-To: <20210606160040.GA97697@www.zefox.net> References: <20210606043152.GA94545@www.zefox.net> <27786296-8C55-4CEC-A587-14BF4465A4F8@yahoo.com> <20210606160040.GA97697@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Jun-6, at 09:00, bob prohaska <fbsd at www.zefox.net> wrote: >> . . . >=20 > I'm seeing lots of=20 > MESS:00:00:01.300591:0: hdmi: HDMI:EDID error reading EDID block 0 = attempt...=20 > errors from u-boot. Up to now they didn't seem to matter.=20 >=20 FYI: The "MESS:" lines are from before U-Boot has been loaded by the RPi firmware. They start even before the firmware loads the .dtb --but after start*.elf is started, so after it and the matching fixup*.dat are loaded. U-Boot is not involved for these HDMI:EDID messages. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39531089-701F-4A5C-B60E-0D9262DF8B78>