From: Andrew Lunn <andrew@lunn.ch>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: "Florian Fainelli" <florian.fainelli@broadcom.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"René Kjellerup" <rk.katana.steel@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Aleksey Nasibulin" <alealexpro100@ya.ru>,
stable@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: BCM5301X: Extend RAM to full 256MB for Linksys EA6500 V2
Date: Wed, 12 Jul 2023 17:23:21 +0200 [thread overview]
Message-ID: <fc94da45-aba8-4e69-a1a0-c1d58a90c68c@lunn.ch> (raw)
In-Reply-To: <20230712014017.28123-1-ansuelsmth@gmail.com>
> --- 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
next prev parent reply other threads:[~2023-07-12 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 1:40 [PATCH] ARM: dts: BCM5301X: Extend RAM to full 256MB for Linksys EA6500 V2 Christian Marangi
2023-07-12 15:23 ` Andrew Lunn [this message]
2023-07-12 17:07 ` Rafał Miłecki
2023-07-12 17:07 ` Rafał Miłecki
2023-07-12 17:23 ` Florian Fainelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc94da45-aba8-4e69-a1a0-c1d58a90c68c@lunn.ch \
--to=andrew@lunn.ch \
--cc=alealexpro100@ya.ru \
--cc=ansuelsmth@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rk.katana.steel@gmail.com \
--cc=robh+dt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).