From nobody Mon Jan 6 20:08:35 2025 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 4YRlcQ22XPz5k7qH for ; Mon, 06 Jan 2025 20:08:38 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YRlcP286xz4VCd for ; Mon, 6 Jan 2025 20:08:37 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net; dmarc=none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 506K8ZfH033376 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 6 Jan 2025 12:08:35 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 506K8ZZL033375 for freebsd-arm@freebsd.org; Mon, 6 Jan 2025 12:08:35 -0800 (PST) (envelope-from fbsd) Date: Mon, 6 Jan 2025 12:08:35 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Buildworld fatal error: 'byteswap.h' file not found on armv7 Message-ID: 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 4YRlcP286xz4VCd X-Spamd-Bar: / X-Spamd-Result: default: False [-0.92 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.971]; NEURAL_HAM_MEDIUM(-0.85)[-0.851]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; DMARC_NA(0.00)[zefox.net]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; R_SPF_NA(0.00)[no SPF record] As an experiment I've tried to build -current and 14.2-stable on a Pi2 v1.1 running 12.4-stable. I know it's not considered good practice to hop that far, but I wanted to see for myself. I thought it would at least compile, since I have another Pi2v1.1 which has been tracking -current and is presently up-to-date. However, the build fails in both buildworld and toolchain, with /usr/src/contrib/file/src/apprentice.c:54:10: fatal error: 'byteswap.h' file not found #include ^~~~~~~~~~~~ The missing file is actually present: root@pelorus:/usr/src # find . -name byteswap.h -depth -print ./contrib/llvm-project/libcxx/include/__bit/byteswap.h ./contrib/ofed/include/byteswap.h ./include/byteswap.h root@pelorus:/usr/src # It's a little hard to see how using 12.4 might cause this sort of error. The source directory is a fresh clone. Is this an expected failure mode? If there's an easy workaround I'd like to try, but if not it's no big deal, I'll just reflash the microSD. Thanks for reading, and any insights. bob prohaska From nobody Mon Jan 6 20:15:55 2025 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 4YRln354D3z5k8hm for ; Mon, 06 Jan 2025 20:16:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YRln330Ksz4VX1 for ; Mon, 6 Jan 2025 20:16:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x636.google.com with SMTP id d9443c01a7336-2166651f752so15665475ad.3 for ; Mon, 06 Jan 2025 12:16:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1736194566; x=1736799366; 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=AKfGUHm7SKysiQ7c2aEFi5pG3gkyLJymkxrrnqmhEEI=; b=V0UPSQgUFtdq5Wj6FySS6cyviXP/Vma9RPR3FW7IPAikh82371fntDtTcVMO21rxEN +g0vHhnho4HYwSVEBMgPWsf6BHtZp4YY3amTda71IzrMPX483+p12WGjP3OUgApJssyJ LvqS7RqvWbMMnaWtO3JvkWpITQUgmxvCh8/LExvr2/kM9dEa8qAVl7iWl25PE6wyQIvU 7uf3AABbg0J0uLwJ1KWFz8DVMIuE2ygqSznYOBgf+r4DyktYW15pE/ytwRUmZCcnwb5c 5XxPlwtkkdN5ANJ9+lhJdVhJyJjUnhAyxwZ5mjQKWgGpU3Z/PhQyjfZB5CBfuefjdf4D mIjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736194566; x=1736799366; 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=AKfGUHm7SKysiQ7c2aEFi5pG3gkyLJymkxrrnqmhEEI=; b=HzPzCfye8ziwbZREPOsUusjqDTV7+XC5UdujAwrV/nd1gn+UGj4LBspGmbAEns1Ffh jjmFCkyQZeezqkV6adPc0NLdZXCNS0rtymJT+aUE1TAkx9o3fXk+sukoE1aaFy3iTT73 QHAceLsId5RpWM1l9C1bhbkRvSxZzq6877JCMlRZzJwyaJ/KRbOsNBpilQAMDPc+Iw3Q 8MgpoUV4IFdnW8Nhmkf06o4gjwIGUXgqsGbLmN1b/P3NU1uorrvN64ON+ElkoauvSDUN Kqv60IGFQhVnAQKpgrKL96XHMKXYWPLSr2OBGBIyqnK771wvIIDtxY7DJGXw/LTVYObc ei/w== X-Gm-Message-State: AOJu0YzlHo3ri8cPf3IkWVJn5VDDhe+oHp6OI4CDJ09UEadHMrWh+mX7 nWHzjWWKKGel7uvlaBTN1lFCMKg6eCyiJccluNvuFkb711ON00PhJDT8rbZKcJ2Wa6km3O6LXjN QRFGwFdGsC3seVm3p8xDQStzjqdmk6rWZ0NYZ4DowxSZAenB2KUKEPA== X-Gm-Gg: ASbGncs0EPWIAXgvaWojEPesVOZzcTqCdA7LHPWkxiAKV2/cXMck2zsLAmTApDw4eGM SIgbTKokKIn2ZSZVty6+1Q1AzQfKHRZhW2nINkQ== X-Google-Smtp-Source: AGHT+IEU1rQDtwq3NEWJFOffe+AeWnaLN0ziNk25jVu6ZMZ/pHRnLcyav7o58ag8XUKahvf29KMVsjFXe2voTDpR9Y8= X-Received: by 2002:a17:902:d589:b0:216:45b9:439b with SMTP id d9443c01a7336-219e6f28486mr850195835ad.50.1736194566223; Mon, 06 Jan 2025 12:16:06 -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: In-Reply-To: From: Warner Losh Date: Mon, 6 Jan 2025 13:15:55 -0700 X-Gm-Features: AbW1kvaavCn-mwltZL5XN2ZmkOTehfTe3to12jACXUC81Sra8-PxN7WJo6p9MqI Message-ID: Subject: Re: Buildworld fatal error: 'byteswap.h' file not found on armv7 To: bob prohaska Cc: freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="000000000000619428062b0f4cda" X-Rspamd-Queue-Id: 4YRln330Ksz4VX1 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] --000000000000619428062b0f4cda Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273736 for o= ne possible solution, though it focuses on 13.x. Warner On Mon, Jan 6, 2025 at 1:08=E2=80=AFPM bob prohaska wr= ote: > As an experiment I've tried to build -current and 14.2-stable > on a Pi2 v1.1 running 12.4-stable. I know it's not considered > good practice to hop that far, but I wanted to see for myself. > > I thought it would at least compile, since I have another Pi2v1.1 > which has been tracking -current and is presently up-to-date. > > However, the build fails in both buildworld and toolchain, with > /usr/src/contrib/file/src/apprentice.c:54:10: fatal error: 'byteswap.h' > file not found > #include > ^~~~~~~~~~~~ > > The missing file is actually present: > root@pelorus:/usr/src # find . -name byteswap.h -depth -print > ./contrib/llvm-project/libcxx/include/__bit/byteswap.h > ./contrib/ofed/include/byteswap.h > ./include/byteswap.h > root@pelorus:/usr/src # > > It's a little hard to see how using 12.4 might cause this sort of error. > The source directory is a fresh clone. > > Is this an expected failure mode? If there's an easy workaround I'd like > to try, but if not it's no big deal, I'll just reflash the microSD. > > Thanks for reading, and any insights. > > bob prohaska > > > > > > --000000000000619428062b0f4cda Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Please see=C2=A0https://bugs.freebsd.org/bugzilla/show_bug.cgi= ?id=3D273736 for one possible solution,
though it focuses on 13.x.<= /div>

Warner

On Mon, Jan 6, 2= 025 at 1:08=E2=80=AFPM bob prohaska <fbsd@www.zefox.net> wrote:
As an experiment I've tried to build -current and = 14.2-stable
on a Pi2 v1.1 running 12.4-stable. I know it's not considered
good practice to hop that far, but I wanted to see for myself.

I thought it would at least compile, since I have another Pi2v1.1
which has been tracking -current and is presently up-to-date.

However, the build fails in both buildworld and toolchain, with
/usr/src/contrib/file/src/apprentice.c:54:10: fatal error: 'byteswap.h&= #39; file not found
#include <byteswap.h>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~

The missing file is actually present:
root@pelorus:/usr/src # find . -name byteswap.h -depth -print
./contrib/llvm-project/libcxx/include/__bit/byteswap.h
./contrib/ofed/include/byteswap.h
./include/byteswap.h
root@pelorus:/usr/src #

It's a little hard to see how using 12.4 might cause this sort of error= .
The source directory is a fresh clone.

Is this an expected failure mode? If there's an easy workaround I'd= like
to try, but if not it's no big deal, I'll just reflash the microSD.=

Thanks for reading, and any insights.

bob prohaska





--000000000000619428062b0f4cda-- From nobody Mon Jan 6 23:21:18 2025 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 4YRqtj4pdNz5kP87 for ; Mon, 06 Jan 2025 23:21:17 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YRqth4tWVz40Nv for ; Mon, 6 Jan 2025 23:21:16 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 506NLJsq034210 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Jan 2025 15:21:19 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 506NLIad034209; Mon, 6 Jan 2025 15:21:18 -0800 (PST) (envelope-from fbsd) Date: Mon, 6 Jan 2025 15:21:18 -0800 From: bob prohaska To: Warner Losh Cc: freebsd-arm@freebsd.org Subject: Re: Buildworld fatal error: 'byteswap.h' file not found on armv7 Message-ID: References: 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 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Rspamd-Queue-Id: 4YRqth4tWVz40Nv 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:7065, ipnet:50.1.16.0/20, country:US] On Mon, Jan 06, 2025 at 01:15:55PM -0700, Warner Losh wrote: > Please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273736 for one > possible solution, > though it focuses on 13.x. > It doesn't seem to make a difference. Right now ./tools/build/cross-build/include/common/osreldate.h contains (apart from disclaimers): #pragma once #define __FreeBSD_version 0 -----the original file ended here----- #ifndef __APPLE__ #if __FreeBSD_version >= 1400079 || (__FreeBSD_version < 1400000 && __FreeBSD_version >= 1204600) #define HAVE_BYTESWAP_H 1 #endif #endif I tried commenting out the #define __FreeBSD_version 0 line thinking it might defeat the test, to no effect. I also dithered the last conditional value above and below the actual value of 1204500 to see if exact equality mattered. Finally I commented out the entire test, leaving only #define HAVE_BYTESWAP_H 1 to no avail. Unless I've done something really obvious wrong it's probably better to start over with a new snapshot so long as they're available and bootable. Thanks for writing! bob prohaska > > On Mon, Jan 6, 2025 at 1:08 PM bob prohaska wrote: > > > As an experiment I've tried to build -current and 14.2-stable > > on a Pi2 v1.1 running 12.4-stable. I know it's not considered > > good practice to hop that far, but I wanted to see for myself. > > > > I thought it would at least compile, since I have another Pi2v1.1 > > which has been tracking -current and is presently up-to-date. > > > > However, the build fails in both buildworld and toolchain, with > > /usr/src/contrib/file/src/apprentice.c:54:10: fatal error: 'byteswap.h' > > file not found > > #include > > ^~~~~~~~~~~~ > > > > The missing file is actually present: > > root@pelorus:/usr/src # find . -name byteswap.h -depth -print > > ./contrib/llvm-project/libcxx/include/__bit/byteswap.h > > ./contrib/ofed/include/byteswap.h > > ./include/byteswap.h > > root@pelorus:/usr/src # > > > > It's a little hard to see how using 12.4 might cause this sort of error. > > The source directory is a fresh clone. > > > > Is this an expected failure mode? If there's an easy workaround I'd like > > to try, but if not it's no big deal, I'll just reflash the microSD. > > > > Thanks for reading, and any insights. > > > > bob prohaska > > > > > > > > > > > > From nobody Thu Jan 9 10:42:17 2025 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 4YTLvc6LM1z5kY7m for ; Thu, 09 Jan 2025 10:42:20 +0000 (UTC) (envelope-from SRS0=qD07=UB=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YTLvc00xLz4hS1 for ; Thu, 9 Jan 2025 10:42:19 +0000 (UTC) (envelope-from SRS0=qD07=UB=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=e8ZvgaZ0; spf=pass (mx1.freebsd.org: domain of "SRS0=qD07=UB=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=qD07=UB=klop.ws=ronald-lists@realworks.nl"; dmarc=pass (policy=quarantine) header.from=klop.ws Date: Thu, 9 Jan 2025 11:42:17 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1736419337; 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: in-reply-to:in-reply-to:references:references; bh=kael1yv50ySGuRUBPe3A21lQR4ajsvKTbc8BPu3sdi4=; b=e8ZvgaZ0we/7rafjmtLoWrvqfc2a3lYFwYHPdAaM5ANZ9URyN1wH2SRApOgFz5ZgMR+bPh Z3b9G+c5pYPhhdSabBjVeGRiOWqJ/umgcvVaavvnM0/pNvXSmBVXu/CNiPxql+CigwSdeV mdaNEAW0r39ZQ4i9uchpLM1skhySNkzhOrwPesBi9M+qMZlFLyjqzVIiA7CmTCBk2Yo9Jc w87cwzswwlgmdrHPqxjkyK1PQkErHLwuValX4rp0dvpv5liSKOhO/b+VN5p+gAhr2/h7z4 r5UPDEebr4uIbr0Zbtc4CrjerFUTPcJCdphIN2X4NT5iizFYZN1OQ5/x5f/HqA== From: Ronald Klop To: Mark Millard Cc: freebsd-arm@freebsd.org, "Bjoern A. Zeeb" Message-ID: <1284671542.924.1736419337261@localhost> In-Reply-To: <68B36F4A-76AD-4CEC-ACBA-3EEF6863BB04@yahoo.com> References: <668r286o-584q-616o-5nq3-0233r3259qsr@yvfgf.mnoonqbm.arg> <7sp0np90-0rnn-n327-qps0-358493p411rs@yvfgf.mnoonqbm.arg> <68B36F4A-76AD-4CEC-ACBA-3EEF6863BB04@yahoo.com> Subject: Re: Raspbery Pi support (release notes/wiki page) update? 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 Content-Type: multipart/alternative; boundary="----=_Part_923_316014044.1736419337122" X-Mailer: Realworks (733.111) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4YTLvc00xLz4hS1 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.20 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; MID_RHS_NOT_FQDN(0.50)[]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=qD07=UB=klop.ws=ronald-lists@realworks.nl]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_NONE(0.00)[194.109.157.24:from]; TO_DN_SOME(0.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_TO(0.00)[yahoo.com]; RCPT_COUNT_THREE(0.00)[3]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=qD07=UB=klop.ws=ronald-lists@realworks.nl]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; HAS_X_PRIO_THREE(0.00)[3]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+] ------=_Part_923_316014044.1736419337122 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi Mark, I just noticed an RPI5 with 16GB RAM became available [1]. Which triggers my interest in an upgrade of my current RPI4/8GB used to build aarch64 ports. I see that you have quite some experience in setting up the RPI5 with knowledge expressed in several emails. Would you mind to setup a https://wiki.freebsd.org/arm/RPI5 page and collect your knowledge/experience there? When RPI5 works well in the future we can then merge the information into https://wiki.freebsd.org/arm/Raspberry%20Pi. Regards, Ronald. [1] https://www.raspberrypi.com/news/16gb-raspberry-pi-5-on-sale-now-at-120/ Van: Mark Millard Datum: maandag, 2 december 2024 22:43 Aan: "Bjoern A. Zeeb" CC: freebsd-arm@freebsd.org Onderwerp: Re: Raspbery Pi support (release notes/wiki page) update? > > On Dec 2, 2024, at 12:43, Bjoern A. Zeeb wrote: > > > On Wed, 27 Nov 2024, Mark Millard wrote: > > > > I assume that all also means there's no way on FreeBSD to update the > > eeprom contents on the RPi4/5[1] (contents replaced the bootcode.bin on > > older PIs.) > > I update the EEPROM's via booting a standard RaspiOS64 (my abbreviation). > That includes updating some defaults/definitions that can be stored in > the EEPROM. (For example, I enable more debug output than is the > default. That includes enabling BOOT_UART .) > > There are commands like: sudo -E rpi-eeprom-config --edit > > I'm not aware of FreeBSD having any such software, even via the ports > tree. > > However, the description of the command is: > > QUOTE > Editing the current bootloader configuration > The following command loads the current bootloader configuration into a text editor. When the editor is closed, rpi-eeprom-configapplies the updated configuration to latest available bootloader release and uses rpi-eeprom-update to schedule an update when the system is rebooted: > END QUOTE > > In essence doing a (after the edit): sudo rpi-eeprom-update -a > > I do not have the references handy, but as I remember, this puts a > file in the msdosfs that, if found at (re)boot, is automatically > used to do the EEPROM update, well before U-boot is involved. > > So: putting a correctly formed file in the right place with the > right name for a reboot to pick up is basic to the EEPROM update > operation. > > The EEPROM contains the bootloader. The RPi5B has less that goes > in the msdosfs (on the microsd card I use to boot the RPi5 via > a separate USB3 drive): > > # find /RPi5-edk2/ -print > /RPi5-edk2/ > /RPi5-edk2/RPI_EFI.fd > /RPi5-edk2/config.txt > /RPi5-edk2/bcm2712-rpi-5-b.dtb > > Nothing analogous to start4*.elf or fixup4*.dat is involved. > > # more /RPi5-edk2/config.txt > armstub=RPI_EFI.fd > device_tree_address=0x1f0000 > device_tree_end=0x210000 > > # Force 32 bpp framebuffer allocation. > framebuffer_depth=32 > > # Disable compensation for displays with overscan. > disable_overscan=1 > > # Force maximum USB power regardless of the power supply. > usb_max_current_enable=1 > > # Force maximum CPU speed. > force_turbo=1 > > # > # Local additions: > enable_uart=1 > uart_2ndstage=1 > dtdebug=1 > disable_commandline_tags=1 > # > [pi5] > over_voltage_delta=100000 > arm_freq=2600 > [all] > > > /bz > > > > > > [1] https://github.com/raspberrypi/rpi-eeprom/tree/master/ > > Releases: https://github.com/raspberrypi/rpi-eeprom/releases > > Tagged: https://github.com/raspberrypi/rpi-eeprom/tags > > (More is tagged than is eventually declared to also be a > release.) > > === > Mark Millard > marklmi at yahoo.com > > > > > ------=_Part_923_316014044.1736419337122 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Mark,

