From: Thirupathaiah Annapureddy Date: Mon, 23 Mar 2020 22:42:44 -0700 Subject: [PATCH v3 1/1] cmd: bootefi: Parse reserved-memory node from DT In-Reply-To: <90cb2956-82ed-df4e-cce7-793008c9f51b@gmx.de> References: <20200315120314.15398-1-xypron.glpk@gmx.de> <05ed603719164a58bbca4af170dab35f@SFHDAG6NODE3.st.com> <90cb2956-82ed-df4e-cce7-793008c9f51b@gmx.de> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 3/17/2020 4:10 AM, Heinrich Schuchardt wrote: > On 3/17/20 9:06 AM, Patrick DELAUNAY wrote: >> Hi, >> >>> From: U-Boot On Behalf Of Heinrich Schuchardt >>> Sent: dimanche 15 mars 2020 13:03 >>> > > It makes sense to keep these coding stretches in sync. > > @Thirupathaiah > * I did not find any example in the Linux code where a status for > ? a subnode of /reserved-memory was specified. Where did you > ? observe reserved memory not having status="okay"? A child node of /reserved-memory may be declared in a SOC specific dtsi file. But a given board's dts file may chose to disable this i.e. it does not need to reserve this memory. > * Does Linux check the status? yes, it checks. __fdt_scan_reserved_mem() -> of_fdt_device_is_available() Best Regards, Thiru