Date: Sun, 3 Jan 2021 11:43:41 +0100 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Andy McClements <ajm@ip-ether.net>, Robert Crowston <crowston@protonmail.com>, Emmanuel Vadot <manu@freebsd.org>, freebsd-arm@freebsd.org, Mark Millard <marklmi@yahoo.com> Subject: Re: RPi4b 8GB 13.0-Current, XHCI broken, wrong U-Boot ? Message-ID: <26E20BD2-BD91-433F-9149-367D8AB9DFED@googlemail.com> In-Reply-To: <8edaad69-422f-8c9c-599c-e9eea00077f0@ip-ether.net> References: <007c8658-b7b6-6852-536c-9c36af64506b@ip-ether.net> <D22EDD0F-8A8E-466C-BCEC-C8E2B3EA9A6B@googlemail.com> <aaefd44f-9dfd-be08-b446-d85c1df185a9@ip-ether.net> <5B626DCC-6F7C-4554-803C-F488A1ED9BEB@googlemail.com> <56d10ea4-3284-3e4c-9521-8bf1008caa2b@ip-ether.net> <26D146B8-0362-4008-9A1F-A6CD6B1479BB@googlemail.com> <8edaad69-422f-8c9c-599c-e9eea00077f0@ip-ether.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Andy & friends :-) ,=20 according to https://www.freshports.org/sysutils/rpi-firmware/=20 we are using 20201201 , assumed that releases are compiled on = amd64(aarch64-port is behind). 20201201 is exactly what I see when I compile sysutils/rpi-firmware = manually=20 on amd64(for all files). But when I open = https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/13.0/F= reeBSD-13.0-CURRENT-arm64-aarch64-RPI3-20201210-7578a4862f0.img.xz I see a mixture of versioning(what has good reason), specially=20 2019/Nov/22 and 2020/Dec./10 . So the good reason is exactly those problems with different versions of = special files. And this let me assume that=20 EMBEDDEDPORTS=3D"sysutils/u-boot-rpi-arm64 sysutils/rpi-firmware=E2=80=9C=20= In https://github.com/freebsd/freebsd-src/release/arm64/RPI.conf is NOT embedded by default, instead we use different files, The files we deal with are specially bcm2711-rpi-4-b.dts ( the reason = for https://reviews.freebsd.org/D26853)=20 and start4.elf and fixup4.dat . So assuming that the firmware is not embedded by default in the sysutils = -port and instead uses different HARD-LINKED versions of = firmware-files, What we do here is finding the correct files which we have to hard-link = for the (*.img)releases. That=E2=80=99s why I sent you the link to :=20 = https://sourceforge.net/projects/d26853-bcm2711-rpi-4-b-dtb/files/rpi4_pac= k_freebsd.zip/download Because currently I assume that start4.elf and fixup4.dat of that link=20= Will boot up your machine directly from USB/SSD. So the question is WHICH files should differ from sysutils/rpi-firmware. While organizing u-boot/firmware/releases is the area of =E2=80=8B=E2=80=8B= manu@, the hardcoded #0X=E2=80=A6. -driver is the area of PCIE-Boss Rob = Crowston :-), this two have the last word what is to do. So finding the right combination of hardcoding, firmware-updates and = hard-linked firmware-files and organizing the (*.img)-release is what = we currently try while I have to browse the fbsd-src again to look for = WHERE=20 some files are hard-linked. So giving manu@ a chance to =E2=80=9Ereorganize" the release is possible = when , let=E2=80=99s say at least 3 Persons=20 ( e.g. Rob, YOU & me) say: these are the files we have to go with for = hard-link. long story short:=20 Andy, yes, thanks in advance to test = https://sourceforge.net/projects/d26853-bcm2711-rpi-4-b-dtb/files/rpi4_pac= k_freebsd.zip/download and=20 https://reviews.freebsd.org/D26853=20 against whatever firmware-version from rpi-org you like., but best = against those which are in the current img-release. (22/November/2019 = and 10/December/2020) AND the latest release from rip-org. By the way, it=E2=80=99s an annoying thing with the firmware but we re = nor the only ones who have to deal with that, e.g. edkII also has sometimes. (M. Millard, didn=E2=80=99t you post a link in the past to src where the = files are hard linked?) Sorry for my chaotic English thanks,Regards K. > Am 03.01.2021 um 09:45 schrieb Andy McClements <ajm@ip-ether.net>: >=20 > =E2=80=94=E2=80=94=E2=80=94 > =E2=80=A6... > However may I suggest I test with files from one of the previous = official repository ZIP archives ? That way we can be sure of the = versioning. eg: >=20 > https://github.com/raspberrypi/firmware/releases >=20 > Should I test with the 1.20201022.zip ? >=20 > Regards, Andy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26E20BD2-BD91-433F-9149-367D8AB9DFED>