[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fc94da45-aba8-4e69-a1a0-c1d58a90c68c@lunn.ch>
Date: Wed, 12 Jul 2023 17:23:21 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Florian Fainelli <florian.fainelli@...adcom.com>,
Hauke Mehrtens <hauke@...ke-m.de>,
Rafał Miłecki <zajec5@...il.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@...adcom.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
René Kjellerup <rk.katana.steel@...il.com>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Aleksey Nasibulin <alealexpro100@...ru>, stable@...r.kernel.org
Subject: Re: [PATCH] ARM: dts: BCM5301X: Extend RAM to full 256MB for Linksys
EA6500 V2
> --- a/arch/arm/boot/dts/broadcom/bcm4708-linksys-ea6500-v2.dts
> +++ b/arch/arm/boot/dts/broadcom/bcm4708-linksys-ea6500-v2.dts
> @@ -19,7 +19,8 @@ chosen {
>
> memory@0 {
> device_type = "memory";
> - reg = <0x00000000 0x08000000>;
> + reg = <0x00000000 0x08000000>,
> + <0x88000000 0x08000000>;
So there is a hole in the middle? Does this require any special
CONFIG_ option to support sparse memory?
Andrew
Powered by blists - more mailing lists