I just noticed an RPI5 with 16GB RAM became available [1]. Which triggers my interest in an upgrade of my current RPI4/8GB used to build aarch64 ports.

I see that you have quite some experience in setting up the RPI5 with knowledge expressed in several emails.
Would you mind to setup a https://wiki.freebsd.org/arm/RPI5 page and collect your knowledge/experience there?

When RPI5 works well in the future we can then merge the information into https://wiki.freebsd.org/arm/Raspberry%20Pi.

Regards,
Ronald.

[1] https://www.raspberrypi.com/news/16gb-raspberry-pi-5-on-sale-now-at-120/
 

Van: Mark Millard <marklmi@yahoo.com>
Datum: maandag, 2 december 2024 22:43
Aan: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
CC: freebsd-arm@freebsd.org
Onderwerp: Re: Raspbery Pi support (release notes/wiki page) update?

On Dec 2, 2024, at 12:43, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote:

> On Wed, 27 Nov 2024, Mark Millard wrote:
>
> I assume that all also means there's no way on FreeBSD to update the
> eeprom contents on the RPi4/5[1] (contents replaced the bootcode.bin on
> older PIs.)

I update the EEPROM's via booting a standard RaspiOS64 (my abbreviation).
That includes updating some defaults/definitions that can be stored in
the EEPROM. (For example, I enable more debug output than is the
default. That includes enabling BOOT_UART .)

There are commands like: sudo -E rpi-eeprom-config --edit

I'm  not aware of FreeBSD having any such software, even via the ports
tree.

However, the description of the command is:

QUOTE
Editing the current bootloader configuration
The following command loads the current bootloader configuration into a text editor. When the editor is closed, rpi-eeprom-configapplies the updated configuration to latest available bootloader release and uses rpi-eeprom-update to schedule an update when the system is rebooted:
END QUOTE

In essence doing a (after the edit): sudo rpi-eeprom-update -a

I do not have the references handy, but as I remember, this puts a
file in the msdosfs that, if found at (re)boot, is automatically
used to do the EEPROM update, well before U-boot is involved.

So: putting a correctly formed file in the right place with the
right name for a reboot to pick up is basic to the EEPROM update
operation.

The EEPROM contains the bootloader. The RPi5B has less that goes
in the msdosfs (on the microsd card I use to boot the RPi5 via
a separate USB3 drive):

# find /RPi5-edk2/ -print
/RPi5-edk2/
/RPi5-edk2/RPI_EFI.fd
/RPi5-edk2/config.txt
/RPi5-edk2/bcm2712-rpi-5-b.dtb

Nothing analogous to start4*.elf or fixup4*.dat is involved.

# more /RPi5-edk2/config.txt
armstub=RPI_EFI.fd
device_tree_address=0x1f0000
device_tree_end=0x210000

# Force 32 bpp framebuffer allocation.
framebuffer_depth=32

# Disable compensation for displays with overscan.
disable_overscan=1

# Force maximum USB power regardless of the power supply.
usb_max_current_enable=1

# Force maximum CPU speed.
force_turbo=1

#
# Local additions:
enable_uart=1
uart_2ndstage=1
dtdebug=1
disable_commandline_tags=1
#
[pi5]
over_voltage_delta=100000
arm_freq=2600
[all]

> /bz
>
>
> [1] https://github.com/raspberrypi/rpi-eeprom/tree/master/

Releases: https://github.com/raspberrypi/rpi-eeprom/releases

Tagged: https://github.com/raspberrypi/rpi-eeprom/tags

(More is tagged than is eventually declared to also be a
release.)

