From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: berlin: add a defconfig
Date: Tue, 03 Feb 2015 23:26:46 +0100 [thread overview]
Message-ID: <54D14B26.4050406@gmail.com> (raw)
In-Reply-To: <3962783.sVjmOB1hYm@wuerfel>
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
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: Antoine Tenart <antoine.tenart@free-electrons.com>,
thomas.petazzoni@free-electrons.com, zmxu@marvell.com,
linux-kernel@vger.kernel.org, jszhang@marvell.com
Subject: Re: [PATCH] ARM: berlin: add a defconfig
Date: Tue, 03 Feb 2015 23:26:46 +0100 [thread overview]
Message-ID: <54D14B26.4050406@gmail.com> (raw)
In-Reply-To: <3962783.sVjmOB1hYm@wuerfel>
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
next prev parent reply other threads:[~2015-02-03 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 11:28 [PATCH] ARM: berlin: add a defconfig Antoine Tenart
2015-02-03 11:28 ` Antoine Tenart
2015-02-03 12:54 ` Arnd Bergmann
2015-02-03 12:54 ` Arnd Bergmann
2015-02-03 13:47 ` Antoine Tenart
2015-02-03 13:47 ` Antoine Tenart
2015-02-03 22:26 ` Sebastian Hesselbarth [this message]
2015-02-03 22:26 ` Sebastian Hesselbarth
2015-02-04 8:54 ` Antoine Tenart
2015-02-04 8:54 ` Antoine Tenart
2015-02-04 10:26 ` Arnd Bergmann
2015-02-04 10:26 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54D14B26.4050406@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.