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: Wed, 8 Nov 2017 10:48:15 +0100 From: Arnd Bergmann <arnd@...db.de> To: Greentime Hu <green.hu@...il.com> Cc: greentime@...estech.com, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-arch <linux-arch@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, Jason Cooper <jason@...edaemon.net>, Marc Zyngier <marc.zyngier@....com>, Rob Herring <robh+dt@...nel.org>, Networking <netdev@...r.kernel.org>, Vincent Chen <vincentc@...estech.com> Subject: Re: [PATCH 20/31] nds32: L2 cache support On Wed, Nov 8, 2017 at 6:55 AM, Greentime Hu <green.hu@...il.com> wrote: > From: Greentime Hu <greentime@...estech.com> > > Signed-off-by: Vincent Chen <vincentc@...estech.com> > Signed-off-by: Greentime Hu <greentime@...estech.com> > + > +/* This is defined for head.S to use due to device tree is not yet built. */ > +#define L2CC_PA_BASE 0x90F00000 This looks problematic, since it prevents you from using the same head.S for multiple SoCs that have different L2 controllers or that have them at different addresses. What does head.S actually do to the L2CC? Could the boot protocol require that to be done by the boot loader before entering the kernel instead? Arnd
Powered by blists - more mailing lists