From owner-freebsd-arm@freebsd.org Sun Jan 3 10:58:01 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 575444CDB0F for ; Sun, 3 Jan 2021 10:58:01 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D7whn0MrRz4m00 for ; Sun, 3 Jan 2021 10:58:00 +0000 (UTC) (envelope-from manu@bidouilliste.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1609671472; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=EaEhI1HXJaNzV9pdenOrIopqs16Hjs8mj+6RioADkkw=; b=tuURSXzFmyoGyAMtBu8LURCrFVUkvvJfIGOd9R0U7xkZiV9KSVyGJTLvwBPQb+2q0xM45V lZ/Y9IPpwSNlGmYvbRuP0SZC8/JQJqYd7wljVGyAT8KVE0njQnKHx7v9168tKakV8C0VWq vzYj5ckTeOQ6bz9vKI+xR0uuVsC4yXQ= Received: from amy (31-38-167-109.abo.bbox.fr [31.38.167.109]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 9739cb48 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sun, 3 Jan 2021 10:57:52 +0000 (UTC) Date: Sun, 3 Jan 2021 11:57:51 +0100 From: Emmanuel Vadot To: Klaus =?ISO-8859-1?Q?K=FCchemann?= Cc: Klaus =?ISO-8859-1?Q?K=FCchemann?= via freebsd-arm , Andy McClements , Robert Crowston , Mark Millard 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> <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> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4D7whn0MrRz4m00 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2021 10:58:01 -0000 On Sun, 3 Jan 2021 11:43:41 +0100 Klaus K=FCchemann via freebsd-arm 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 : > >=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