RPi4b 8GB 13.0-Current, XHCI broken, wrong U-Boot ?

[Klaus Küchemann]

Hi Andy & friends :-) , 
according to https://www.freshports.org/sysutils/rpi-firmware/ 
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 
on amd64(for all files).
But when I open https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-arm64-aarch64-RPI3-20201210-7578a4862f0.img.xz
I see a mixture of versioning(what has good reason), specially 
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 
EMBEDDEDPORTS="sysutils/u-boot-rpi-arm64 sysutils/rpi-firmware“ 
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) 
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’s why I sent you the link to : 
https://sourceforge.net/projects/d26853-bcm2711-rpi-4-b-dtb/files/rpi4_pack_freebsd.zip/download
Because currently I assume that start4.elf and fixup4.dat of that link 
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 ​​manu@, the hardcoded #0X…. -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 
some files are hard-linked.
So giving manu@ a chance to „reorganize" the release is possible when , let’s say at least 3 Persons 
( e.g. Rob, YOU & me) say: these are the files we have to go with for hard-link.

long story short: 
Andy, yes, thanks in advance to test https://sourceforge.net/projects/d26853-bcm2711-rpi-4-b-dtb/files/rpi4_pack_freebsd.zip/download and 
https://reviews.freebsd.org/D26853 
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’s 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’t 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 at ip-ether.net>:
> 
> ———
> …...
> 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:
> 
> https://github.com/raspberrypi/firmware/releases
> 
> Should I test with the 1.20201022.zip ?
> 
> Regards, Andy