Date: Sun, 3 Jan 2021 11:57:51 +0100 From: Emmanuel Vadot <manu@bidouilliste.com> To: Klaus =?ISO-8859-1?Q?K=FCchemann?= <maciphone2@googlemail.com> Cc: Klaus =?ISO-8859-1?Q?K=FCchemann?= via freebsd-arm <freebsd-arm@freebsd.org>, Andy McClements <ajm@ip-ether.net>, Robert Crowston <crowston@protonmail.com>, Mark Millard <marklmi@yahoo.com> Subject: Re: RPi4b 8GB 13.0-Current, XHCI broken, wrong U-Boot ? Message-ID: <20210103115751.9d9d5470a6e4e3f849016b88@bidouilliste.com> In-Reply-To: <26E20BD2-BD91-433F-9149-367D8AB9DFED@googlemail.com> 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> <26E20BD2-BD91-433F-9149-367D8AB9DFED@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 Jan 2021 11:43:41 +0100 Klaus K=FCchemann via freebsd-arm <freebsd-arm@freebsd.org> wrote: > 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(aarch= 64-port is behind). > 20201201 is exactly what I see when I compile sysutils/rpi-firmware manua= lly=20 > on amd64(for all files). This port only compile the rpi3-psci-monitor part. The boot file for rpi (bootcode, dtb, start* etc ...) aren't compiled, they are just fetched and installed. > But when I open https://download.freebsd.org/ftp/snapshots/arm64/aarch64/= ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-arm64-aarch64-RPI3-20201210-7578a4862f= 0.img.xz > I see a mixture of versioning(what has good reason), specially=20 > 2019/Nov/22 and 2020/Dec./10 . I've updated the port on the 13th of december (https://svnweb.freebsd.org/ports?view=3Drevision&revision=3D557893) so you will not see the same files in this image. > So the good reason is exactly those problems with different versions of s= pecial files. > And this let me assume that=20 > EMBEDDEDPORTS=3D"sysutils/u-boot-rpi-arm64 sysutils/rpi-firmware?=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 f= or the (*.img)releases. > That?s why I sent you the link to :=20 > https://sourceforge.net/projects/d26853-bcm2711-rpi-4-b-dtb/files/rpi4_pa= ck_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. The port IS used for generating the image (and I mean the port not the package so even if an update is made to the port and there is no package yet the port, so the new files, will be used when the image is created). Check the RPI image (https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/13.0/FreeBSD-13.0-CU= RRENT-arm64-aarch64-RPI-20201224-3cc0c0d66a0-255241.img.xz) > So the question is WHICH files should differ from sysutils/rpi-firmware. None. > While organizing u-boot/firmware/releases is the area of ??manu@, the har= dcoded #0X?. -driver is the area of PCIE-Boss Rob Crowston :-), this two ha= ve 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 curre= ntly 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 ?reorganize" the release is possible when , l= et?s say at least 3 Persons=20 There is nothing to "reorganize". > ( e.g. Rob, YOU & me) say: these are the files we have to go with for har= d-link. >=20 > long story short:=20 > Andy, yes, thanks in advance to test https://sourceforge.net/projects/d26= 853-bcm2711-rpi-4-b-dtb/files/rpi4_pack_freebsd.zip/download and=20 > https://reviews.freebsd.org/D26853=20 > against whatever firmware-version from rpi-org you like., but best agains= t those which are in the current img-release. (22/November/2019 and 10/Dece= mber/2020) AND the latest release from rip-org. >=20 >=20 > By the way, it?s an annoying thing with the firmware but we re nor the on= ly ones who have to deal with that, > e.g. edkII also has sometimes. >=20 > (M. Millard, didn?t you post a link in the past to src where the files ar= e hard linked?) >=20 > Sorry for my chaotic English > thanks,Regards >=20 > K. >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > > Am 03.01.2021 um 09:45 schrieb Andy McClements <ajm@ip-ether.net>: > >=20 > > ??? > > ?... > > However may I suggest I test with files from one of the previous offici= al 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 >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" --=20 Emmanuel Vadot <manu@bidouilliste.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210103115751.9d9d5470a6e4e3f849016b88>