From owner-freebsd-arm@freebsd.org Sun Jan 3 10:43:47 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 5447F4CD4A8 for ; Sun, 3 Jan 2021 10:43:47 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D7wNM1Tspz4l4N; Sun, 3 Jan 2021 10:43:46 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-wm1-x32d.google.com with SMTP id v14so14539966wml.1; Sun, 03 Jan 2021 02:43:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=OQi+EN99AIHVnQfcEQLinaWqiU43gE6RetcT73lFM20=; b=NJxy4V5lxWzNdGOx6psr2yFVKTtOtU9EAOYzMJjWjTKSs3dOxPQQS7l92wZNDpO7un 9O9IiZH2Z0CAbo0A47nzvTGncZntIblIw/Ed7GQykN1nUYhowxGwWJPmDtlCNFPyk8pu KtLFh9UZ88C+p34BVI4+e08HfhrJughiUAcM5bpwoIxZQ90RlpQEqMag0B/wV3//uZQu P3nQgySU8/bhsxQGT47xCxrYkbz8jbwx3jVvBUrrOPkPw0qKHzOICmllKqjmqbbl6JOs E7w1XC5e/3wwCkDMcpNGHvrAMfvHRyLJ4b09euUpgGe1JayqdrHTLnOYLbwpM/2iX4DX DyPA== X-Gm-Message-State: AOAM531F3vl1x9+nTpmPo5IthmarS9L67du/dIju2TeCtiqv6fdCnU/p YP91Okv+zbfk1U4sZ7f6Y80= X-Google-Smtp-Source: ABdhPJxPKS9tG0qVLWlBVvTYcJvArAeTdBTgQI83wWnwwTspxQaTUsxxB7NNKovBfNhN18B5SoENTg== X-Received: by 2002:a05:600c:410d:: with SMTP id j13mr22714292wmi.95.1609670625458; Sun, 03 Jan 2021 02:43:45 -0800 (PST) Received: from [192.168.1.167] (dynamic-046-114-104-069.46.114.pool.telefonica.de. [46.114.104.69]) by smtp.googlemail.com with ESMTPSA id z63sm31427470wme.8.2021.01.03.02.43.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Jan 2021 02:43:44 -0800 (PST) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) Subject: Re: RPi4b 8GB 13.0-Current, XHCI broken, wrong U-Boot ? Date: Sun, 3 Jan 2021 11:43:41 +0100 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> To: Andy McClements , Robert Crowston , Emmanuel Vadot , freebsd-arm@freebsd.org, Mark Millard In-Reply-To: <8edaad69-422f-8c9c-599c-e9eea00077f0@ip-ether.net> Message-Id: <26E20BD2-BD91-433F-9149-367D8AB9DFED@googlemail.com> X-Mailer: Apple Mail (2.3654.40.0.2.32) X-Rspamd-Queue-Id: 4D7wNM1Tspz4l4N X-Spamd-Bar: ---- 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:43:47 -0000 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 : >=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