RPi4B: modern firmware vs. Device tree loaded to 0x4000 (size 0xbe0c) [fails] vs. to 0x1f0000 (size 0xbd90) [works]?

Robert Crowston crowston at protonmail.com
Mon Oct 12 21:05:13 UTC 2020


The boot time has not been so important to me. Once the system has booted, it is time for a new project. :-)

Actually, what is a lot more interesting for me is network boot. Then I can stop juggling SD cards when I test new kernels.

— RHC.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, 12 October 2020 12:35, Klaus Cucinauomo <maciphone2 at googlemail.com> wrote:

>
>
> > Am 12.10.2020 um 01:13 schrieb Robert Crowston crowston at protonmail.com:
> > ...
> >
> > > > mmc0 is current device
> > >
> > > should not be mmc0 if you boot from USB/SSD
> >
> > I'm still using sd cards.
> > ...
> > — RHC.
>
> The one and only pcie-BOSS itself is forced by armstubs to boot from a poor 10Mb/sWrite SD-card-fingernail…
> This terrible misery must end. ;-) Ha Ha,
> …... that’s why we want to use the xhci-boot feature of 2020.10
>
> Regards
> K.
>> ...
> PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
> starting USB...
> ….
> Device 0: Vendor: JMicron Rev: 3202 Prod: Tech
> Type: Hard Disk
> Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)
> ... is now current device
> Scanning usb 0:1...
> Found EFI removable media binary efi/boot/bootaa64.efi
>>



More information about the freebsd-arm mailing list