RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)

[Mark Millard]

On 2020-Oct-9, at 13:28, Klaus Cucinauomo <maciphone2 at googlemail.com> wrote:
> 
> Am 09.10.2020 um 21:25 schrieb Mark Millard <marklmi at yahoo.com>:
>> 
>> 
>> Linux has its own dts/dtsi/... sources instead of using the .dtb files
>> from the RPi folks, not directly based on any vintage of the RPi .dtb
>> files if I understand right……………..
> 
> FreeBSD imports the linux-dts :
> https://github.com/freebsd/freebsd/tree/master/sys/gnu/dts/arm64/broadcom

FreeBSD imports lots of linux-dts material that it does not put
to use. Only some of the imported material is used.

release/arm64/RPI3.conf indicates use of:
(There is not RPi4 release yet.)

DTB_DIR="/usr/local/share/rpi-firmware"
DTB="bcm2709-rpi-2-b.dtb bcm2710-rpi-3-b.dtb bcm2710-rpi-3-b-plus.dtb bcm2711-rpi-4-b.dtb"
. . .
EMBEDDEDPORTS="sysutils/u-boot-rpi3 sysutils/rpi-firmware"
. . .
        UBOOT_DIR="/usr/local/share/u-boot/u-boot-rpi3"
. . .
        DTB_FILES="armstub8.bin armstub8-gic.bin bootcode.bin fixup_cd.dat \
                fixup_db.dat fixup_x.dat fixup.dat LICENCE.broadcom \
                start_cd.elf start_db.elf start_x.elf start.elf \
                fixup4.dat fixup4cd.dat fixup4db.dat fixup4x.dat start4.elf \
                start4cd.elf start4db.elf start4x.elf ${DTB}"

. . .
        for _UF in ${UBOOT_FILES}; do
                chroot ${CHROOTDIR} cp -p ${UBOOT_DIR}/${_UF} \
                        ${FATMOUNT}/${_UF}
        done
        for _DF in ${DTB_FILES}; do
                chroot ${CHROOTDIR} cp -p ${DTB_DIR}/${_DF} \
                        ${FATMOUNT}/${_DF}
        done
        chroot ${CHROOTDIR} cp -p ${DTB_DIR}/config_rpi4.txt \
                        ${FATMOUNT}
        chroot ${CHROOTDIR} cp -p ${DTB_DIR}/config_rpi3.txt \
                        ${FATMOUNT}/config.txt
        chroot ${CHROOTDIR} mkdir -p ${FATMOUNT}/overlays
        for _OL in ${OVERLAYS}; do
                chroot ${CHROOTDIR} cp -p ${OL_DIR}/${_OL} \
                        ${FATMOUNT}/overlays/${_OL}
        done

It is not using sys/gnu/dts/arm64/broadcom/ material.


>> ………. I use apt to update the ubuntu microsd card once and a while.
> 
> I simply used the Raspberry Pi Imager(automatically updates itself to latest)
> to get a „reproducible" `latest`- msdos-partition of Ubuntu :

The Raspberry Pi Imager is a way to install RaspiOS to
media from Windows, macOS, ubuntu, or RaspiOS. It does
not install Windows, macOS, or ubuntu but RaspiOS (an
abbreviation of "Raspberry Pi OS").

> https://www.raspberrypi.org/downloads/

ubuntu's RPi* images are available via links from:

https://ubuntu.com/download/raspberry-pi

with arm64 links going to:

https://ubuntu.com/download/raspberry-pi/thank-you?version=20.04.1&architecture=arm64+raspi

These are not via the rpi organization's web site and
www.raspberrypi.org does not provide the ubuntu image(s).


> And it booted FreeBSD on the 4GB-model from SSD(w/o SD-card) (until reported hang)
> ( additionally I changed in config.txt from disable-bt to miniuart-bt)

Looks to be that you were using RaspiOS's DTB and related
materials directly, not ubuntu's materials.


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)