linux-kernel - Re: [PATCH] ARM: berlin: add a defconfig

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: <20150204085404.GB12908@kwain>
Date:	Wed, 4 Feb 2015 09:54:04 +0100
From:	Antoine Tenart <antoine.tenart@...e-electrons.com>
To:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	linux-arm-kernel@...ts.infradead.org,
	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

Hi Sebastian,

On Tue, Feb 03, 2015 at 11:26:46PM +0100, Sebastian Hesselbarth wrote:
> 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.
> 
> 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?

In term of coverage, multi_v7_defconfig should be sufficient. The main
advantage of having a custom Berlin defconfig would be for me to have a
small kernel image and a configuration to start with without having to
maintain it out of tree, for Berlin related developments.

It's not mandatory, but it's useful at least for me. So the question
is whether we want this defconfig mainlined or out of tree.

Antoine

-- 
Antoine Ténart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
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/