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

[Mark Millard]

On 2020-Oct-8, at 19:49, bob prohaska <fbsd at www.zefox.net> wrote:

> On Thu, Oct 08, 2020 at 09:27:22PM -0500, Kyle Evans wrote:
>> On Thu, Oct 8, 2020 at 9:18 PM bob prohaska <fbsd at www.zefox.net> wrote:
>>> 
>>> On Thu, Oct 08, 2020 at 01:34:12PM -0500, Kyle Evans wrote:
>>>> 
>>>> Here's a patch that I hacked out and can't test for quite a while yet,
>>>> feel free to give it a shot:
>>>> https://people.freebsd.org/~kevans/bcm2835_vcbus.diff  -- the best
>>>> guarantee I can give you is that it builds. We'll need to test it on
>>>> both RPi4 models with the separate bus and the original RPi4s, as well
>>>> as an RPi3 and RPi2/0w.
>>>> 
>>> 
>>> FWIW, a Pi3B running
>>> FreeBSD www.zefox.org 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r366466M: Thu Oct  8 17:18:55 PDT 2020     bob at www.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC  arm64
>>> 
>>> seems to build, boot and run without immediate problems.
>>> 
>>> A Pi2 running
>>> FreeBSD www.zefox.com 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r365692: Thu Oct  8 16:57:50 PDT 2020     bob at www.zefox.com:/usr/obj/usr/src/arm.armv7/sys/GENERIC-MMCCAM  arm

RPi2 <= v1.1? (32-bit only, bcm2709-rpi-2-b.dtb from https://github.com/Hexxeh/rpi-firmware/ )
RPi2 >= v1.2? (64-bit and 32-bit capable, bcm2710-rpi-2-b.dtb )

I've not looked at the differences in the .dtb files.

>>> also built, booted and ran.
>>> 
>>> Uptime so far is only a few minutes, but so far, so good. If the MMCCAM
>>> mismatch is significant let me know and I'll fix it.
>>> 
>> 
>> Thanks for testing!
>> 
>> Can you also confirm the output of `dmesg | grep 'WARNING:'`, please?
>> In particular, I'd like to know if you hit either of:
>> 
>> WARNING: Improper peripheral attachment ...
>> WARNING: bus for '...' missing dma-ranges
>> 
> 
> On the Pi2 I see:
> bob at www:~ % dmesg | grep 'WARNING:'
> WARNING: WITNESS option enabled, expect reduced performance.
> WARNING: Device "openfirm" is Giant locked and may be deleted before FreeBSD 13.0.
> WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0.
> WARNING: Device "fb" is Giant locked and may be deleted before FreeBSD 13.0.
> WARNING: WITNESS option enabled, expect reduced performance.
> 
> On the Pi3 I see:
> bob at www:~ % dmesg | grep 'WARNING:'
> WARNING: WITNESS option enabled, expect reduced performance.
> WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0.
> WARNING: Device "openfirm" is Giant locked and may be deleted before FreeBSD 13.0.
> WARNING: Device "fb" is Giant locked and may be deleted before FreeBSD 13.0.
> WARNING: WITNESS option enabled, expect reduced performance.
> 
> so the answer seems to be "no".
> 
> HTH, let me know if I can try anthing else. Both installs are expendable.


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