Date: Sat, 17 Apr 2021 20:04:26 -0700 From: Mark Millard <marklmi@yahoo.com> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-arm@freebsd.org Subject: Re: RPi4B 2711ZPKFSB06C0T parts seen in the wild, 13.0-RELEASE fails to boot on them Message-ID: <39AB95E8-AC86-465C-94E6-C2B8040EB45D@yahoo.com> In-Reply-To: <YHuctG7HFHedRo0P@ceres.zyxst.net> References: <05740E83-5A45-4944-AC87-629D21D7F579.ref@yahoo.com> <05740E83-5A45-4944-AC87-629D21D7F579@yahoo.com> <YHuctG7HFHedRo0P@ceres.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Apr-17, at 19:43, tech-lists <tech-lists at zyxst.net> wrote: > On Sat, Apr 17, 2021 at 11:08:31AM -0700, Mark Millard via freebsd-arm = wrote: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255080 >>=20 >> comment #5 reports a comparison/contrast of 4 GiByte >> RPi4B's with: >>=20 >> BROADCOM >> 2711ZPKFSB06BOT >> TE1919 >> 045-23 B3 W >=20 > Is there a way, on both linux and freebsd, of reading this information > other than looking at the writing on the chip directly? I've never noticed a reference to a way to do that directly. In some cases you can infer from the RPi revision code's "TTTTTTTT Type" field that it should have C0T (or later?) parts: The 14: CM4 and 13: 400. But, for this new example, the type field is far from sufficient and we can not be sure that even the whole revision code would be sufficient. Some B0T parts might have a b03114 revision code for all I know. =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?39AB95E8-AC86-465C-94E6-C2B8040EB45D>