From nobody Thu Jan 11 16:20:28 2024 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 4T9qdy5SCfz56NP1 for ; Thu, 11 Jan 2024 16:20:38 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from mail-yw1-x1130.google.com (mail-yw1-x1130.google.com [IPv6:2607:f8b0:4864:20::1130]) (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 4T9qdy3qjxz4nqB for ; Thu, 11 Jan 2024 16:20:38 +0000 (UTC) (envelope-from dfr@rabson.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-5e76948cda7so53479757b3.3 for ; Thu, 11 Jan 2024 08:20:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rabson-org.20230601.gappssmtp.com; s=20230601; t=1704990037; x=1705594837; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hBsAOA6v7zI6TkEl10yjNdVQLlnYYcB2UvaCpmfFmuA=; b=aaPX4zxTgt6uBD6EgJ33Af9KzD1TCTA7Iw4IcjFb2ayIfDpvA+r6S4R2cVoPWTMI49 4pN7GoWyr7l2FGGA1kRJskJt/z8mpJkSSU4bSo2gaYKTqaVcpKq2a2jlSBuHPPEaxT5S YSdjsQeS7JUSkL0UNRWSotKWL0cV72SPJ7kxyZ97z7dNQY8soo5FrfkqZGoJnjTlr+eY 4eYt4C9xdeDk1uucVtTmWQi8dS55J4OcMpuxCNeyKBSg7+jzUpYz3JOj4/MUGKP9w+0K y7Pb0TLSEi1gYRBY0XkgrohFij9bhrfN3UYsC9yw9Z2a6hXQYlQfFEfPLbJpsjH/jyvF CDNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704990037; x=1705594837; 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=hBsAOA6v7zI6TkEl10yjNdVQLlnYYcB2UvaCpmfFmuA=; b=AhQtlt10vtvZoo6oxFYFIj09LDT2mqOU1IU4ILzy3SolyZRtZAsouqpc8gbeNwKOIX faGdi3xovm9QP18W0a9qhAAj1rQiSoSxOd2monsxYfmHL/5wTtWZCN8f3u5i7+or/KN8 F3Wftw7QojkV7ba74/KLpft5C0Fi7NnVndkkMH4MTOsrFglDLyi3W9+6hcNIrv/wrFFC 8Pcz4v2jFFEFSkoUCe8Hbvw3U2ct1AQxT/bf5jk6r5F38eMQ3zat9GRfA7clghGkwezk buTu4SyUi3krKkWUZlqHrm7IOLhkHsYnD41mq3TOkobPdUd+WU28KCJsU9zo1uBAPZIx /ISg== X-Gm-Message-State: AOJu0Yz33xQC73DaP6oLEtMDq9IDxbyDXjXdLQNQRqG7Mp6tJUqGDDng kvesYA6Nn5Xsb/C3W4jyvgq7oDkM0mIk+ZIkqphMVHRg80DgVg== X-Google-Smtp-Source: AGHT+IGY9EYUaiAceDHwUv5b3mixicDERnpKnXlESkHsPfJj0gT2JYOxVDi7lDywaIA3HJxR2xgBhw0mRzLhjpYb8Go= X-Received: by 2002:a81:4917:0:b0:5e7:ed6f:c63b with SMTP id w23-20020a814917000000b005e7ed6fc63bmr9911ywa.95.1704990037422; Thu, 11 Jan 2024 08:20:37 -0800 (PST) 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: <5a39810c-5fd8-4969-a222-2561b050b035@FreeBSD.org> In-Reply-To: From: Doug Rabson Date: Thu, 11 Jan 2024 16:20:28 +0000 Message-ID: Subject: Re: When will FreeBSD support RPI5? To: Mark Millard Cc: Jesper Schmitz Mouridsen , John Kennedy , ykla , FreeBSD ARM List Content-Type: multipart/alternative; boundary="00000000000086c7c0060eaded9a" X-Rspamd-Queue-Id: 4T9qdy3qjxz4nqB 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:2607:f8b0::/32, country:US] --00000000000086c7c0060eaded9a Content-Type: text/plain; charset="UTF-8" On Thu, 11 Jan 2024 at 01:30, Mark Millard wrote: > (While I normally use FreeBSD's U-Boot type of context, > My builds do have patches to allow RPi4B EDK2 use to > avoid the problems that I know to test for.) > I'm curious how you were able to boot FreeBSD on rpi4 with EDK2 - I tried with both the FreeBSD package as well as the latest release from github. FreeBSD-14.0 stalled trying to initialise xhci while FreeBSD-15 gets a little further but also hangs before reaching single user mode. I'm wondering if perhaps I should use the dtbs from sysutils/rpi-firmware rather than the ones from sysutils/edk2@rpi4. --00000000000086c7c0060eaded9a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, 11 Jan 2024 at 01:30, Mark Mi= llard <marklmi@yahoo.com> wr= ote:
(While I normally use FreeBSD's U-Boot t= ype of context,
My builds do have patches to allow RPi4B EDK2 use to
avoid the problems that I know to test for.)

I'm curious how you were able to boot FreeBSD on rpi4 with EDK2 -= I tried with both the FreeBSD package as well as the latest release from g= ithub. FreeBSD-14.0 stalled trying to initialise xhci while FreeBSD-15 gets= a little further but also hangs before reaching single user mode. I'm = wondering if perhaps I should use the dtbs from sysutils/rpi-firmware rathe= r than the ones from sysutils/edk2@rpi4.

--00000000000086c7c0060eaded9a--