===
Mark Millard
marklmi at yahoo.com

 


  ------=_Part_923_316014044.1736419337122-- From nobody Thu Jan 9 16:21:43 2025 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 4YTVTr3Cskz5l44Z for ; Thu, 09 Jan 2025 16:24:00 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-48.consmr.mail.gq1.yahoo.com (sonic310-48.consmr.mail.gq1.yahoo.com [98.137.69.174]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YTVTq4ZKcz4Nfq for ; Thu, 9 Jan 2025 16:23:59 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1736439836; bh=VKGm7fSTQhFQkxU8xzX0cnPwEzRWsBN1s7LekR5H5fo=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=HgOe6bf0Iz+Pdo+KfxdHveRCjYPJozbu90m2Ihmzbo/HZa3rMsJAsY5Szk9EGKwQWgd9CWgct0z6DJmwLgupo5k0nYJbY8vh33iURrKIhTm8i5NvT+dPlu8TjVAj30he8mWHPcA4YMnqDku1dXKm0knLNjWh6q66yLDC4wxexZ+y5iVBNDyCKWr/+rwyxLZjWZoHMd9MNalI4XNLOpeBTy5z9gzuj1UYXZHPkxPIVRbJOn7OvOnZ0ODsnrlnBjpW16MSvgVWmE2CKEeqnAVZEtuEphT/CcYCzJ3KGv8jje/L3t0/6E6i00hJ9s4AzlPXPUGMqNagdlV8ysyU9isiqg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1736439836; bh=inZSZyTxxkmjz/TJmCcoXdw5faDcXHwNQ40nWKHARnP=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=E3o1oU8P0154NhwvU1hbWlgsZ9ZkwC+RBmLryi5IHYiNIwYWdT/vT7va3lgxcLtNB5CnlxlJ/yJKcCBUHxH95dnq8xKhCGPAuNXPhCpSJuOAvGDoP3weaX2nlcCDQgqjtNvYvnFozxWy+C8/WNulXN6X6CJDtbsQbQJoWEabAJo+CIpkRParJ7Crgzo2VR3icg+fYksSJ/VJgvTkhC+2XvzomlR88kCBhRONoGFMQb7iZ2MiLcOPnmMzP13KO98cKRYKN7Bl7NaN5ldIbNoZyE4StDYzCbInZ7csfDFSrxkR4G7k/xm7Hc3jdpv7D5eSYXYh8pft78bNDgFFs14Kjg== X-YMail-OSG: 04.zuyUVM1lIfcO3fK5Mxyuoe_KweC7vmNYOBOZxYTx.DQX.VNOO8O7.Nm38QPG 83xPQOmwoU3Y9Qim2pjHqOdhRJExrH4J68et65fc8xfoSGYgzGropJKmFl0ZPCJnCYGHXYI7oTMV lq5P6.7W5yABNA2WM7yjaGXS5x83xJA5bkVzKXVc44rguvGDjrXW6NQ_Qb3441jh5qk09Ds2xvQt 2KpAgp_HsLeHxmgQjk7vqVZbtLaZ6vpcvBP9how.GtK5JoXzj1Toq2XVMPgESiF667mPwMcdQk.u .sa25A1NvEQI2zZFdx0bCphkzkcnYzCiyMOLNsTJaxKHvp_6pXhUu___VAAObyaWU.82qn0Ut6iF H9Z_m4jvesK3v6YqkPAT3tcjPowRcDn2WP0eOaxdQFthOh_TRqBYOoyIQC8NBwwkgQ8TJvaL1teO 3uMxkyH3ZIJisFAlDC59oq4dg0B8lO573YVdC_RFmFiPdfYljCKsPzH6N3m_NfT3QRdNGO9oioWC cUDzzWKVey4uY17QW3Nfiw621v5YhczTOa8xlUuVPFITY.oB9xAJaKdpNZ0LrA1DKO7WuDZCtQrf DgdSQ7xOhlwGNUw5mkl16kc3NeRiN.iqCyL7rWJzgPVH1MNkPIqeAzr_aytQAFqSfZINwoDHTo9n DZ7uP2rcNz96xjlMHbmwr4UX7SbNtExLq.qRhEo1OEUak8WyS76WRLw5R1WUGMxYNiNG5b9Zkjdi KFSQePr4rSRXgrTL.V8HmAn9StoilsY_MQuHlvVx5iRw3h2QdDNZJiiDIbIsOrteuo3tExPJZEsD vJnXg_n0TqFmxlmQYDTSMctFT478MkzF31ITRWrIsZbhmVX1sGZvJ8fTkqAUitalmzFNk0p.eDV8 bakx01akObWEJX8zMwJZvAIXPVWBtRqrf.HGs26qxg7.oWvC6sx.Nq96JGLAa_fbJjuMAxRChRmb AZtE1QGpKIx_7iEhiHhiwTajpBmGnQ2.STctxromAID5Y.U1qjVRsK2LZq.p84XJxRYYk3YNl2oM tNwMmA6XzLxdyv7srn4eE5m74nZkZo0sVtVRYiN4zIQHT0164uaGtBA3B7CuU1prQXz1wrd8ObPu QK.K4Dn2YRXx0efiY.Fi0awf_SMsi6NCX3eVE5foEyOoQAb2G2drvfubzVwuBwh_uf30K4JLfNYZ VH3f_gc6oAozmKIffmq7YsDFn5CUw8Akfuj4DaO32pOk02KV6D3mm5Fh3CC9t6J_E6uJyaCTU5Q_ USZn6gCEosOcikJug5P2a4U9FShqtOH9r1OuJUQDLMuKB7BoJ_8LzpEnCutRCkapLvJ2BvhVVmHp w7H52wbPuHNd209KazcCyCsE7H2x0.flDNSwUJtoP3cnlUHa0M8k.solKh_MJq9kSLlvaHPeMb4q I_rCB8BPq_6pOjVadxmQ2eWyRKzYHZs60y_wEWSTc6K9hsvpMDFT1l3D3A7LpFxjdXOhWnUORQXY T1N45yuLkb4TbdxUUgSHamMeOn1vKAPBTPxOPByQwLcd1ndWg1oYHRcarRFMSp.HuFTTU8OQo_u9 LPKPjwfmzhdHizYGfceWBZHZzSUUvuraYybZZE.f6YgZmj2q35G7p38NN7I6FIMvVUGjhm7Md_Aj RNJpO1c5Mcz4jCzjrx2JB2glxlbMr8HG.LNGL935bB5J4mIL.MsRtrA.ZDvfYIFdsvD65hl3.i4u I4pHK0L4QMahLrtAn4H3yuLI4hq5u3b_2onWavqgHJ2YDp4c2JGYe8j1c1HVj6Uguw13pG33XJB4 ilZ3wHeSR0MC1.xvHRI9vO5O4iT5lvRhNEGZT4sIaWjC_WbJnvCkDPU_qlqzdxuhlZTcKjSH0Key gbqTtajLIPaCWRkfMMIT5YnVemoUZKXuEf.mchiAb7oECZDpI__L9efJSu_VCsH8Ie4pICiD5jZj zgC8ir7bu1oOKep_Kj3c_FYZ3g2DzltEmhivcisyPDJm1uN4hNkBBKTbgQkHqhywZeBdH3QX6jRd wCzZHiuFrJO1rvkAAaLfnFE_BlBSdp8pT4TQwpNmlK8UQKm0Y63il.SzdzeUA0xQZWbLRxPXYHIh sF.dMKyOwCabKGkK1v2LrC4yvQwl6IqU80KFCqzI76oHnXpoWmFIic8dPM4_RQVW2fXuZ3Fu2Vx. 9OTh5Us3H3WQtcnDa2Ysgk.sofyeUXiv4pwDSIXz3E8tDb8tc5EuES9BFzyXjCzE_bigTPzfwMAJ F1Hsu4wvNDzapY61O5jRD2r.r2M9rnZmmWtU1a6T2r58JWFUaiwLGx69HXYdnIhw- X-Sonic-MF: X-Sonic-ID: 3fd12f9b-159f-4407-a524-c2413b0a92f3 Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Thu, 9 Jan 2025 16:23:56 +0000 Received: by hermes--production-gq1-5dd4b47f46-zz6g6 (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 92b5b411685c95f678f1b33ad6b62b3f; Thu, 09 Jan 2025 16:21:55 +0000 (UTC) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 \(3826.300.87.4.3\)) Subject: Re: Raspbery Pi support (release notes/wiki page) update? From: Mark Millard X-Priority: 3 (Normal) In-Reply-To: <1284671542.924.1736419337261@localhost> Date: Thu, 9 Jan 2025 08:21:43 -0800 Cc: freebsd-arm@freebsd.org, "Bjoern A. Zeeb" Content-Transfer-Encoding: quoted-printable Message-Id: References: <668r286o-584q-616o-5nq3-0233r3259qsr@yvfgf.mnoonqbm.arg> <7sp0np90-0rnn-n327-qps0-358493p411rs@yvfgf.mnoonqbm.arg> <68B36F4A-76AD-4CEC-ACBA-3EEF6863BB04@yahoo.com> <1284671542.924.1736419337261@localhost> To: Ronald Klop X-Mailer: Apple Mail (2.3826.300.87.4.3) X-Rspamd-Queue-Id: 4YTVTq4ZKcz4Nfq 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:36647, ipnet:98.137.64.0/20, country:US] Hello Ronald, I'm away from all FreeBSD system access for a couple of weeks, doing things that need to take priority on my time. I do know that https://github.com/worproject/rpi5-uefi is not being actively updated by anyone, including its original author. It (in ACPI mode) is the only way I know how to FreeBSD-boot the only RPi5 that I (usually) have access to. Relative to the author's notes about the status, see: = https://github.com/worproject/rpi5-uefi/issues/18#issuecomment-2080098959 It says, in part: "I'm not actively working on it, but this doesn't mean it's dead - contributions are welcome." No contributions have been made. The last commit was on 2024-Mar-15. It also reports, relative to the (failed/incomplete) upstreaming: QUOTE (2024-Apr-26 material): =E2=80=A2 The TF-A port is upstreamed, minus one PCI patch that's = waiting on review. =E2=80=A2 I've also submitted the patches in my EDK2 base fork back in January, but I haven't heard anything since. The EDK2 review process is slow in general, at times non-existent (understandably, not many maintainers), so I just gave up on that idea. END QUOTE I also know that https://github.com/worproject/rpi5-uefi will not recognize the 16 GiByte of memory: The board revision code was used to assign the memory size. There is no use of anything that would track total_mem from config.txt . (That, in turn, controls what the live-dtb indicates for memory size and layout issues as I understand.) See: https://github.com/worproject/rpi5-uefi/issues/12 . Sorry for the news, Mark On Jan 9, 2025, at 02:42, Ronald Klop wrote: Hi Mark, I just noticed an RPI5 with 16GB RAM became available [1]. Which = triggers my interest in an upgrade of my current RPI4/8GB used to build = aarch64 ports. I see that you have quite some experience in setting up the RPI5 with = knowledge expressed in several emails. Would you mind to setup a https://wiki.freebsd.org/arm/RPI5 page and = collect your knowledge/experience there? When RPI5 works well in the future we can then merge the information = into https://wiki.freebsd.org/arm/Raspberry%20Pi. Regards, Ronald. [1] = https://www.raspberrypi.com/news/16gb-raspberry-pi-5-on-sale-now-at-120/ Van: Mark Millard Datum: maandag, 2 december 2024 22:43 Aan: "Bjoern A. Zeeb" CC: freebsd-arm@freebsd.org Onderwerp: Re: Raspbery Pi support (release notes/wiki page) update? On Dec 2, 2024, at 12:43, Bjoern A. Zeeb = wrote: > On Wed, 27 Nov 2024, Mark Millard wrote: > > I assume that all also means there's no way on FreeBSD to update the > eeprom contents on the RPi4/5[1] (contents replaced the bootcode.bin = on > older PIs.) I update the EEPROM's via booting a standard RaspiOS64 (my = abbreviation). That includes updating some defaults/definitions that can be stored in the EEPROM. (For example, I enable more debug output than is the default. That includes enabling BOOT_UART .) There are commands like: sudo -E rpi-eeprom-config --edit I'm not aware of FreeBSD having any such software, even via the ports tree. However, the description of the command is: QUOTE Editing the current bootloader configuration The following command loads the current bootloader configuration into a = text editor. When the editor is closed, rpi-eeprom-configapplies the = updated configuration to latest available bootloader release and uses = rpi-eeprom-update to schedule an update when the system is rebooted: END QUOTE In essence doing a (after the edit): sudo rpi-eeprom-update -a I do not have the references handy, but as I remember, this puts a file in the msdosfs that, if found at (re)boot, is automatically used to do the EEPROM update, well before U-boot is involved. So: putting a correctly formed file in the right place with the right name for a reboot to pick up is basic to the EEPROM update operation. The EEPROM contains the bootloader. The RPi5B has less that goes in the msdosfs (on the microsd card I use to boot the RPi5 via a separate USB3 drive): # find /RPi5-edk2/ -print /RPi5-edk2/ /RPi5-edk2/RPI_EFI.fd /RPi5-edk2/config.txt /RPi5-edk2/bcm2712-rpi-5-b.dtb Nothing analogous to start4*.elf or fixup4*.dat is involved. # more /RPi5-edk2/config.txt armstub=3DRPI_EFI.fd device_tree_address=3D0x1f0000 device_tree_end=3D0x210000 # Force 32 bpp framebuffer allocation. framebuffer_depth=3D32 # Disable compensation for displays with overscan. disable_overscan=3D1 # Force maximum USB power regardless of the power supply. usb_max_current_enable=3D1 # Force maximum CPU speed. force_turbo=3D1 # # Local additions: enable_uart=3D1 uart_2ndstage=3D1 dtdebug=3D1 disable_commandline_tags=3D1 # [pi5] over_voltage_delta=3D100000 arm_freq=3D2600 [all] > /bz > > > [1] https://github.com/raspberrypi/rpi-eeprom/tree/master/ Releases: https://github.com/raspberrypi/rpi-eeprom/releases Tagged: https://github.com/raspberrypi/rpi-eeprom/tags (More is tagged than is eventually declared to also be a release.) =3D=3D=3D Mark Millard marklmi at yahoo.com =20 =20 =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Thu Jan 9 17:53:52 2025 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 4YTXTY1dQDz5jj8H for ; Thu, 09 Jan 2025 17:53:53 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YTXTW4fndz4XC1 for ; Thu, 9 Jan 2025 17:53:51 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net; dmarc=none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 509Hrqkc050207 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Thu, 9 Jan 2025 09:53:53 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 509HrqQV050206 for freebsd-arm@freebsd.org; Thu, 9 Jan 2025 09:53:52 -0800 (PST) (envelope-from fbsd) Date: Thu, 9 Jan 2025 09:53:52 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: [Bug 273566] stray characters contaminate serial console Message-ID: References: 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 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Rspamd-Queue-Id: 4YTXTW4fndz4XC1 X-Spamd-Bar: / X-Spamd-Result: default: False [-0.25 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; NEURAL_HAM_SHORT(-0.15)[-0.152]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; DMARC_NA(0.00)[zefox.net]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; R_SPF_NA(0.00)[no SPF record] On Thu, Jan 09, 2025 at 12:36:42PM +0000, bugzilla-noreply@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273566 > > --- Comment #6 from Sulev-Madis Silber --- > i messed with things on purpose to see if they break and they did > > ftdi isolates usb ttl adapter is connected with usb end at 13.4 on amd64 and > serial end at current on armv7 > > login via serial using cu, to the armv7 board, then kill cu > > then, with ssh i execute: > > sh -c 'while :; do : | wall; done' > > on said armv7 device > > let some time pass and run cu on port again > > this is what shell history has: > > 41 14:20 Broadcast Message from root@ask-m-001 ^G^G > 42 14:20 ( /dev/pts/0 ) at 14:19 EET... > ^@BBBBBBBBBBBBBJBBBBBBgBBBB^_BBBBBBBB > BBJBBBBBBFBBBBBBwBBBB^_BBBBBBBBBBJBBBBBBFBBBBBBgB^@ > 43 14:20 h > 14:20,root@ask-m-001:~# > > is this what you experience? In short, yes, the usb end is on armv7, the serial end is arm64 : bob@nemesis:~ % Broadcast Message from bob@nemesis.zefox.com ^G^G Broadcast: Command not found. bob@nemesis:~ % bob@nemesis:~ % bob@nemesis:~ % bob@nemesis:~ % bob@nemesis:~ % bob@nemesis:~ % (/dev/pts/1) at KBBBFBBBBBBBBBBBBBBBBBBBBgëB×BBBBBBBBBBBBBBNBBBBBBfgëB×BBBBBBBBBBBBBBNBBBBB^@ Badly placed ()'s. I did this by dropping the cu connection to arm64 using ~~., using your wall command briefly, killing it with control-c and then picking up the serial connection. Recalling history on the serial (arm64) end I see 999 7:13 su 1000 19:41 exit 1001 9:17 h 1002 9:19 Broadcast Message from bob@nemesis.zefox.com ^G^G 1003 9:21 ( /dev/pts/1 ) at KBBBFBBBBBBBBBBBBBBBBBBBBgëB×BBBBBBBBBBBBBBNBBBBBBfgëB×BBBBBBBBBBBBBBNBBBBB^@ 1004 9:25 h bob@nemesis:~ % It appears that only one instance of "leakage" into the serial-end command history occurs through the duration of the wall transmissiion. Thanks for writing! bob prohaska From nobody Thu Jan 9 19:31:33 2025 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 4YTZfQ27y6z5jt6D for ; Thu, 09 Jan 2025 19:31:42 +0000 (UTC) (envelope-from pjfloyd@wanadoo.fr) Received: from smtp.smtpout.orange.fr (smtp-71.smtpout.orange.fr [80.12.242.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.smtpout.orange.fr", Issuer "DigiCert Global G2 TLS RSA SHA256 2020 CA1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YTZfN5yP8z4lC1 for ; Thu, 9 Jan 2025 19:31:40 +0000 (UTC) (envelope-from pjfloyd@wanadoo.fr) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=wanadoo.fr header.s=t20230301 header.b=AEfRJOtH; spf=pass (mx1.freebsd.org: domain of pjfloyd@wanadoo.fr designates 80.12.242.71 as permitted sender) smtp.mailfrom=pjfloyd@wanadoo.fr; dmarc=pass (policy=quarantine) header.from=wanadoo.fr Received: from [192.168.1.28] ([90.18.202.102]) by smtp.orange.fr with ESMTPA id VyFhtZ554cGVxVyFktzQyX; Thu, 09 Jan 2025 20:31:38 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wanadoo.fr; s=t20230301; t=1736451098; bh=V+Tk5sTS3CLdysE9JjaBkpfttpZ4uFeAPg+/UT/g8+w=; h=Message-ID:Date:MIME-Version:Subject:To:From; b=AEfRJOtH1Ro+0Br8avnsqm+pG6bqZWSiAMZ7cyPrPVyPcmHk2MuDm5tajShU/ikzF xydhivjXd6bNGT6h7OW0db2OqqUB+fHHLryIQaDgc7wfmCx2Jh25RnuS0h12GHsIeU y9GjIAlNshXWyxE6Vix8CruO00zg8wMGTv/vb8ywoE4mQkpA/PtpDeTmJF4py4JHtC MfObrS7h5SB3vjnwpWLcASpF2vH7LYfO3H/ajn3Ov5oHWi4ih3PnnTu7+oVZVUnfVb HFnZv2AZ2PUG3qD1hI8tK4cIfharxvYbZ72mSrqF+iZFdILnIJDHvyd+hMDwAanjHh 43gcsusQLgytA== X-ME-Helo: [192.168.1.28] X-ME-Auth: cGpmbG95ZEB3YW5hZG9vLmZy X-ME-Date: Thu, 09 Jan 2025 20:31:38 +0100 X-ME-IP: 90.18.202.102 Message-ID: <51c72f9e-19fc-4cf6-8bb8-dacb97b9b793@wanadoo.fr> Date: Thu, 9 Jan 2025 20:31:33 +0100 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 User-Agent: Mozilla Thunderbird Subject: Re: Raspbery Pi support (release notes/wiki page) update? To: freebsd-arm@freebsd.org References: <668r286o-584q-616o-5nq3-0233r3259qsr@yvfgf.mnoonqbm.arg> <7sp0np90-0rnn-n327-qps0-358493p411rs@yvfgf.mnoonqbm.arg> <68B36F4A-76AD-4CEC-ACBA-3EEF6863BB04@yahoo.com> <1284671542.924.1736419337261@localhost> Content-Language: en-GB From: Paul Floyd In-Reply-To: <1284671542.924.1736419337261@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4YTZfN5yP8z4lC1 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.09 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[wanadoo.fr,quarantine]; RWL_MAILSPIKE_VERYGOOD(-0.20)[80.12.242.71:from]; R_DKIM_ALLOW(-0.20)[wanadoo.fr:s=t20230301]; R_SPF_ALLOW(-0.20)[+ip4:80.12.242.0/25]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[wanadoo.fr:dkim]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_FROM(0.00)[wanadoo.fr]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[wanadoo.fr]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[wanadoo.fr:+]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:3215, ipnet:80.12.240.0/20, country:FR]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[80.12.242.71:from] On 09-01-25 11:42, Ronald Klop wrote: > Hi Mark, > > I just noticed an RPI5 with 16GB RAM became available [1]. Which > triggers my interest in an upgrade of my current RPI4/8GB used to build > aarch64 ports. > > I see that you have quite some experience in setting up the RPI5 with > knowledge expressed in several emails. > Would you mind to setup a https://wiki.freebsd.org/arm/RPI5 wiki.freebsd.org/arm/RPI5> page and collect your knowledge/experience there? I just made a start: https://wiki.freebsd.org/arm/Raspberry%20Pi%205 A+ Paul From nobody Fri Jan 10 05:37:42 2025 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 4YTr5w5Cy9z5knkR for ; Fri, 10 Jan 2025 05:37:56 +0000 (UTC) (envelope-from freebsd-arm-freebsd-org097@ketas.si.pri.ee) Received: from mail.ketas.si.pri.ee (d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13e8:21e:bff:fea2:d004]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YTr5t6Hycz4kNx for ; Fri, 10 Jan 2025 05:37:54 +0000 (UTC) (envelope-from freebsd-arm-freebsd-org097@ketas.si.pri.ee) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ketas.si.pri.ee header.s=ketas-si-pri-ee-20240416002854-4096 header.b=iJyjWMPu; spf=pass (mx1.freebsd.org: domain of freebsd-arm-freebsd-org097@ketas.si.pri.ee designates 2001:7d0:8437:13e8:21e:bff:fea2:d004 as permitted sender) smtp.mailfrom=freebsd-arm-freebsd-org097@ketas.si.pri.ee; dmarc=pass (policy=reject) header.from=ketas.si.pri.ee X-Original-To: freebsd-arm@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ketas.si.pri.ee; s=ketas-si-pri-ee-20240416002854-4096; t=1736487464; bh=UzY0NzThYifoCQ2RrglQFSk/AAyer7Gzjo3HGKWaHSM=; h=Date:From:To:Subject:In-Reply-To:References; b=iJyjWMPuaa8irBtOmTBM40VBTJyI6QKETsPvL5mG8IFAnU3zkRcyI0de1S1Tvptkc 2Oz1FZnOkLwzFSW6v2Kl8XX8OpHYSkM/BzaAb7M8WXKaeyq4bS25Sg1lkRK26yOt3t M0D0MVy2dCxpKGTEfGw68sKb8biCzmPhYDHE+AUhWT+ZwSS55FUZNcbhIELMC6SeHY DRbH+KcKAvTtXw0KgXAKoJRBgSeYlD9oAe9iyqRuEHwdIrEaz/CXiJsg8+rkS9qkav 6AJnFoQJlX9thtptZeVoplnlPUmjxERvaz+HkYj/euG9O0Q5HEutIWM9xUklCeC12I 8abPTW8H+rcYFzaqgUQtrBToUCH+2R/gXL/sZ8Y4Qtost1GhN0Sjzuvt/WWP09dkgB 5yRk0uHKQBjt5Zm4tmpzif6Vd5enPoPgxxxdS0rotUEvi3aFp9kW6Kuo8dRZVPvEmt fP8WxIVaO/IL6i2eFWiDYPKTlh72RdOitpEMvlp+Gw/NeYLe+CsyFzYtP01RZwEhxI mvc4PLDc15/1OE/uGHOA2BUBXn6YtmMnmopH4dBAazGl6Y/r4tdMV6WQEB2+0OzkTK xMxHFzHz1pKxa8LwkYaZjVbGN+VT//jQJpj/Ims5Jw126gUCGjnkd/F6b7n8wbax5d BG1BzgzXjolJbKKKm85mrv9Q= Received: from [IPv6:::1] (0114-0000-0000-0000-13c8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13c8::114]) (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) (No client certificate requested) by mail.ketas.si.pri.ee (Postfix) with ESMTPSA id 4E5495AF2F9 for ; Fri, 10 Jan 2025 07:37:44 +0200 (EET) Date: Fri, 10 Jan 2025 07:37:42 +0200 From: Sulev-Madis Silber To: freebsd-arm@freebsd.org Subject: Re: [Bug 273566] stray characters contaminate serial console User-Agent: K-9 Mail for Android In-Reply-To: References: Message-ID: 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 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4YTr5t6Hycz4kNx X-Spamd-Bar: / X-Spamd-Result: default: False [-0.90 / 15.00]; HFILTER_HOSTNAME_5(3.00)[d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.995]; DMARC_POLICY_ALLOW(-0.50)[ketas.si.pri.ee,reject]; R_SPF_ALLOW(-0.20)[+ip6:2001:7d0:8437:1300::/56]; R_DKIM_ALLOW(-0.20)[ketas.si.pri.ee:s=ketas-si-pri-ee-20240416002854-4096]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:3249, ipnet:2001:7d0::/32, country:EE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[ketas.si.pri.ee:+] not sure if this is even this arm mailing list topic but problem exists=2E = and the more i try to push it, the more it fails From nobody Fri Jan 10 09:03:45 2025 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 4YTwgS5d67z5jvDS for ; Fri, 10 Jan 2025 09:03:48 +0000 (UTC) (envelope-from SRS0=4Fcw=UC=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YTwgS3Xjfz45JT for ; Fri, 10 Jan 2025 09:03:48 +0000 (UTC) (envelope-from SRS0=4Fcw=UC=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Fri, 10 Jan 2025 10:03:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1736499825; 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: in-reply-to:in-reply-to:references:references; bh=8bAER16huP3ca7/5IHbDoJ4IZ4WoomFHxdMcKLVUmJ4=; b=xWZ35nTe83jaVymoEI7E05Hs96ZAlwMurEJDn/Z2C2+7gZOAbPDygo0M7/6Q1MMAUlKHhl vTEnyAZDDJSLljMlpfoFh3ZoDbZKZJEy1xjk8vCavqKL8f0zahlaEP+ZtGP+XQZGeoND/b bY/9YaSHunpaqII2CnOBJYiEjSUu4IcAb6vNNjlLYBfhVXTMc6SAeZt2uupG1KrlyLat2o 7zTnTwGBNUMrP6YyPvUmEkqaENFMdhxxq3ztUECokQZ1kbxjJUl2F3NA2ycuLxfxMG6mOs +79pncalWCQLQKHQkhoYd3VhupFPn8NzfIRvpMUa/vaLWKGEEmlIgROo9ADUkQ== From: Ronald Klop To: Paul Floyd Cc: freebsd-arm@freebsd.org Message-ID: <881635894.2479.1736499825338@localhost> In-Reply-To: <51c72f9e-19fc-4cf6-8bb8-dacb97b9b793@wanadoo.fr> References: <668r286o-584q-616o-5nq3-0233r3259qsr@yvfgf.mnoonqbm.arg> <7sp0np90-0rnn-n327-qps0-358493p411rs@yvfgf.mnoonqbm.arg> <68B36F4A-76AD-4CEC-ACBA-3EEF6863BB04@yahoo.com> <1284671542.924.1736419337261@localhost> <51c72f9e-19fc-4cf6-8bb8-dacb97b9b793@wanadoo.fr> Subject: Re: Raspbery Pi support (release notes/wiki page) update? (RPI5) 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 Content-Type: multipart/alternative; boundary="----=_Part_2478_66504177.1736499825335" X-Mailer: Realworks (733.112) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4YTwgS3Xjfz45JT 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:3265, ipnet:194.109.0.0/16, country:NL] ------=_Part_2478_66504177.1736499825335 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Paul Floyd Datum: donderdag, 9 januari 2025 20:31 Aan: freebsd-arm@freebsd.org Onderwerp: Re: Raspbery Pi support (release notes/wiki page) update? > > > On 09-01-25 11:42, Ronald Klop wrote: > > Hi Mark, > > > > I just noticed an RPI5 with 16GB RAM became available [1]. Which > triggers my interest in an upgrade of my current RPI4/8GB used to build > aarch64 ports. > > > > I see that you have quite some experience in setting up the RPI5 with > knowledge expressed in several emails. > > Would you mind to setup a https://wiki.freebsd.org/arm/RPI5 wiki.freebsd.org/arm/RPI5> page and collect your knowledge/experience there? > > > I just made a start: > https://wiki.freebsd.org/arm/Raspberry%20Pi%205 > > A+ > Paul > > > > > Thank you very much! Just ordered a RPI5. Regards, Ronald. ------=_Part_2478_66504177.1736499825335 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Van: Paul Floyd <pjfloyd@wanadoo.fr>
