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: Thu, 18 Feb 2016 15:34:30 +0100 From: Gregory CLEMENT <gregory.clement@...e-electrons.com> To: Arnd Bergmann <arnd@...db.de> Cc: linux-arm-kernel@...ts.infradead.org, Thierry Reding <thierry.reding@...il.com>, Bjorn Helgaas <bhelgaas@...gle.com>, Andrew Lunn <andrew@...n.ch>, Jason Cooper <jason@...edaemon.net>, linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org, linux-next@...r.kernel.org, Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>, Thomas Petazzoni <thomas.petazzoni@...e-electrons.com> Subject: Re: [PATCH] PCI: mvebu: Restrict build to 32-bit ARM Hi Arnd, On jeu., févr. 18 2016, Arnd Bergmann <arnd@...db.de> wrote: > On Thursday 18 February 2016 14:32:10 Thierry Reding wrote: >> From: Thierry Reding <treding@...dia.com> >> >> This driver uses PCI glue that is only available on 32-bit ARM. This >> used to work fine as long as ARCH_MVEBU and ARCH_DOVE were exclusively >> 32-bit, but that's changed now, with ARCH_MVEBU also being available >> on 64-bit ARM. >> >> Signed-off-by: Thierry Reding <treding@...dia.com> > > Looks fine as a temporary workaround, but I think what we really want to > do here is to remove the dependency, as the new ARM64 platforms are going > to need this driver anyway. Actually the mvebu ARM64 platform we know about (Armada 3700, 7K and 8K), won't use the same controller. A7K/A8K will use a synopsis IP and Armada 3700 a new Marvell IP. So for me depending on ARM32 is enough. Gregory -- Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
Powered by blists - more mailing lists