Date: Fri, 9 Oct 2020 18:46:20 -0700 From: Mark Millard <marklmi@yahoo.com> To: Klaus Cucinauomo <maciphone2@googlemail.com> Cc: freebsd-arm@freebsd.org Subject: Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) Message-ID: <A4434A74-1D46-4372-9936-E794410C128B@yahoo.com> In-Reply-To: <7CB99D94-6F37-4150-9D1B-9488D4FE83EF@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> <93E411FA-6024-4E2F-AAFF-C051AF4F35EE@yahoo.com> <7CB99D94-6F37-4150-9D1B-9488D4FE83EF@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Oct-9, at 18:08, Klaus Cucinauomo <maciphone2 at googlemail.com> = wrote: >> Am 10.10.2020 um 02:39 schrieb Mark Millard <marklmi@yahoo.com>: >> =E2=80=A6=E2=80=A6 >> ... >> No use is made of FreeBSD=E2=80=99s sys/gnu/dts/arm64/broadcom/ by = this technique. =46rom the log for one of my builds of sysutils/rpi-firmware : ( I ignore armstub8*.bin related things. ) =3D=3D=3D> License BROADCOM accepted by the user . . . =3D> Attempting to fetch = https://codeload.github.com/raspberrypi/firmware/tar.gz/2042453?dummy=3D/r= aspberrypi-firmware-1.20200723.g20200723-2042453_GH0.tar.gz . . . =3D=3D=3D> Extracting for rpi-firmware-1.20200723.g20200723 =3D> SHA256 Checksum OK for = raspberrypi-firmware-1.20200723.g20200723-2042453_GH0.tar.gz. . . . =3D=3D=3D> Patching for rpi-firmware-1.20200723.g20200723 cp -f /usr/ports/sysutils/rpi-firmware/files/config.txt = /wrkdirs/usr/ports/sysutils/rpi-firmware/work/firmware-2042453/boot/ cp -f /usr/ports/sysutils/rpi-firmware/files/config_rpi_0_w.txt = /wrkdirs/usr/ports/sysutils/rpi-firmware/work/firmware-2042453/boot/ cp -f /usr/ports/sysutils/rpi-firmware/files/config_rpi3.txt = /wrkdirs/usr/ports/sysutils/rpi-firmware/work/firmware-2042453/boot/ cp -f /usr/ports/sysutils/rpi-firmware/files/config_rpi3_edk2.txt = /wrkdirs/usr/ports/sysutils/rpi-firmware/work/firmware-2042453/boot/ cp -f /usr/ports/sysutils/rpi-firmware/files/config_rpi4.txt = /wrkdirs/usr/ports/sysutils/rpi-firmware/work/firmware-2042453/boot/ /bin/rm -f = /wrkdirs/usr/ports/sysutils/rpi-firmware/work/firmware-2042453/boot/kernel= .img /bin/rm -f = /wrkdirs/usr/ports/sysutils/rpi-firmware/work/firmware-2042453/boot/kernel= 7.img . . . So, if you want to see what sysutils/rpi-firmware is currently based on, you can try that: fetch = https://codeload.github.com/raspberrypi/firmware/tar.gz/2042453?dummy=3D/r= aspberrypi-firmware-1.20200723.g20200723-2042453_GH0.tar.gz yourself and then look at the content of the .tar.gz produced. When I try it: fetch = https://codeload.github.com/raspberrypi/firmware/tar.gz/2042453?dummy=3D/r= aspberrypi-firmware-1.20200723.g20200723-2042453_GH0.tar.gz fetch: = https://codeload.github.com/raspberrypi/firmware/tar.gz/2042453?dummy=3D/r= aspberrypi-firmware-1.20200723.g20200723-2042453_GH0.tar.gz: size of = remote file is not known raspberrypi-firmware-1.20200723.g20200723-2042 177 MB 8136 kBps = 22s # tar -tf raspberrypi-firmware-1.20200723.g20200723-2042453_GH0.tar.gz | = more firmware-2042453/ firmware-2042453/.github/ firmware-2042453/.github/ISSUE_TEMPLATE/ firmware-2042453/.github/ISSUE_TEMPLATE/bug_report.md firmware-2042453/README.md firmware-2042453/boot/ firmware-2042453/boot/COPYING.linux firmware-2042453/boot/LICENCE.broadcom firmware-2042453/boot/bcm2708-rpi-b-plus.dtb firmware-2042453/boot/bcm2708-rpi-b.dtb firmware-2042453/boot/bcm2708-rpi-cm.dtb firmware-2042453/boot/bcm2708-rpi-zero-w.dtb firmware-2042453/boot/bcm2708-rpi-zero.dtb firmware-2042453/boot/bcm2709-rpi-2-b.dtb firmware-2042453/boot/bcm2710-rpi-2-b.dtb firmware-2042453/boot/bcm2710-rpi-3-b-plus.dtb firmware-2042453/boot/bcm2710-rpi-3-b.dtb firmware-2042453/boot/bcm2710-rpi-cm3.dtb firmware-2042453/boot/bcm2711-rpi-4-b.dtb firmware-2042453/boot/bootcode.bin firmware-2042453/boot/fixup.dat firmware-2042453/boot/fixup4.dat firmware-2042453/boot/fixup4cd.dat firmware-2042453/boot/fixup4db.dat firmware-2042453/boot/fixup4x.dat firmware-2042453/boot/fixup_cd.dat firmware-2042453/boot/fixup_db.dat firmware-2042453/boot/fixup_x.dat firmware-2042453/boot/kernel.img . . . firmware-2042453/boot/overlays/wittypi.dtbo firmware-2042453/boot/start.elf firmware-2042453/boot/start4.elf firmware-2042453/boot/start4cd.elf firmware-2042453/boot/start4db.elf firmware-2042453/boot/start4x.elf firmware-2042453/boot/start_cd.elf firmware-2042453/boot/start_db.elf firmware-2042453/boot/start_x.elf . . . (I'll not list it all.) The .tar.gz provides the .dtb files directly., no compilation needed. The .tar.gz contains lots of unused files and directories as well as the ones to be put on RPi* media. > Seems to be unclear(at least to me), whether ever used or never > ...while absolutely possible that you`re right here. > ` have discussed that with Rob Crowston & Mike Karels some time ago,=20= > The problem was the bcm2711-rpi-4-b.dtb , which at that time = shouldn=E2=80=99t be changed because to stay compatible with the = 8GB-model., > so possibly since then there never was a newer dts compiled to dtb. The fetch command picks out a specific commit and ignores more recent commits (until the Makefile and distinfo are changed to cause and check the results of a different fetch command). > But I G U E S S(still can=E2=80=99t resist;-) that we now have to = patch&compile( at least bcm2711-rpi-4-b) to stay in touch with 2020.10 >=20 >> Am 10.10.2020 um 02:21 schrieb Mark Millard <marklmi at yahoo.com>: >> My FreeBSD USB3 SSD is partitioned as:=E2=80=A6=E2=80=A6.. >> After that it tries to boot from ethernet (which was >> not connected). >=20 > Tomorrow I will look again exactly with which partition tables I = booted the SSD,=20 > for today I am completely dizzy from all that rpi-dtb stuff , I = can=E2=80=99t remember what I did :-) =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?A4434A74-1D46-4372-9936-E794410C128B>