Date: Tue, 12 Jul 2022 09:46:35 -0700 From: Mark Millard <marklmi@yahoo.com> To: Ronald Klop <ronald-lists@klop.ws> Cc: Warner Losh <imp@bsdimp.com>, "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, "Dr. Rolf Jansen" <freebsd-rj@cyclaero.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Partition layout of ARM SD card images Message-ID: <C30581DB-7DC4-46B3-9618-B0A4CBD7710D@yahoo.com> In-Reply-To: <1169617916.2919.1657613121111@localhost> References: <1169617916.2919.1657613121111@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Jul-12, at 01:05, Ronald Klop <ronald-lists@klop.ws> wrote: > . . . >=20 >=20 > It seems the image builder of aarch64 13-stable is disabled.=20 > https://ci.freebsd.org/job/FreeBSD-stable-13-aarch64-images/ > Other architectures are enabled.=20 Looks to me like even if the: https://ci.freebsd.org/job/FreeBSD-*-aarch64-images/ were being run, the activity would not seem to test what the likes of: cd /usr/src/release sh release.sh -c arm64/RPI.conf does in chroot_arm_build_release for producing an image. For example, chroot_arm_build_release does not use mkimg . It appears that: = https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/build-imag= es.sh is only set up for where passing "-b ufs/boot/pmbr" to mkimg is useful. In fact: https://ci.freebsd.org/job/FreeBSD-main-aarch64-images/ shows runs failing for: mkimg: ufs/boot/pmbr: No such file or directory before they disabled the project. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C30581DB-7DC4-46B3-9618-B0A4CBD7710D>