Date: Tue, 17 Mar 2020 22:02:22 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: Ross Alexander <rwa@athabascau.ca>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: freebsd-arm Digest, Vol 724, Issue 3 (Answer: sysutils/u-boot-rpi3 and sysutils/u-boot-rpi4 have been updated) Message-ID: <F9B8A0F5-8619-4F8C-9002-58EDE398D93C@yahoo.com> In-Reply-To: <40B4C39A-7A3D-4C34-81AC-7EC05BBF0572@yahoo.com> References: <mailman.67.1584273601.57537.freebsd-arm@freebsd.org> <alpine.BSF.2.22.395.2003161327310.93374@autopsy.pc.athabascau.ca> <4DB90158-B77E-4D65-8E94-B6941D7D76DE@yahoo.com> <20200317173515.GA65926@www.zefox.net> <40B4C39A-7A3D-4C34-81AC-7EC05BBF0572@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Mar-17, at 11:26, Mark Millard <marklmi at yahoo.com> wrote: > On 2020-Mar-17, at 10:35, bob prohaska <fbsd at www.zefox.net> wrote: >=20 >> On Mon, Mar 16, 2020 at 06:25:01PM -0700, Mark Millard wrote: >>>=20 >>> sysutils/u-boot-rpi3 and sysutils/u-boot-rpi4 have >>> been updated to pick up patches and to configure >>> the reserved RAM for armstub8*.bin correctly: >>>=20 >>> Author: kevans >>> Date: Mon Mar 16 21:32:55 2020 >>> New Revision: 528547 >>> URL:=20 >>> https://svnweb.freebsd.org/changeset/ports/528547 >>>=20 >>>=20 >>> Log: >>> sysutils/u-boot-rpi{3,4}: Add patch to fix PSCI stub reservation >>>=20 >>> For the traditional spin table setup, only the lowest page needs >>> to be reserved. However, our PSCI stubs are slightly bigger and = occupy >>> a little over one page. These patches, already sent upstream, allow = a >>> variable number of initial pages to be reserved for the SMP stubs. = We >>> then set the values for these in our fragment to '2' to reserve the = first >>> and second page. >>>=20 >>> Approved by: koobs (mentor) >>> Approved by: manu (uboot, maintainer) >>> MFH: 2020Q1 >>> Differential Revision:=09 >>> https://reviews.freebsd.org/D24085 >>>=20 >>>=20 >>> Modified: >>> head/sysutils/u-boot-master/distinfo >>> head/sysutils/u-boot-rpi3/Makefile >>> head/sysutils/u-boot-rpi3/files/rpi3_fragment >>> head/sysutils/u-boot-rpi4/Makefile >>> head/sysutils/u-boot-rpi4/files/rpi4_fragment >>=20 >> It looks like sysutils/u-boot-rpi3 builds and installs without >> error on a Pi3 reporting >> root@www:/boot/uboot # uname -KU >> 1300045 1300045 >>=20 >> with /usr/ports at Revision: 528581 >>=20 >> However, the make install clearly didn't touch /boot/msdos and >> I couldn't find any obvious instructions on what has to be done >> by hand (ISTR some brief directions from make install previously). >> Make install claims to build man pages, but man can't find them. >>=20 >> In /usr/ports/sysutils/u-boot-rpi3/work/u-boot-2019.10 are found, >> among many other things, a series of files: >>=20 >> -rwxr-xr-x 1 root wheel 4794232 Mar 17 10:07 u-boot >> -rwxr-xr-x 1 root wheel 500440 Mar 17 10:07 u-boot-nodtb.bin >> -rwxr-xr-x 1 root wheel 500440 Mar 17 10:07 u-boot.bin >> -rw-r--r-- 1 root wheel 9167 Mar 17 09:58 u-boot.cfg >> -rw-r--r-- 1 root wheel 5605 Mar 17 10:07 u-boot.cfg.configs >> -rw-r--r-- 1 root wheel 1348 Mar 17 09:59 u-boot.lds >> -rw-r--r-- 1 root wheel 480139 Mar 17 10:07 u-boot.map >> -rwxr-xr-x 1 root wheel 1438904 Mar 17 10:07 u-boot.srec >> -rw-r--r-- 1 root wheel 195715 Mar 17 10:07 u-boot.sym >>=20 >> Any hints as to what goes where would be most helpful. >>=20 >=20 > Using an RPi4 as an example (mostly) . . . >=20 > # mount > /dev/label/RPi4root on / (ufs, NFS exported, local, noatime, = soft-updates) > devfs on /dev (devfs) > /dev/label/RPi4boot on /boot/efi (msdosfs, local, noatime) >=20 > So I see the msdosfs under /boot/efi/ . >=20 > # ls -ldT /boot/efi/*u-boot* > -rwxr-xr-x 1 root wheel 445896 Mar 16 07:59:02 2020 = /boot/efi/u-boot.bin >=20 > So that is where to place the file. >=20 > As for where to get the file to copy there, again for > my RPi4 context, not RPi3: >=20 > # ls -ldT /usr/local/share/u-boot/u-boot-rpi4/* > -rw-r--r-- 1 root wheel 124 Mar 16 07:59:03 2020 = /usr/local/share/u-boot/u-boot-rpi4/README > -rw-r--r-- 1 root wheel 37 Mar 16 07:59:03 2020 = /usr/local/share/u-boot/u-boot-rpi4/metadata > -rw-r--r-- 1 root wheel 445896 Mar 16 07:59:03 2020 = /usr/local/share/u-boot/u-boot-rpi4/u-boot.bin >=20 > So, for RPi3 that would be: >=20 > # ls -ldT /usr/local/share/u-boot/u-boot-rpi3/* > -rw-r--r-- 1 root wheel 124 Mar 16 07:59:02 2020 = /usr/local/share/u-boot/u-boot-rpi3/README > -rw-r--r-- 1 root wheel 37 Mar 16 07:59:02 2020 = /usr/local/share/u-boot/u-boot-rpi3/metadata > -rw-r--r-- 1 root wheel 500440 Mar 16 07:59:02 2020 = /usr/local/share/u-boot/u-boot-rpi3/u-boot.bin >=20 > Note: >=20 > The RPi*'s do not have such materials placed via dd (outside > the file systems), unlike most small arm boards. I use this > to have media that dual boots, such as booting a Rock64 (uses > dd to outside the file systems) or a RPi4 . I should have shown how to find where installed files are after installation. Using u-boot-rpi3 as an example: # pkg info -l u-boot-rpi3 u-boot-rpi3-2019.10_1: /usr/local/share/licenses/u-boot-rpi3-2019.10_1/GPLv2 /usr/local/share/licenses/u-boot-rpi3-2019.10_1/LICENSE /usr/local/share/licenses/u-boot-rpi3-2019.10_1/catalog.mk /usr/local/share/u-boot/u-boot-rpi3/README /usr/local/share/u-boot/u-boot-rpi3/metadata /usr/local/share/u-boot/u-boot-rpi3/u-boot.bin =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F9B8A0F5-8619-4F8C-9002-58EDE398D93C>