Date: Fri, 9 Oct 2020 17:39:13 -0700 From: Mark Millard <marklmi@yahoo.com> To: Klaus Cucinauomo <maciphone2@googlemail.com> Cc: Kyle Evans <kevans@freebsd.org>, Robert Crowston <crowston@protonmail.com>, freebsd-arm@freebsd.org Subject: Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) Message-ID: <93E411FA-6024-4E2F-AAFF-C051AF4F35EE@yahoo.com> In-Reply-To: <27E7A6A9-04A4-4B15-96CB-84AE478ED755@googlemail.com> References: <D8BDF95A-D6A8-4E95-A0CE-D53068E8355B.ref@yahoo.com> <D8BDF95A-D6A8-4E95-A0CE-D53068E8355B@yahoo.com> <ABE16EA6-49F1-461F-9B8A-6DAA7ED6A18D@googlemail.com> <98BC985D-EAAB-4AFB-AA8F-7391A45C4EBF@yahoo.com> <91324D35-B66A-4674-AE37-45F3DDB736FD@yahoo.com> <2B3F0409-88F2-4EBD-9C39-37929F973C77@yahoo.com> <B3133D77-FA24-4F42-B529-D0B56F48E790@yahoo.com> <CCEEC0AD-B874-4753-AAA1-B3B5B302A30C@googlemail.com> <E82AE086-837C-4CEA-92D5-78A39412F964@yahoo.com> <803EF261-1407-4331-AC56-1D49E05F8382@googlemail.com> <2FAA304E-045B-4B10-AA14-1E869FB6FD00@yahoo.com> <27E7A6A9-04A4-4B15-96CB-84AE478ED755@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Oct-9, at 17:17, Klaus Cucinauomo <maciphone2@googlemail.com> =
wrote:
>> Am 09.10.2020 um 23:25 schrieb Mark Millard <marklmi@yahoo.com>:
>>=20
>> FreeBSD imports lots of linux-dts material that it does not put
>> to use. Only some of the imported material is used.
>>=20
>> release/arm64/RPI3.conf indicates use of:
>> (There is not RPi4 release yet.)
>>=20
>> DTB_DIR=3D"/usr/local/share/rpi-firmware"
>> DTB=3D"bcm2709-rpi-2-b.dtb bcm2710-rpi-3-b.dtb =
bcm2710-rpi-3-b-plus.dtb bcm2711-rpi-4-b.dtb"
>> . . .
>> EMBEDDEDPORTS=3D"sysutils/u-boot-rpi3 sysutils/rpi-firmware"
>> . . .
>> UBOOT_DIR=3D"/usr/local/share/u-boot/u-boot-rpi3=E2=80=9C
>> =E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6.
>>=20
>> It is not using sys/gnu/dts/arm64/broadcom/ material.
>=20
>=20
> ah, `forgot to mention :
> [dtb =3D DeviceTree-Blob =3D=3D compiled dts(DeviceTreeSource)]
> So the dtb`s you mention are compiled off of the dts.
> So I GUESS ;-) that sys/gnu/dts/arm64/broadcom/ isn=E2=80=99t a dead =
unused directory =E2=80=A6
Look at the sysutils/rpi-firmware port that creates and
fills in /usr/local/share/rpi-firmware/ with the .dtb
files that are copied by the above procedure.
It makes no use of sys/gnu/dts/arm64/broadcom/ at all.
Instead it does things like the following in its Makefile:
USE_GITHUB=3D yes
GH_ACCOUNT=3D raspberrypi
(I omit a 2nd account that is also listed.)
GH_PROJECT=3D firmware
(I omit a 2nd project that is also listed.)
FW_TAG=3D 2042453
. . .
GH_TAGNAME=3D ${FW_TAG}
(I omit a 2nd TAGNAME that is also listed.)
and in its distinfo it has:
TIMESTAMP =3D 1596906388
SHA256 (raspberrypi-firmware-1.20200723.g20200723-2042453_GH0.tar.gz) =3D =
a90ce74236fa04cbb11232c077a1271afdeefb5b0af417a88076c4948e569cd4
SIZE (raspberrypi-firmware-1.20200723.g20200723-2042453_GH0.tar.gz) =3D =
186178244
(I omit a 2nd file that is also listed.)
So it gets a .tar.gz from github that supplies the material,
in a already compiled/built form as it turns out.
No use is made of FreeBSD's sys/gnu/dts/arm64/broadcom/ by this =
technique.
=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?93E411FA-6024-4E2F-AAFF-C051AF4F35EE>