From owner-freebsd-arm@freebsd.org Mon May 6 21:49:06 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A11F71597045 for ; Mon, 6 May 2019 21:49:06 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A8458C3A2; Mon, 6 May 2019 21:49:05 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id x46LmNfF045309 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 6 May 2019 14:48:24 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id x46LmNuG045308; Mon, 6 May 2019 14:48:23 -0700 (PDT) (envelope-from fbsd) Date: Mon, 6 May 2019 14:48:23 -0700 From: bob prohaska To: Ian Lepore Cc: James Shuriff , "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: Compiling u-boot-rpi3 on an rpi3 Message-ID: <20190506214823.GB45045@www.zefox.net> References: <20190506151908.GA43714@www.zefox.net> <20190506180501.GB44000@www.zefox.net> <20190506192919.GA44506@www.zefox.net> <20190506210832.GA45045@www.zefox.net> <81a9c8cd930ae5740a3245c0f956fc280cc5f473.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <81a9c8cd930ae5740a3245c0f956fc280cc5f473.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 3A8458C3A2 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.87 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; IP_SCORE(0.11)[ip: (0.41), ipnet: 50.1.16.0/20(0.21), asn: 7065(-0.03), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.16)[0.157,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.20)[0.198,0]; MX_GOOD(-0.01)[cached: www.zefox.net]; NEURAL_SPAM_LONG(0.52)[0.524,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 May 2019 21:49:06 -0000 On Mon, May 06, 2019 at 03:18:10PM -0600, Ian Lepore wrote: > On Mon, 2019-05-06 at 14:08 -0700, bob prohaska wrote: > > Ok, now I'm thoroughly confused 8-) It sounds as if the guiding > > assumption behind the u-boot-rpi3 port is that it _isn't_ being > > self-hosted, but rather part of a cross-compile to be copied onto > > an installer medium. This is at variance with "normal" ports, but > > consistent with an embedded target that never self-hosts. > > > > Looking at my own rpi3's /boot directory, most of the files are dated > > May 4th, the last time world and kernel were rebuilt and installed. > > Are those files genuinely up-to-date, or merely fresh copies of old > > versions from /usr/share.....? > > > > On a Pi3 that _is_ selfhosting, will updating rpi-firmware and u- > > boot-rpi3 > > and then updating world and kernel complete the firmware and u-boot > > update? > > > > Apologies for the confusion, and thanks for any clarification! > > > > bob prohaska > > > > Updating boot stuff is always a semi-manual procedure. For example, on > x86 systems after doing make installworld you have a new boot0 and a > new gptboot or zfsboot, but they've only been installed to /boot. It's > up to you to run the gpart commands that install those things to the > outside-the-ufs-filesystem parts of the disk drive. > > The same concept applies to arm and other embedded systems, which have > an even more diverse set of "outside the ufs filesystem" things to deal Apparently I'm not understanding the significance of "outside of ufs" in this situation. On the Pi3 a simple cp works. I'd think that an install script could run gpart, certainly more reliably than I can! > with. In the embedded case it's not necessarily even safe or possible > to install the various boot bits to /boot, because there may be items > that have the same name (u-boot.bin for example) but actually differ > depending on SoC or system type. Doesn't the system have to know that anyway to compile in the first place? > So installing boot bits to > /usr/local/share/u-boot then making the user handle the last bit of the > install is about the only option. > If it's not practical to make an installer sufficiently platform-aware to handle "the last bit" then a man page would really help. U-boot updates aren't needed often and a botched attempt is hard to recover from. Thanks for reading! bob prohaska > > > -----Original Message----- > > > From: James Shuriff > > > Sent: Monday, May 6, 2019 3:42 PM > > > To: bob prohaska > > > Cc: freebsd-arm@freebsd.org > > > Subject: RE: Compiling u-boot-rpi3 on an rpi3 > > > > > > /boot/msdos is an arbitrary location. It's not even required to > > > mount it. I mount my FAT partition elsewhere. Some boards don't > > > even have u-boot in the filesystem they dd it directly onto the > > > disk. Also consider you don't have to build the port on the > > > Raspberry Pi, so there would be no way to install u-boot from the > > > host system without knowing where the SD card is mounted. > > > > > > The rpi-firmware port also puts stuff in /usr/local/share. That's > > > the port that has most of the files needed for the Raspberry Pi's > > > FAT partition. Here is a list of the files in the FAT partition and > > > where you can get them from: > > > > > > /LICENSE.broadcom: rpi-firmware port > > > /armstub8.bin: rpi-firmware port > > > /bcm2710-rpi-3-b.dtb: rpi-firmware port > > > /bootcode.bin: rpi-firmware port > > > /config.txt: rpi-firmware (config_rpi3.txt) > > > /dtb/*: FreeBSD Build Output > > > (/usr/obj/usr/src/arm64.aarch64/sys/$KERNCONF/modules/usr/src/sys/m > > > odules/dtb or /boot/dtb on the Raspberry Pi) > > > /fixup*.dat: rpi-firmware port > > > /overlays/*: rpi-firmware port > > > /start*.elf: rpi-firmware port > > > /u-boot.bin: u-boot-rpi3 port > > > > > > - James Shuriff > > > > > > -----Original Message----- > > > From: bob prohaska > > > Sent: Monday, May 6, 2019 3:29 PM > > > To: James Shuriff > > > Cc: bob prohaska > > > Subject: Re: Compiling u-boot-rpi3 on an rpi3 > > > > > > On Mon, May 06, 2019 at 06:18:35PM +0000, James Shuriff wrote: > > > > Copy /usr/local/share/u-boot/u-boot-rpi3/u-boot.bin to > > > > /boot/msdos. > > > > > > > > > > Ok, that did the trick. Is there some particular reason make > > > install didn't perform the copy? > > > > > > Thank you very much! > > > > > > bob prohaska > > > > > > > > > > - James Shuriff > > > > > > > > -----Original Message----- > > > > From: owner-freebsd-arm@freebsd.org < > > > > owner-freebsd-arm@freebsd.org> On > > > > Behalf Of bob prohaska > > > > Sent: Monday, May 6, 2019 2:05 PM > > > > To: Mika??l Urankar > > > > Cc: freebsd-arm@freebsd.org; freebsd-ports@freebsd.org > > > > Subject: Re: Compiling u-boot-rpi3 on an rpi3 > > > > > > > > On Mon, May 06, 2019 at 06:20:45PM +0200, Mika??l Urankar wrote: > > > > > Le lun. 6 mai 2019 ?? 17:19, bob prohaska > > > > > a ??crit : > > > > > > > > > > > > On Mon, May 06, 2019 at 03:22:31PM +0200, Mika??l Urankar > > > > > > wrote: > > > > > > > > > > > > > > It builds fine here on aarch64, do you have > > > > > > > security/openssl* installed? > > > > > > > > > > > > > > > > > > > Yes, security/openssl is installed. I didn't use it by > > > > > > default > > > > > > because of earlier reports of trouble. The system reminds me > > > > > > that > > > > > > > > > > Delete it and rebuild u-boot-rpi3 > > > > > > > > > > > > > That certainly helped, make now runs successfully. > > > > > > > > But, make install didn't update anything in /boot/msdos. > > > > There seem to be three copies of u-boot-bin floating around, with > > > > identical size. Should I copy one manually to /boot/msdos, and > > > > does it matter which one? > > > > > > > > Thanks for reading and your help! > > > > > > > > bob prohaska > > > > > > > > _______________________________________________ > > > > freebsd-arm@freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > > > To unsubscribe, send any mail to " > > > > freebsd-arm-unsubscribe@freebsd.org" > > > > ________________________________ > > > > DISCLAIMER: This message and any attachments are intended solely > > > > for the use of the recipient and may contain confidential > > > > information. If you have received this message in error please > > > > delete it and promptly notify the sender, James Shuriff ( > > > > james@opentech.cc). > > > > > > > > > > ________________________________ > > > DISCLAIMER: This message and any attachments are intended solely > > > for the use of the recipient and may contain confidential > > > information. If you have received this message in error please > > > delete it and promptly notify the sender, James Shuriff ( > > > james@opentech.cc). > > > > > > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org > > " >