From nobody Thu Jul 04 19:42:16 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 4WFRr722CLz5PK5H for ; Thu, 04 Jul 2024 19:42:31 +0000 (UTC) (envelope-from pmh@hausen.com) Received: from mail2.pluspunkthosting.de (mail2.pluspunkthosting.de [217.29.33.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WFRr66vsbz4FCv for ; Thu, 4 Jul 2024 19:42:30 +0000 (UTC) (envelope-from pmh@hausen.com) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (87.138.185.145) by mail2.pluspunkthosting.de (Axigen) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA id 16D3AB; Thu, 4 Jul 2024 21:42:27 +0200 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 \(3774.600.62\)) Subject: Re: Update boot partition on a Pi - necessary? How? From: "Patrick M. Hausen" X-Priority: 3 (Normal) In-Reply-To: <36B840F1-D893-4888-B4B2-C94735EC7D92@yahoo.com> Date: Thu, 4 Jul 2024 21:42:16 +0200 Cc: Ronald Klop , Mark Millard Content-Transfer-Encoding: 7bit Message-Id: <87A6A5D9-6458-4272-9A19-695210981349@hausen.com> References: <6B3A59F7-92CF-4614-9501-8C7D62FF676B@hausen.com> <1128281839.5949.1720092998746@localhost> <36B840F1-D893-4888-B4B2-C94735EC7D92@yahoo.com> To: FreeBSD ARM List X-Mailer: Apple Mail (2.3774.600.62) 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:16188, ipnet:217.29.32.0/20, country:DE] X-Rspamd-Queue-Id: 4WFRr66vsbz4FCv Thanks everybody for the hints. > Am 04.07.2024 um 18:04 schrieb Mark Millard : >> >> The files in the FAT partition are a combination of >> https://www.freshports.org/sysutils/rpi-firmware/ > > Installing that package/port installs files into: > > /usr/local/share/rpi-firmware/ I know. I already copy the i2c module from that port to my boot partition for the master node on my Turing Pi. Since I needed to re-image one of my compute modules for other reasons, anyway, I decided to use dd to update the remaining Pis and re-apply my ansible play to bring the control node to the configuration I need, afterwards. I would still love to see a documentation like the Klara Systems article [1] on FreeBSD booting on amd64 about the process on Raspberry Pis. Why does this have to be so convoluted and intransparent? Yeah, it's from Linux. ;-) I also never understood the need for initramfs and friends. Our bootloader is simple and straightforward. Today with ubiquitous GPT the bootloader is launched by legacy BIOS or EFI, it can read UFS or ZFS, loads the kernel and starts it. Done. But I digress. Thanks again. Not willing to invest much time into the RPi platform apart from running my small cluster - contrary to amd64 of which I have around 100 systems to keep up to date. So I'll probably stick to images and dd for now. Kind regards, Patrick [1] https://klarasystems.com/articles/the-freebsd-boot-process