Datum: donderdag, 9 januari 2025 20:31
Aan: freebsd-arm@freebsd.org
Onderwerp: Re: Raspbery Pi support (release notes/wiki page) update?



On 09-01-25 11:42, Ronald Klop wrote:
> Hi Mark,
>
> I just noticed an RPI5 with 16GB RAM became available [1]. Which > triggers my interest in an upgrade of my current RPI4/8GB used to build > aarch64 ports.
>
> I see that you have quite some experience in setting up the RPI5 with > knowledge expressed in several emails.
> Would you mind to setup a https://wiki.freebsd.org/arm/RPI5 <https:// > wiki.freebsd.org/arm/RPI5> page and collect your knowledge/experience there?


I just made a start:
https://wiki.freebsd.org/arm/Raspberry%20Pi%205

A+
Paul

 



Thank you very much!
Just ordered a RPI5.

Regards,
Ronald.
  ------=_Part_2478_66504177.1736499825335-- From nobody Fri Jan 10 16:06:46 2025 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 4YV63R1MLSz5kZFS for ; Fri, 10 Jan 2025 16:06:43 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YV63Q4c8Zz3wfQ for ; Fri, 10 Jan 2025 16:06:42 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 50AG6nLV054272 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 10 Jan 2025 08:06:49 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 50AG6kkT054271; Fri, 10 Jan 2025 08:06:46 -0800 (PST) (envelope-from fbsd) Date: Fri, 10 Jan 2025 08:06:46 -0800 From: bob prohaska To: Sulev-Madis Silber Cc: freebsd-arm@freebsd.org Subject: Re: [Bug 273566] stray characters contaminate serial console Message-ID: References: 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4YV63Q4c8Zz3wfQ 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:7065, ipnet:50.1.16.0/20, country:US] On Fri, Jan 10, 2025 at 07:37:42AM +0200, Sulev-Madis Silber wrote: > not sure if this is even this arm mailing list topic but problem exists. and the more i try to push it, the more it fails > It might not hurt to copy the freebsd-current list. From your description at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273566 it appears you're seeing the trouble on an amd box. So far I've seen it only on arm (Raspberry Pi) but I've nothing else on hand. Thanks for writing, bob prohaska > From nobody Fri Jan 10 17:52:13 2025 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 4YV8PS0czdz5kFhS for ; Fri, 10 Jan 2025 17:52:28 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-21.consmr.mail.gq1.yahoo.com (sonic310-21.consmr.mail.gq1.yahoo.com [98.137.69.147]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YV8PR5QTbz4C8k for ; Fri, 10 Jan 2025 17:52:27 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1736531545; bh=w40HLjnYuWxsnKAOVXqhPY41iXP335JLTLSTy3WiWvw=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=ucYsET37sIfm9dhN2R6yFzeKvlj+bP+kPJfv0+MKXPhaI0IQA9/9VkV26+6CG4bukS1k0hHrKkugo4yFTphxR/mmdyD3mm/yUsYKxe98c9hHd76G4X2Gi5HiOTimUGoIE8NKPk4QZsdfRwfXUfT86bopT+93FZUHI/8obFpdRV46FlQFJEcvWzrxmo4W6ASfMVjxmYzFJ4MGqf2s0agPamzwmEIpiysqx22aUoNlsLrZWKqPGJIr2qCV1akHXvZFcxHXnn/o1AdKm0S7A8fbxQEVU5zxH6UcnaANlbdKQWZf4GpN6J5ksl+G/NXnNhH5+h69gpCWVp5gnNoXqNUcyg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1736531545; bh=ecykufMI4Ff9FRzHqu+FlfW/Al2Pm/n+Ns7n50nsD3R=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=UrFMuSsfJChOLhQqc2SvbNjWIrkiMSwJJIeagCiW70Df2Re7TRp1Kes7Voi939UqYxVr3hOWdHTBGJZNiHBsxET4XKcGf7f9S8dCvsQcq1ozSXfNBsrYnBWT5D3sZCE+t3SpeLFRrx6cGl1GzKxc9RqMRFRdSGf97S7OT6T9HjDZBLvrJijFu9akgOjHcfO6AKtopjyvwPNmOB7rEfla3GChaSnfsg1ZqbxdmAFc5W/zS4Vhbu2UzNu7GWWyO6NmpuiSLM2S4rBc/lXSOxXOcIyx4ZVAA9/g8nFrvx3GC4yw9nTr4odlG01RRMQwto2HCawkBMnxbmcSlVD0DCwUoQ== X-YMail-OSG: 7BKLLS4VM1nmlSP4sU01uXzjVN8nMYtQaxipn3FDsfGVs1D.F9VMSGV7_xm8ZBk G59tZGCSZROt28IrLO6WkABxUL0G8IyUbIXoWME1jV67WFgZwHytMBMX5vdyyjkJ9fwRA7ywl5mC .xbCNXKmpxaMLQTiSag.VXA7c0QF61cR6rxBOBEpwOhKlE.U2c3xiPWD6zVkrw8raJlfiJDvUOt3 0DWMFAm1akd3yPQNsi.tiN_B_B9gnM3Qlt3x_uMzQ5zTaUuvcSutMKqFg9E.1Xqx8sB0J3_hEzhk zNzd2vM4615LBjG9fxCqIdtdQ_11ps4k463LsLgNFiG.TZ.fzPpMWxY5D_gTiqshxxZ8ujYGwT0. Zxq0zbQqa6dAIw3dFYeY9F9NVAspqeed5h_RQBVYF2UCXDvyXCsqydNwL23dP.Cp6efi81Lf1BVF batq_oxBnXtXupLXEbR9OQUeI0h33pokC.9GYICePGk_AuiDKxg5EgITodBXwI6g39k9SmgnH6WG QNIbKnnhtYPKF46SFJaIJO0yzrKscOx.rfRPcWnlOuszQL.8L3W8JEj.8rXBnwD1fnOs5G_XbCaw p4jc0vpTwLP747VhZHvb98Hk0d9_Kh9V6PoWkDb2XLXeUuxkrlFzWT7kMXaqHZb8e1V2eyLfzVjK p6JuvcEXwqSdCxBnbK2Ow_vSRt_YHdknH1cFEEq21ftcbb0p0XmCllqcIa7N3_ftc5EY45ePMS9x oHSjFYH5w5iSva_nHMKpaDliF2QBJoBbv_KLsNLK0JwRGx.ThZX2LbLJKfHBt3b1XxvYf5rNOeyP mpq0D9hj2nZdz977Fnl6fJbaxtqPA3pWbjYBmirDSeB1T9IUAbRI2ZwYT25utu.qZVCaPKwhbno4 16eYP0ZjTmBjwSkkuCIhOZNVy3NIpigQSAjHnbQy04gku5fZB9grABfweFGUBigtawddAOgr5jjq Ln7fpWecLLgvhSaE3.gxCLso1LO8yix.RlnMciHe28ruI2Ohdk71Hn_nJqgSyl1crJJUmKLLZat_ IyliPeMCm2jlkPyxCH5RbKuIej5QI9Kq4HJJGxj0g5T6bX_3JKacioJIHN7DrpGz_n2g.ok_T6SW A9Lo57GPeFxavqsJ687o8yzfISF_1iMQIcpcxOsUmm3SRBxiRZKCNZaB1APfy2TwZdtJHktujx71 7Ik8YRtYk1t89FT2b.r364euwRJm8gOr4ZVpciyrPfGblayj7pvmTFKnGRFG2wH6IkUnZCnibNo9 cwwzkmo5LT0aovT2okR3fY6DDDxlTM_mtp8nwN1hQe3UXGHYXW1Ka0xiPNuonlSP_U3xPbIxOAIV JypjgYrdhgGtQmtk4NnAMQryjP7xr8FweVeeT7pIkxWRKmU54kHFtnv9A872dIPRcPzgwtDW1dXa iYqYV_eoDgSG5Qr.nrriGRQu5XrsMQjhE8tgow1ji1Aq.KyHsDfA8kZ0O6TGM3xwL0.vWrpSvCTg Qyg9ofem1EGJvf4SI3idHWoBSk0U2u8uzD9rjxfePmtUcD0K2WkK3tCtdAQQMKc77X_idKL1973z UZu8.PZl.Xk_sH_hC2MyqqNjj9n7Rn1OmQW..UxDil.LgbsVgl8ReQy.UAdfCNusr35ef6sPg3Qg Ad0b_OCUlhV8dZO0J2VgzDT5pVRJmVl64JplNF6lKXMIfvczAhqTbqT.22plnZ_4lHCS.XY7Ltdb krk96CA.NFvoKuvHNpQt1FJDc0Ft9nKp1npjs49VvcSrh4EeMx1C_iOG8hGclcj41XI8GoLyhVIj _rvnwekA0bv_ONfRoClvKaxoVoD1laBNQtzu0JdqU9TPciXQ90f5tWjKmT2Fj9m_njSCJvPV1lVE 3KPDikQ0loA8AMfD_w9C7BTz2LWcpHnVCJQHODbLXai3jjm5piAa4yoEMrlRQEEF2eu6tC4h8O2v gSnD2F3EafJTXtcAitUtJb7KiEeB_y8NueSmJc3L107FmqQYEL1cJVN6eH_Osza3ooFV5FPwP98P zhj3DYb27At0BvNt7I3lUR00ewN.O9IqbGKP79SL9a8PTFz_5iodEJLQIVmCBC9cpKg_kglq66PO FXytYGUTPhvWeU.XYE6regU9MBxv_vMsgd2EQnuTC.JKhpuefocgHeonfhuXlhCZNKJ9OfVMfKD. 1trSFIJZAO8drAgTf7WFq3G300B7qUTzYiV1ZxuvMQcFBJ..spIFBfZcZi6fsgEekasOrQu.nRB0 ojqDRlKvBYC_7zknjj7DtveQ.1hSX4Y8wS.e3XIjKDy94tpHBg_c4kLNDILH9Gd5D X-Sonic-MF: X-Sonic-ID: 4913fb9e-faf4-4f51-8477-8bab00d46d66 Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Fri, 10 Jan 2025 17:52:25 +0000 Received: by hermes--production-gq1-5dd4b47f46-pfhh2 (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID e4f94abf9239ea2f69043868f9d3ba7d; Fri, 10 Jan 2025 17:52:25 +0000 (UTC) Content-Type: text/plain; charset=us-ascii 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 (Mac OS X Mail 16.0 \(3826.300.87.4.3\)) Subject: Re: Raspbery Pi support (release notes/wiki page) update? (RPI5) From: Mark Millard X-Priority: 3 (Normal) In-Reply-To: <881635894.2479.1736499825338@localhost> Date: Fri, 10 Jan 2025 09:52:13 -0800 Cc: Paul Floyd , freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <668r286o-584q-616o-5nq3-0233r3259qsr@yvfgf.mnoonqbm.arg> <7sp0np90-0rnn-n327-qps0-358493p411rs@yvfgf.mnoonqbm.arg> <68B36F4A-76AD-4CEC-ACBA-3EEF6863BB04@yahoo.com> <1284671542.924.1736419337261@localhost> <51c72f9e-19fc-4cf6-8bb8-dacb97b9b793@wanadoo.fr> <881635894.2479.1736499825338@localhost> To: Ronald Klop X-Mailer: Apple Mail (2.3826.300.87.4.3) X-Rspamd-Queue-Id: 4YV8PR5QTbz4C8k 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:36647, ipnet:98.137.64.0/20, country:US] Hello Ronald, (Working from memory and old Email content.) I'll note that I have partitions for the FreeBSD EFI loader (msdosfs), FreeBSD-in-UFS, and SWAP-space on USB3 media but the rpi5-uefi content on a microsd card in a msdosfs . I copy the FreeBSD loader.efi to the USB3's msdosfs with appropriate path and file naming. (Note: My context is normally main [so: 15 at this point].) =46rom an old Email (/boot/efi is a mount point for USB3 media's msdsofs): # find /boot/efi/EFI/ -print /boot/efi/EFI/ /boot/efi/EFI/FREEBSD /boot/efi/EFI/FREEBSD/loader.efi /boot/efi/EFI/BOOT /boot/efi/EFI/BOOT/bootaa64.efi I doubt that the FREEBSD path is needed but I've always blindly made both copies of the /boot/loader.efi that is in FreeBSD's file system for aarch64. Note: I force the capitalization of EFI to make the name distinct. /boot/efi/efi/ is normal as I remember. EFI is in the msdosfs . In this organization, the microsd card is the starting point. The rpi5-uefi then finds the USB3's msdosfs's BOOT/bootaa64.efi . That in turn finds the USB3's FreeBSD kernel in UFS and loads and starts it. That in turn does the mount of the root file system (from the same UFS file system as the kernel in my context) and starts the world code. I've also done examples with ZFS (bectl use) instead of UFS in the past but normally only use ZFS on the largest/fastest FreeBSD configuration that I (usually) have access to. (I've never used ZFS for redundancy or striping or such: just for bectl use.) Mark On Jan 10, 2025, at 01:03, Ronald Klop wrote: Van: Paul Floyd Datum: donderdag, 9 januari 2025 20:31 Aan: freebsd-arm@freebsd.org Onderwerp: Re: Raspbery Pi support (release notes/wiki page) update? On 09-01-25 11:42, Ronald Klop wrote: > Hi Mark, > > I just noticed an RPI5 with 16GB RAM became available [1]. Which > = triggers my interest in an upgrade of my current RPI4/8GB used to build = > aarch64 ports. > > I see that you have quite some experience in setting up the RPI5 with = > knowledge expressed in several emails. > Would you mind to setup a https://wiki.freebsd.org/arm/RPI5 wiki.freebsd.org/arm/RPI5> page and collect your knowledge/experience = there? I just made a start: https://wiki.freebsd.org/arm/Raspberry%20Pi%205 A+ Paul =20 Thank you very much! Just ordered a RPI5. Regards, Ronald. =20 =3D=3D=3D Mark Millard marklmi at yahoo.com