From owner-freebsd-arm@freebsd.org Fri Jan 1 18:25:10 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 780524D008B for ; Fri, 1 Jan 2021 18:25:10 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D6tjf2XVzz3R3X for ; Fri, 1 Jan 2021 18:25:10 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qt1-f170.google.com (mail-qt1-f170.google.com [209.85.160.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 3D0F32D2E0 for ; Fri, 1 Jan 2021 18:25:10 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qt1-f170.google.com with SMTP id g24so14588890qtq.12 for ; Fri, 01 Jan 2021 10:25:10 -0800 (PST) X-Gm-Message-State: AOAM531fuR8L1PtJ5murc0FZp/95USZyrxs/xDGe0F2BpT6p2g5KIY3d qkGZnyUoUuT1aAJ2AxJpNADFipNYc+uj7vUFNrM= X-Google-Smtp-Source: ABdhPJxCvaiJyOz8I4y2Q1a/jBPxT/y9ed9SBzlLNom1u9Iywfdtq1PGteLVm8v3taRiRI3hRIzePpKuDVtjNhWPmsY= X-Received: by 2002:ac8:7141:: with SMTP id h1mr61659041qtp.211.1609525509749; Fri, 01 Jan 2021 10:25:09 -0800 (PST) MIME-Version: 1.0 References: <007c8658-b7b6-6852-536c-9c36af64506b@ip-ether.net> In-Reply-To: From: Kyle Evans Date: Fri, 1 Jan 2021 12:24:58 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: RPi4b 8GB 13.0-Current, XHCI broken, wrong U-Boot ? To: Robert Crowston Cc: Andy McClements , freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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: Fri, 01 Jan 2021 18:25:10 -0000 On Fri, Jan 1, 2021 at 11:05 AM Robert Crowston via freebsd-arm wrote: > > The u-boot output is not a smoking gun; the u-boot version packaged up th= ere did not have the driver in it. The freebsd driver is separate and does = not depend on u-boot. > > As I recall, that warning indicates that we tried, but failed to load the= firmware, which I haven=E2=80=99t seen in the wild before. Could you try b= ooting in verbose mode? > > Do you know what version of USB firmware is installed on the Pi? Alternat= ively, when did you purchase this hardware? (My suspicion is that the Pi fo= undation moved the goalposts again ...) > > You say this works fine with the UEFI boot? If you can use boot with that= one, it would be good to see if it works. > > Re: state of the pi 4, I guess we should bundle up a proper image of it, = either for USB drive or SD Card, instead of telling users to perform all th= is surgery. > What surgery are you referring to here? The -RPI image OP tried from the 24th is one that should boot as-is on all arm64 RPi variants without modification using the upstream U-Boot rpi arm64 config and a consolidated config.txt that conditionally does what's needed for the RPi4.