aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm27xx/patches-5.4/950-0655-dts-bcm2711-EMMC2-can-address-the-whole-first-GB.patch
diff options
context:
space:
mode:
Diffstat (limited to 'target/linux/bcm27xx/patches-5.4/950-0655-dts-bcm2711-EMMC2-can-address-the-whole-first-GB.patch')
-rw-r--r--target/linux/bcm27xx/patches-5.4/950-0655-dts-bcm2711-EMMC2-can-address-the-whole-first-GB.patch31
1 files changed, 0 insertions, 31 deletions
diff --git a/target/linux/bcm27xx/patches-5.4/950-0655-dts-bcm2711-EMMC2-can-address-the-whole-first-GB.patch b/target/linux/bcm27xx/patches-5.4/950-0655-dts-bcm2711-EMMC2-can-address-the-whole-first-GB.patch
deleted file mode 100644
index 4c5e50636c..0000000000
--- a/target/linux/bcm27xx/patches-5.4/950-0655-dts-bcm2711-EMMC2-can-address-the-whole-first-GB.patch
+++ /dev/null
@@ -1,31 +0,0 @@
-From 4f2da50bb75ec7b74a23e119062d945626398e30 Mon Sep 17 00:00:00 2001
-From: Phil Elwell <phil@raspberrypi.com>
-Date: Mon, 20 Apr 2020 11:25:18 +0100
-Subject: [PATCH] dts: bcm2711: EMMC2 can address the whole first GB
-
-Although 0xfc000000 looks like an inaccessible RAM address (due to the
-peripheral mappings), with RAM mapped at 0xc0000000 (as it is on the
-30/32-bit VPU bus) this is actually 0x3c000000 in the ARM memory space,
-which is fine.
-
-This difference is potentially the cause of some warnings seen in
-sdhci_send_command.
-
-Fixes: "dts: bcm2711: Move emmc2 to its own 'bus'"
-
-Signed-off-by: Phil Elwell <phil@raspberrypi.com>
----
- arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
---- a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
-+++ b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
-@@ -223,7 +223,7 @@
- #size-cells = <1>;
-
- ranges = <0x0 0x7e000000 0x0 0xfe000000 0x01800000>;
-- dma-ranges = <0x0 0xc0000000 0x0 0x00000000 0x3c000000>;
-+ dma-ranges = <0x0 0xc0000000 0x0 0x00000000 0x40000000>;
-
- emmc2: emmc2@7e340000 {
- compatible = "brcm,bcm2711-emmc2";