linux-kernel - RE: [PATCH] arm64: dts: realtek: Add Realtek rtd1619 and mjolnir

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7c94c59649c04442886a98c057c07654@realtek.com>
Date:   Sun, 17 Nov 2019 15:39:28 +0000
From:   James Tai <james.tai@...ltek.com>
To:     Andreas Färber <afaerber@...e.de>
CC:     "linux-realtek-soc@...ts.infradead.org" 
        <linux-realtek-soc@...ts.infradead.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
        Mark Rutland <mark.rutland@....com>,
        "Rob Herring" <robh+dt@...nel.org>
Subject: RE: [PATCH] arm64: dts: realtek: Add Realtek rtd1619 and mjolnir

Hi Andreas,

> > Sorry for my misunderstanding. The RAM region don't require two cells
> > for memory nodes, so I'll fix it in v3 patch.
> 
> Should I then also change RTD1395 to use only one cell, or does it support
> more RAM than RTD1619?

Yes, you can. The memory capacity of RTD1395 and RTD1619 are the same.

> By my calculation 0x98000000 is less than 2.4 GiB! So, does RAM continue
> between r-bus and GIC, similar to how it does on RTD1195? Then we need to
> exclude those RAM ranges from the SoC node (adjusting 0x68000000).

We need to reserve memory address for r-bus and GIC and exclude those RAM range from the SoC node.