Date: Mon, 8 Mar 2021 10:56:15 -0800 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: RPi4 Status and xorg behavior Message-ID: <4D8FD8EE-6642-46ED-8AAE-CAECB36572F6@yahoo.com> In-Reply-To: <20210308173045.GB13739@www.zefox.net> References: <BDF8C846-1CB3-421E-A8D5-25E0075C7106@yahoo.com> <20210307021628.GA99890@www.zefox.net> <AAA4E495-4E9E-4C55-A07E-74D9737EC15B@yahoo.com> <20210307155515.GA4591@www.zefox.net> <67BF2EAC-04AD-4822-99B2-48A99563331F@yahoo.com> <G5ZAfvg49jl5dj40HAnjmwoEKpVSuGp8KmiBrSY_EBLXou6UGBIjU3tVxUuPGKeCvXEovg2d3tqhIGOmQCyb7c3wKsUHJ8xrSasvwXfbqwk=@protonmail.com> <4B963C56-D7E9-42FE-8B8B-B8A425ACE78F@yahoo.com> <20210308011035.GA6603@www.zefox.net> <DB3CD5BA-337E-476F-9F0C-C70401F7D800@yahoo.com> <C500EE5B-B483-4580-8C7C-9B9B013D726B@googlemail.com> <20210308173045.GB13739@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Mar-8, at 09:30, bob prohaska <fbsd at www.zefox.net> wrote: > On Mon, Mar 08, 2021 at 02:40:06PM +0100, Klaus K??chemann wrote: >>=20 >>=20 >>=20 >> it would also help to be explicit about the firmware-version. >> I would suggest to base tests on - 1.20210303. - , as it should then = be the >> latest in the next build , IIRC. >>=20 > Is there some way to check it from FreeBSD? The machine usually > runs RaspiOS and was updated yesterday, so I'd expect the firmware > to be reasonably current but can't be certain. Summary for current context: (The below presumes that the msdosfs file system involved is mounted on /boot/efi . Adjust as needed for your context.) # strings /boot/efi/start4.elf | grep VC_BUILD_ID_ VC_BUILD_ID_USER: dom VC_BUILD_ID_TIME: 12:10:40 VC_BUILD_ID_VARIANT: start VC_BUILD_ID_TIME: Feb 25 2021 VC_BUILD_ID_BRANCH: bcm2711_2 VC_BUILD_ID_HOSTNAME: buildbot VC_BUILD_ID_PLATFORM: raspberrypi_linux VC_BUILD_ID_VERSION: 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean) That strings and grep can be used locally to see if the start4.elf matches the above. fixup4.dat *.dtb's and such do not seem to contain such identification information. Full checking requires getting a full copy and diffing the result (or just replacing). But if one has been careful to not mix and match files, the above should be a good cross check. More generally, the below is how I figured out the above text for the current example. . . Treating this as an example of a more general process, starting from: https://github.com/raspberrypi/firmware/commits/1.20210303 clicking on the first <> on the right gets to: = https://github.com/raspberrypi/firmware/tree/fcf8d2f7639ad8d0330db9c8db9b7= 1bd33eaaa28 clicking on boot gets to: = https://github.com/raspberrypi/firmware/tree/fcf8d2f7639ad8d0330db9c8db9b7= 1bd33eaaa28/boot clicking on start4.elf gets to a page with a Download button: clicking on Download (or copy link for Download and use of it) gets a copy of the start4.elf . The URL was: = https://github.com/raspberrypi/firmware/raw/fcf8d2f7639ad8d0330db9c8db9b71= bd33eaaa28/boot/start4.elf Then this file's content shows: # strings start4.elf | grep VC_BUILD_ID_ VC_BUILD_ID_USER: dom VC_BUILD_ID_TIME: 12:10:40 VC_BUILD_ID_VARIANT: start VC_BUILD_ID_TIME: Feb 25 2021 VC_BUILD_ID_BRANCH: bcm2711_2 VC_BUILD_ID_HOSTNAME: buildbot VC_BUILD_ID_PLATFORM: raspberrypi_linux VC_BUILD_ID_VERSION: 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean) and that type strings and grep use can be used on /boot/efi/start4.elf to see if the start4.elf matches. (Wording presumes the /boot/efi/ mount point. Vary as needed.) I will note that VC_BUILD_ID_VERSION is not from the public github server space. It seems to be from a non-pubic internal one, possibly the source code git repository. So do not expect to match it with github hash-ids for commits of binary materials. I will note that: https://github.com/raspberrypi/firmware/commits/master shows two commits on Mar 5 2021 that are after the 1.20210303 tagged material, as well as older activity: Commits on Mar 5, 2021 =E2=80=A2 firmware: hdmi_2711: Rework I2C driver to NOT use the = AUTO-I2C block =E2=80=A6 popcornmix committed 3 days ago 1711f63=20 =E2=80=A2 kernel: Bump to 5.10.20 =E2=80=A6 popcornmix committed 3 days ago 530cfdd=20 Commits on Feb 25, 2021 =E2=80=A2 firmware: arm_loader: Return all borrowed DMA channels = =E2=80=A6 popcornmix committed 11 days ago 5985247=20 Commits on Feb 24, 2021 =E2=80=A2 firmware: platform: vl805: Get BAR2 address from PCIe = BAR2 registers popcornmix committed 12 days ago 7872272=20 Commits on Feb 22, 2021 =E2=80=A2 kernel: Bump to 5.10.17 =E2=80=A6 popcornmix committed 14 days ago . . . =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?4D8FD8EE-6642-46ED-8AAE-CAECB36572F6>