Date: Wed, 5 Oct 2022 23:45:38 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm <freebsd-arm@freebsd.org>, freebsd-uboot@freebsd.org Subject: Re: EDK2 on RPi3 was: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <DC32CA76-5072-4521-BCD8-CDF1512420D4@yahoo.com> In-Reply-To: <3A76826B-B4E6-4837-915E-C9E1172BEA20@yahoo.com> References: <5FFDAA6A-AD8C-4E40-A2EB-4082E5086679@googlemail.com> <38DFEB91-AC60-4FD1-8088-95B0A06C5E5D@yahoo.com> <EEC43DA1-6B68-4FDD-A68A-A3055E86E407@googlemail.com> <20221003004624.GA3381@www.zefox.net> <B32F06DD-DFAF-4CB7-A973-7C07846F6E8E@yahoo.com> <20221004001857.GA7109@www.zefox.net> <62F8D709-BBC3-41C4-B1A9-939B2001BA52@yahoo.com> <1DE565E3-3906-4C53-83C8-EBC20A4E3C95@yahoo.com> <20221005034608.GA12761@www.zefox.net> <1560695E-4D99-40A1-8D62-29EAB24C7997@yahoo.com> <20221005160737.GA15227@www.zefox.net> <136B9190-4C73-45FB-8B41-FEEF7C38A253@yahoo.com> <3A76826B-B4E6-4837-915E-C9E1172BEA20@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I found evidence of a ACPI+DeviceTree vs. just DeviceTree
difference via the boot -v output: note the #Pages of the
BootServicesData and the prior ConventionalMemory area.
ACPI+DeviceTree:
---<<BOOT>>---
GDB: debug ports: uart
GDB: current port: uart
KDB: debugger backends: ddb gdb
KDB: current backend: ddb
WARNING: Cannot find freebsd,dts-version property, cannot check DTB =
compliance
Type Physical Virtual #Pages Attr
. . .
ACPIReclaimMemory 000033b20000 000000000000 00000010 WC WT WB=20
ConventionalMemory 000033b30000 000000000000 00001213 WC WT WB=20
BootServicesData 000034d43000 000000000000 00001ce1 WC WT WB=20
ConventionalMemory 000036a24000 000000000000 000001d2 WC WT WB=20
Just DeviceTree:
---<<BOOT>>---
GDB: debug ports: uart
GDB: current port: uart
KDB: debugger backends: ddb gdb
KDB: current backend: ddb
WARNING: Cannot find freebsd,dts-version property, cannot check DTB =
compliance
Type Physical Virtual #Pages Attr
. . .
ACPIReclaimMemory 000033b20000 000000000000 00000010 WC WT WB=20
ConventionalMemory 000033b30000 000000000000 000011d0 WC WT WB=20
BootServicesData 000034d00000 000000000000 00001d24 WC WT WB=20
ConventionalMemory 000036a24000 000000000000 000001d2 WC WT WB=20
After that 6 lines were different for kernel output to the login
prompt:
A) The temperature line's reported figures varied a little.
B) Just DeviceTree got a:
(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00=20
(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an =
error
(probe0:umass-sim0:0:0:0): Retrying command, 3 more tries remain
sequence; ACPI+DeviceTree did not.
C) The /dev/gpt/CA72USBufs clean/free/frags line's figures were
somewhat different.
D) The time line's figures (after the "Starting background file system
checks in 60 seconds." line) was somewhat different.
That is it for boot -v output differences (non-debug build).
I've switched the RPi3 EDk2 microsd card to use ACPI+DeviceTree.
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DC32CA76-5072-4521-BCD8-CDF1512420D4>