From owner-freebsd-arm@freebsd.org Mon May 6 21:27:32 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 7FEF91596AD8 for ; Mon, 6 May 2019 21:27:32 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1.eu.mailhop.org (outbound1.eu.mailhop.org [52.28.251.132]) (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 B5F328BA20 for ; Mon, 6 May 2019 21:27:31 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1557178048; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=U41UQZ9G4Z8GGeFFtgdSLd8a/mFSEma+pKHsaddASbwimkhrn91in1VyGSg+0AyPF1mcxgh2sXEbE xjebEZl3NW9/L58ydRcyeXpBwFf7UyCT+c/ms/Eb1AAxVmiTLm2bB562RtCfb08giG3rxssFXK9lQn 5c/N+CqQ93D7BQyr2+Smqhl7GWqf0btFIRjgb+KILSeKArLS8+R3FmbGMsCOI1akWCvLjtnU4NlduH L8S2j423FQO5UbN+hi+o3BTCozIJudQr1ze3LFiWSWiVgt6Ao0MpZlEdzcIL9AmBS4C4K3RYz8kMUv +PDH7aZhzE+2fessynVBQALbxUSFkZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=20ifZ46vBxsZzPy1D7PWo/ZnwHKczAiJP9K7ikkfI8U=; b=husk5J3IZ3af7qpwmzNj3j4K62V2yLesDPKylXuqshODjMH0G7mWi60hYY3CdyieyhDD5im4eekLN wEmsrIhtw5GlvkztI+lxHXtHI3HRWnD8wFFgSDMG2u5FZOHqskDFICcRFhcOBAIbxZQxZ6d5anAyon c90GKdQZeWZroCN2Nst04khsypAvIa4Yw7QSYIZHQ50L7hUyZKGrpXReF12GDjWVcK3dGROiPOrNLh fOaf8vV/xaoDBGPyvpKGHuasnIJ+LheOXYP3s/GE79p5Kk5b2GA3EHgG72+O6vGZB0Kkp1DCrjQonM dXF7fifnNfDLXHFI4I98B8Xloiw4w9Q== ARC-Authentication-Results: i=1; outbound3.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=20ifZ46vBxsZzPy1D7PWo/ZnwHKczAiJP9K7ikkfI8U=; b=GVsgbmBzUzF6JXpI1QNoAKFUbzG3rcAzBs3Qwl5HPQmg/wN+1IYNuzIXuABF5B6csUIRfAddx3Tw3 d4w3YEIZO37UlTaDsZyyL+bDPYKsw3QcGzl/4lImq9aXqZ1xMpex7yXxdHBkNzVLsGOyAlvHQ/+Y3T CPv8w28+5qEjB4nXIDvBbKM6rwe1gEcXNsZwT7oRlqaQhwqjKHZ2Iw0zFT7SiHjVdi7BM6m1kcNQJX qYxl0MZrmyEDiGymNB6ZOtiZ6+9DN4bEL4BzuoCrYA2gXxz/mzUOUwP+1ACerv22LHTYUXTmO0XCHl 9neYNgA1NZRTW9ziDTtpFIa96G8JITg== X-MHO-RoutePath: aGlwcGll X-MHO-User: bd5e8216-7045-11e9-908b-352056dbf2de X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.eu.mailhop.org (Halon) with ESMTPSA id bd5e8216-7045-11e9-908b-352056dbf2de; Mon, 06 May 2019 21:27:26 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x46LROBM034202; Mon, 6 May 2019 15:27:24 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: Compiling u-boot-rpi3 on an rpi3 From: Ian Lepore To: James Shuriff , bob prohaska Cc: "freebsd-arm@freebsd.org" Date: Mon, 06 May 2019 15:27:24 -0600 In-Reply-To: References: <20190506020115.GA40421@www.zefox.net> <20190506151908.GA43714@www.zefox.net> <20190506180501.GB44000@www.zefox.net> <20190506192919.GA44506@www.zefox.net> <20190506210832.GA45045@www.zefox.net> <81a9c8cd930ae5740a3245c0f956fc280cc5f473.camel@freebsd.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: B5F328BA20 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.980,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:16509, ipnet:52.28.0.0/16, country:US] 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:27:32 -0000 On Mon, 2019-05-06 at 21:24 +0000, James Shuriff wrote: > You have to cross compile regardless of what your host system is. U- > Boot uses GNU's toolchain, unfortunately. That didn't used to be true. GCC was required to cross-compile on amd64, but native compiles were done using the preinstalled host clang. That was fixed back in like 2016, maybe even earlier. Hmmm, for armv6/7 that is; maybe it never worked for aarch64? -- Ian > Rpi-firmware will also install files in /usr/local/share because, as > previously stated, it's the safest option. I don't know how often the > VideoCore blobs get updated but if you want the latest and greatest > replace what's in your /boot with the blobs from rpi-firmware, U-Boot > from u-boot-rpi3, the dtb's from /boot, and bootaa64.efi from > /boot/loader_lua.efi (same as /boot/loader.efi, it's a hard link). > > If you want a completely up to date system install the rpi-firmware > port and copy over newer versions of the files. You'll need the dtb's > from /boot and you'll have to update bootaa64.efi from loader_lua.efi > in /boot. > > - James Shuriff > > -----Original Message----- > From: Ian Lepore > Sent: Monday, May 6, 2019 5:18 PM > To: bob prohaska ; James Shuriff < > james@opentech.cc> > Cc: freebsd-arm@freebsd.org > Subject: Re: Compiling u-boot-rpi3 on an rpi3 > > 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 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. 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. > > -- Ian > > > > > 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 > > > /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 > > " > > ________________________________ > 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 james@opentech.cc>). >