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
| ||
|
Message-ID: <20230406152511.GA3117403-robh@kernel.org> Date: Thu, 6 Apr 2023 10:25:11 -0500 From: Rob Herring <robh@...nel.org> To: Lorenzo Bianconi <lorenzo@...nel.org> Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com, kuba@...nel.org, matthias.bgg@...il.com, linux-mediatek@...ts.infradead.org, nbd@....name, john@...ozen.org, sean.wang@...iatek.com, Mark-MC.Lee@...iatek.com, lorenzo.bianconi@...hat.com, daniel@...rotopia.org, krzysztof.kozlowski+dt@...aro.org, devicetree@...r.kernel.org Subject: Re: [PATCH v2 net-next 00/10] mtk: wed: move cpuboot, ilm and dlm in dedicated dts nodes On Fri, Mar 31, 2023 at 03:12:36PM +0200, Lorenzo Bianconi wrote: > Since cpuboot, ilm and dlm memory region are not part of MT7986 SoC RAM, That's not really a requirement. Is that the only "problem" here? Certainly going from a standard binding to a custom phandle reference is not an improvement. > move them in dedicated mt7986a syscon dts nodes. What makes them a syscon? Are they memory or h/w registers? Can't be both... Perhaps mmio-sram? > At the same time we keep backward-compatibility with older dts version where > cpuboot, ilm and dlm were defined as reserved-memory child nodes. Doesn't really seem big enough issue to justify carrying this. Rob
Powered by blists - more mailing lists