From nobody Mon Aug 21 10:37:58 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RTpps3sxxz4qbTR for ; Mon, 21 Aug 2023 10:38:13 +0000 (UTC) (envelope-from guyyur@gmail.com) Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RTppr6kfbz4QGQ for ; Mon, 21 Aug 2023 10:38:12 +0000 (UTC) (envelope-from guyyur@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-99bcfe28909so400271966b.3 for ; Mon, 21 Aug 2023 03:38:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692614290; x=1693219090; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fB/ONUUf4j0lZlwAlHqZsAm864mNtvT3/m+7nseLnpg=; b=b6ngPanArOttjpJtq1iyuOehfMeOCgM28pY2kjMcsZdgkNRxL7Wimx5e9bS39QTECt 8dNdPPRjOVjGkZy0cFl1rnumbzkUxbdyTY7BKqtTYR/0kZR4/AW+wHrKLB2JkP8q8QIv ujSu/fUfV8s25UzpG/NtLDGuLlCblR1lVoHGtLJao9vnEYC2iVnGqNGECijlB74h6XnY 0nxlBmlqAWPWPOOpfJvZgQCuQQaRjhnQZ+cbBcKaBT+Ng8L0W+O/mapGDG+8/PKWohQv cFqc2Ni/+MF3CUUR+3iKfzkQ0Flj5AYi/P/toOBX/dtjgg0R7drtremo+bzi9pWbh+O0 60bQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692614290; x=1693219090; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fB/ONUUf4j0lZlwAlHqZsAm864mNtvT3/m+7nseLnpg=; b=CNOQW6Nb6FEOrRiBn9A9euB/y4z09qI2mhpCIXo3osfFOCM76mk0UvzVaDMg3uMI5x tkVGxYN7lYiHEmcEQjVJauLgfXuCAUwWLZxxD8hB5XPrxSzKHgvmgd48nXXddB+Z3pH8 jaMzE4w3BWgwsqcbg/bQ+bgxrH6SkOEO9FcxZU6l8VRjXIRL3v60RXv+VjSk0eW9XYv2 v/KR1la7FvT1uRLGWNhjv9aJorJ4Zny8oD0/cXQRy9jzN+iDwc/QlwFFN/1MRujU1wsk cxzxOc8lLGf5/P9omL2LXJk3tyrxFHY5TrTKSk0JUHTghqaDf7jLO6Hw2gaEhbPXhY9c C/xA== X-Gm-Message-State: AOJu0YyyTh4upX3fkH7ge9h5jRZTG27P5I1Z99YbwBMa3NwNE6BcWHl4 1Twy2kcVuocn/e0pYIQQbEMvRjs+pNbCJh+AlLr8MHR6DqQ= X-Google-Smtp-Source: AGHT+IFfrH1yYUcqHdBvqPxMHWMKTury9fOjyg+a883JFuitnDCTzqJ5U8vzxFxvVFAQ3ltvGjNT0whu1IO/OsG8y0g= X-Received: by 2002:a17:906:2929:b0:99e:bb:e1b5 with SMTP id v9-20020a170906292900b0099e00bbe1b5mr4560323ejd.24.1692614290024; Mon, 21 Aug 2023 03:38:10 -0700 (PDT) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Guy Yur Date: Mon, 21 Aug 2023 13:37:58 +0300 Message-ID: Subject: Re: Rock64 vs. USB3 for 14.0-ALPHA2 's Rock64 snapshot vs. device tree update(?) To: Mark Millard Cc: freebsd-arm Content-Type: multipart/alternative; boundary="0000000000007fcc9106036c796a" X-Rspamd-Queue-Id: 4RTppr6kfbz4QGQ X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --0000000000007fcc9106036c796a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Sun, Aug 20, 2023 at 10:08=E2=80=AFPM Mark Millard w= rote: > On Aug 20, 2023, at 11:08, Guy Yur wrote: > > ... (snip) > > > > I boot from sdcard with msdosfs partition with EFI/BOOT/bootaa64.efi an= d > the dtb in rockchip/ dir in the partition. > > I tested renaming the rockchip dir so the dtb won't be found and there > was still a device tree provided. > > seen in devinfo and ofwdump. > > Back when I established my structure (long ago) this provided > U-Boot's translation of its *.dtb --which did not work for > FreeBSD purposes at the time. FreeBSD's Rock64 related updates > have been based on tracking upstream linux at some point. > Doing what I did got the FreeBSD *.dtb that FreeBSD expected > (at the time. anyway). > > Updating with more correct information for future reference since from my previous post it sounds like u-boot behavior changed when it has not in regards to placing the fdt file in the EFI partition. The real issue is a bug in u-boot 2023.07.02 failing to read the fdt from the EFI partition and the u-boot provided fdt bindings for Rock64 containing wrong xhci definition. Reading fdt file was fixed in: https://source.denx.de/u-boot/u-boot/-/commit/2984d21a28f812c9c1fd2243cc727= 96f69a61585 I believe all issues should be resolved in the next u-boot release. ... (snip) > > I do not know if the Rock64 related support will continue to > be updated to track the linux upstream updates or not. (If not, > then likely snapshots and releases for Rock64 would stop.) > > As stands I do not plan on going down a path that might not > be what FreeBSD ends up with for Rock64 related support if > it is updated. For now, I've just put the Rock64 to the side. > But I'm keeping copies of your notes. > > I think the current fdt that comes with 14.0 works fine for USB3, so at least for now a modern device tree should work. ... (snip) > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > =3D=3D=3D Guy Yur --0000000000007fcc9106036c796a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

On Sun, Aug 20, 2023 at 10:08=E2=80=AFPM Mark Mill= ard <marklmi@yahoo.com> wrot= e:
On Aug 20, 20= 23, at 11:08, Guy Yur <guyyur@gmail.com> wrote:

... (snip)
>
> I boot from sdcard with msdosfs partition with EFI/BOOT/bootaa64.efi a= nd the dtb in rockchip/ dir in the partition.
> I tested renaming the rockchip dir so the dtb won't be found and t= here was still a device tree provided.
> seen in devinfo and ofwdump.

Back when I established my structure (long ago) this provided
U-Boot's translation of its *.dtb --which did not work for
FreeBSD purposes at the time. FreeBSD's Rock64 related updates
have been based on tracking upstream linux at some point.
Doing what I did got the FreeBSD *.dtb that FreeBSD expected
(at the time. anyway).

=C2=A0
Updating with more correct informati= on for future reference since
from my previous post it sounds like u-boo= t behavior=C2=A0changed when
it has not in regards to placing the fdt fi= le in the EFI partition.

The real issue is a bug i= n u-boot 2023.07.02 failing to read the fdt from the EFI partition
and the u-boot provided fdt bindings for Rock64 containing wrong xhci def= inition.


I believe all iss= ues should be resolved in the next u-boot release.

... (snip)

I do not know if the Rock64 related support will continue to
be updated to track the linux upstream updates or not. (If not,
then likely snapshots and releases for Rock64 would stop.)

As stands I do not plan on going down a path that might not
be what FreeBSD ends up with for Rock64 related support if
it is updated. For now, I've just put the Rock64 to the side.
But I'm keeping copies of your notes.


I think the current fdt that comes wit= h 14.0 works fine for USB3,
so at least for now a modern device t= ree should work.

... (snip)

=3D=3D=3D
Mark Millard
marklmi at yahoo.com


=3D=3D=3D
Guy Yur=C2=A0
--0000000000007fcc9106036c796a--