Searched hist:"5910 fe02d64647833e54f9a12509ff2b485ed568" (Results 1 – 2 of 2) sorted by relevance
| /freebsd/sys/arm/broadcom/bcm2835/ |
| H A D | bcm2835_vcbus.c | diff 5910fe02d64647833e54f9a12509ff2b485ed568 Mon Dec 09 18:34:40 CET 2019 Kyle Evans <kevans@FreeBSD.org> RPI: Fix DMA/SDHCI on the BCM2836 (Raspberry Pi 2)
r354875 pushed VCBUS <-> ARMC translations to runtime determination, but
incorrectly mapped addresses for the BCM2836 -- SOC_BCM2835 and SOC_BCM2836
are actually mutually exclusive, so the BCM2836 config (GENERIC) would have
taken the latter path in the header and used 0x3f000000 as peripheral start.
Easily fixed -- split out the BCM2836 into its own memmap config and use
that instead if SOC_BCM2836 is included. With this, we get back to userland
again.
Reported by: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl>
|
| H A D | bcm2835_vcbus.h | diff 5910fe02d64647833e54f9a12509ff2b485ed568 Mon Dec 09 18:34:40 CET 2019 Kyle Evans <kevans@FreeBSD.org> RPI: Fix DMA/SDHCI on the BCM2836 (Raspberry Pi 2)
r354875 pushed VCBUS <-> ARMC translations to runtime determination, but
incorrectly mapped addresses for the BCM2836 -- SOC_BCM2835 and SOC_BCM2836
are actually mutually exclusive, so the BCM2836 config (GENERIC) would have
taken the latter path in the header and used 0x3f000000 as peripheral start.
Easily fixed -- split out the BCM2836 into its own memmap config and use
that instead if SOC_BCM2836 is included. With this, we get back to userland
again.
Reported by: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl>
|