From nobody Mon Jan 31 14:52:53 2022 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 785DB1993C1B for ; Mon, 31 Jan 2022 14:53:03 +0000 (UTC) (envelope-from SRS0=a6zr=SP=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 4JnWJZ1K9yz4RfK for ; Mon, 31 Jan 2022 14:53:02 +0000 (UTC) (envelope-from SRS0=a6zr=SP=klop.ws=ronald-lists@realworks.nl) Date: Mon, 31 Jan 2022 15:52:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1643640773; 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=xiNRc6JFomt4tfCglRK9GF0T8JLMl9ngvFm5fpifaVY=; b=Xy88LtbQANTuJ12MjRL5Vg0fwU027VQhD8vIUOtWuq76eypUA3Urk6pIQHku9F3CTvWlLv SWbDDKQuNpFfMVLCUXXOpiyrgulFV/kHFwHDg90EEpbILARjIRVhnA589+Re/EWD3HyTMz bOnxQoZcN0qjOvdwQd65Yvr3uXeokMdoE27RUrtQEg0zkjApTEMFifo/clcrBKcpTXHfgC 5Ejihc9QqxqZduQaVPi8XDeTd+5qnEbO33tLgQ++Cg6D5970pPtlDaDuCU3umaK4y9XJ8/ Zoac1mX3hcp8DIX2UwmKdf8TNFaadjs4OMP8b5I38FN4qlSJ3QLYC7hvQxoXAw== From: Ronald Klop To: Mike Karels Cc: Stefan Parvu , freebsd-arm Message-ID: <208103706.383.1643640773365@localhost> In-Reply-To: <7C430492-002B-42A5-BD3E-2FA6B6A92D17@karels.net> References: <091FE5A0-9304-4780-AC9C-8712742D3D35@kronometrix.org> <0544C75F-7B46-4D80-96EC-E898B2B8DD1D@kronometrix.org> <7C430492-002B-42A5-BD3E-2FA6B6A92D17@karels.net> Subject: Re: RBPI3 for FreeBSD 12.3 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_382_2061704107.1643640773290" X-Mailer: Realworks (593.5.8d33753) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4JnWJZ1K9yz4RfK X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=Xy88LtbQ; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=a6zr=SP=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=a6zr=SP=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-3.20 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; HAS_X_PRIO_THREE(0.00)[3]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-arm]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=a6zr=SP=klop.ws=ronald-lists@realworks.nl]; RCVD_COUNT_ZERO(0.00)[0]; RWL_MAILSPIKE_POSSIBLE(0.00)[194.109.157.24:from]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=a6zr=SP=klop.ws=ronald-lists@realworks.nl] X-ThisMailContainsUnwantedMimeParts: N ------=_Part_382_2061704107.1643640773290 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable =20 Van: Mike Karels Datum: zondag, 30 januari 2022 14:21 Aan: Stefan Parvu CC: freebsd-arm Onderwerp: Re: RBPI3 for FreeBSD 12.3 >=20 >=20 > On 30 Jan 2022, at 1:33, Stefan Parvu wrote: >=20 > >> There was a u-boot change required to boot 12.3 on RPi3, but it didn= =E2=80=99t > >> get checked in before the ports tree was tagged. > > > > I see. Do we expect to have ready images anyway published or we move fw= d to 13.1 ? >=20 > I haven=E2=80=99t heard of modified images being made later. But 13.0 is= available now. >=20 > Mike > > > > Thank you > > Stefan > =20 >=20 >=20 >=20 Hi, Might a snapshot help? It is not a release version, but it is more up-to-da= te than 12.2. https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/12.3/ NB: Running 13.0 on RPI3 gives freebsd-update support. Which is a very reso= urce friendly way of keeping it up-to-date. My rpi3 runs it. Regards, Ronald. =20 ------=_Part_382_2061704107.1643640773290 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable  

Van: Mike Karels <mike@karels.net>
Datum: zondag, 30 januari 2022 14:21
Aan: Stefan Parvu <sparvu@kronometrix.org>
CC: freebsd-arm <freebsd-arm@freebsd.org>
Onderwerp: Re: RBPI3 for FreeBSD 12.3


On 30 Jan 2022, at 1:33, Stefan Parvu wrote:

>> There was a u-boot change required to boot 12.3 on RPi3, but it di= dn=E2=80=99t
>> get checked in before the ports tree was tagged.
>
> I see. Do we expect to have ready images anyway published or we move f= wd to 13.1 ?

I haven=E2=80=99t heard of modified images being made later.  But 13.0= is available now.

        Mike
>
> Thank you
> Stefan
 


Hi,

Might a snapshot help? It is not a release version, but it is more up-to-da= te than 12.2.
https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/12.3/
NB: Running 13.0 on RPI3 gives freebsd-update support. Which is a very reso= urce friendly way of keeping it up-to-date. My rpi3 runs it.

Regards,
Ronald.
  ------=_Part_382_2061704107.1643640773290--