Re: RPi4B: modern firmware vs. Device tree loaded to 0x4000 (size 0xbe0c) [fails] vs. to 0x1f0000 (size 0xbd90) [works]?
Robert Crowston via freebsd-arm <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <Tu1E1Q_qbalMQOG4gpQ8UHFBKbUCZU8uc9pZVXnI2T6b3sUK0gzwh1LjhxZHOE6ZQT-q7qpylhQ_fzHMSjKxHSifllMeJ1cXGbOIGJ8Chxo=@protonmail.com> |
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 <[email protected]> wrote: > > > > Am 12.10.2020 um 01:13 schrieb Robert Crowston [email protected]: > > ... > > > > > > 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 > … > — _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "[email protected]"