Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
bob prohaska <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
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 [email protected]:/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 [email protected]:/usr/obj/usr/src/arm.armv7/sys/GENERIC-MMCCAM arm 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 reading, bob prohaska _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "[email protected]"