Date: Mon, 11 Sep 2017 01:48:49 -0700 From: Mark Millard <markmi@dsl-only.net> To: Emmanuel Vadot <manu@bidouilliste.com>, Tim Kientzle <tim@kientzle.com> Cc: FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Missing in action during arm64/aarch64 builds: no pine64_plus.dtb to be found from buildkernel, installkernel, or u-boot-pine64 Message-ID: <A3B82DE7-37B3-4566-8EE3-7967CE2ADCE2@dsl-only.net> In-Reply-To: <20170911095641.616658985e7148a88f6c03a7@bidouilliste.com> References: <DB33811B-1DB8-4461-A8D4-78B7118A547C@dsl-only.net> <20170911095641.616658985e7148a88f6c03a7@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-Sep-11, at 12:56 AM, Emmanuel Vadot <manu at bidouilliste.com> = wrote: > On Sat, 9 Sep 2017 16:35:11 -0700 > Mark Millard <markmi at dsl-only.net> wrote: >=20 >> The context here is head -r323246 amd64 -> arm64/aarch64 >> cross build activity. >>=20 >> =46rom installkernel : >>=20 >> # find /usr/obj/DESTDIRs/clang-cortexA53-installkernel/ -name "*.dtb" = -print >> #=20 >>=20 >> =46rom buildkernel : >>=20 >> # find /usr/obj/cortexA53_clang/arm64.aarch64/ -name "*.dtb" -print >> #=20 >>=20 >> =46rom installing u-boot-pine64 : >>=20 >> # ls -lTd /usr/local/share/u-boot/u-boot-pine64/* >> -rw-r--r-- 1 root wheel 125 Sep 6 00:49:44 2017 = /usr/local/share/u-boot/u-boot-pine64/README >> -rw-r--r-- 1 root wheel 505940 Sep 6 00:49:43 2017 = /usr/local/share/u-boot/u-boot-pine64/u-boot-sunxi-with-spl.bin >>=20 >>=20 >> As stands the file must be manually produced. >=20 > Since the latest update of u-boot-pine64 the dtb is included in = u-boot. > U-Boot loads it and pass it to boot1.efi. Cool . . . Trying: # mv /boot/efi/dtb/pine64_plus.dtb /boot/efi/dtb/no_pine64_plus.dtb # shutdown -r now does reboot just fine. As does: # rm -fr /boot/efi/dtb # shutdown -r now A cold boot also boots into the kernel. So no .dts or .dtb is needed for the Pine64+ 2GB . For reference after this: # mount /dev/label/PINE642GAroot on / (ufs, NFS exported, local, noatime, = soft-updates, nfsv4acls) devfs on /dev (devfs, local, multilabel) /dev/label/PINE642GAboot on /boot/efi (msdosfs, local, noatime) # find /boot/efi /boot/efi /boot/efi/startup.nsh /boot/efi/EFI /boot/efi/EFI/BOOT /boot/efi/EFI/BOOT/bootaa64.efi /boot/efi/System Volume Information /boot/efi/System Volume Information/WPSettings.dat I have no clue if this hidden dtb contributes to the USB problem(s) or not: . . . cryptosoft0: <software crypto> NULL mp in getnewvnode(9), tag crossmp Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 ugen0.1: <Generic OHCI root HUB> at usbus0 uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on = usbus0 uhub_attach: getting USB 2.0 HUB descriptor = failed,error=3DUSB_ERR_SHORT_XFER device_attach: uhub0 attach returned 6 usbus0: Root HUB problem, error=3DUSB_ERR_NO_ROOT_HUB mmcsd0: 32GB <SDHC SE32G 8.0 SN 09781303 MFG 07/2017 by 3 SD> at mmc0 = 50.0MHz/4bit/65535-block . . . My old -r308??? context not only could use usb devices but had the root file system on a USB SSD. But modernizing made plugged in USB devices not show up. >> crochet goes to the trouble to have logic to >> build and install pine64_plus.dtb (based on >> arm64/pine64_plus.dts ). Looks like crochet does not need to produce the .dtb . It is not even clear that if a dtb/pine64_plus.dtb exists that it is used for anything. >> Is pine64_plus.dtb required for the likes of >> Pine64+ 2GB's? Now answered as: no. >> If yes: should it be automatically >> built and installed someplace for arm64/aarch64 >> builds (even if more manual steps are required to >> have the final placement on the Pine64 media)? =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A3B82DE7-37B3-4566-8EE3-7967CE2ADCE2>