| 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: <54D14B26.4050406@gmail.com> Date: Tue, 03 Feb 2015 23:26:46 +0100 From: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com> To: Arnd Bergmann <arnd@...db.de>, linux-arm-kernel@...ts.infradead.org CC: Antoine Tenart <antoine.tenart@...e-electrons.com>, thomas.petazzoni@...e-electrons.com, zmxu@...vell.com, linux-kernel@...r.kernel.org, jszhang@...vell.com Subject: Re: [PATCH] ARM: berlin: add a defconfig On 03.02.2015 13:54, Arnd Bergmann wrote: > On Tuesday 03 February 2015 12:28:52 Antoine Tenart wrote: >> Marvell Berlin SoCs did not have a custom defconfig and were only >> supported in multi_v7_defconfig. >> >> Adds a proper defconfig, allowing to boot a Berlin SoC with all the >> currently supported features: SMP, Pinmux, AHCI, Ethernet, I2C, GPIO, >> USB, SDHCI. >> >> > > Are there any features that are not currently supported by > multi_v7_defconfig? If so, please also add them there as > loadable modules. Antoine, Arnd, do we really need two potentially diverging defconfigs? I am aware that multi_v7_defconfig adds a lot of stuff that is not required for Berlin, but still I think in terms of coverage (both Berlin and non-Berlin stuff) multi_v7 is sufficient, isn't it? However, if there is a strong desire for Berlin-only defconfig, I'll agree. Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists