From owner-freebsd-arm@freebsd.org Mon May 6 21:09:17 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 112E3159616C for ; Mon, 6 May 2019 21:09:17 +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 459C38A85B for ; Mon, 6 May 2019 21:09:14 +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 x46L8Xem045161 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 6 May 2019 14:08:34 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id x46L8XCa045160; Mon, 6 May 2019 14:08:33 -0700 (PDT) (envelope-from fbsd) Date: Mon, 6 May 2019 14:08:33 -0700 From: bob prohaska To: James Shuriff Cc: "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: Compiling u-boot-rpi3 on an rpi3 Message-ID: <20190506210832.GA45045@www.zefox.net> References: <20190506020115.GA40421@www.zefox.net> <20190506151908.GA43714@www.zefox.net> <20190506180501.GB44000@www.zefox.net> <20190506192919.GA44506@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 459C38A85B X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.63 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; NEURAL_HAM_MEDIUM(-0.20)[-0.200,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; 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)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: www.zefox.net]; NEURAL_SPAM_LONG(0.03)[0.034,0]; NEURAL_HAM_SHORT(-0.20)[-0.197,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:09:17 -0000 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 On Mon, May 06, 2019 at 07:46:03PM +0000, James Shuriff wrote: > EFI/BOOT/bootaarch64.efi is the same as /boot/loader_lua.efi which is also the same as /boot/loader.efi. You can use a different loader, of course, but the Lua loader is the default. > > - James Shuriff > > -----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/modules/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 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). >