lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 23 Jan 2018 15:11:50 +0800 From: Shawn Guo <shawnguo@...nel.org> To: Rasmus Villemoes <rasmus.villemoes@...vas.dk> Cc: Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, Russell King <linux@...linux.org.uk>, devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v2] ARM: dts: ls1021a: add nodes for on-chip ram On Wed, Jan 03, 2018 at 04:45:45PM +0100, Rasmus Villemoes wrote: > Although the two nodes constitute one contiguous 128K region, still > describe them separately: > > - That's how they are described in the reference manual: "Each OCRAM > occupies a 64 KB of address region...", and the names ocram1 and > ocram2 are also as used in the manual. > > - The two areas are treated differently by the boot ROM code: OCRAM2 is > zero-initialized, while, again quoting the RM, "software must perform > the zero initialization of OCRAM1." > > Signed-off-by: Rasmus Villemoes <rasmus.villemoes@...vas.dk> Applied, thanks.
Powered by blists - more mailing lists