From: Arnd Bergmann <arnd@arndb.de>
To: Roland Stigge <stigge@antcom.de>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Defconfig update for LPC32xx
Date: Fri, 20 Apr 2012 14:54:08 +0000 [thread overview]
Message-ID: <201204201454.09200.arnd@arndb.de> (raw)
In-Reply-To: <4F904795.4050505@antcom.de>
On Thursday 19 April 2012, Roland Stigge wrote:
> Hi,
>
> I'm planning to update arch/arm/configs/lpc32xx_defconfig, adjusting to
> device tree and new driver options.
>
> Now I wonder if I should (1) just add drivers which are used on the
> reference machine (PHYTEC LPC3250 board) or (2) additionally add all
> drivers that I have seen together with LPC32xx on other boards also,
> which would demonstrate that the same binary kernel runs on all LPC32xx
> machines, but increasing kernel size a bit.
>
> I would prefer option (2) but first want to ask for advice.
I think either way is fine, this is one of the things I would completely
leave to you as the platform maintainer.
If you know that other machines are working with the same defconfig,
it would be helpful to also have their .dts files in the kernel source
for reference, but not mandatory.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Defconfig update for LPC32xx
Date: Fri, 20 Apr 2012 14:54:08 +0000 [thread overview]
Message-ID: <201204201454.09200.arnd@arndb.de> (raw)
In-Reply-To: <4F904795.4050505@antcom.de>
On Thursday 19 April 2012, Roland Stigge wrote:
> Hi,
>
> I'm planning to update arch/arm/configs/lpc32xx_defconfig, adjusting to
> device tree and new driver options.
>
> Now I wonder if I should (1) just add drivers which are used on the
> reference machine (PHYTEC LPC3250 board) or (2) additionally add all
> drivers that I have seen together with LPC32xx on other boards also,
> which would demonstrate that the same binary kernel runs on all LPC32xx
> machines, but increasing kernel size a bit.
>
> I would prefer option (2) but first want to ask for advice.
I think either way is fine, this is one of the things I would completely
leave to you as the platform maintainer.
If you know that other machines are working with the same defconfig,
it would be helpful to also have their .dts files in the kernel source
for reference, but not mandatory.
Arnd
next prev parent reply other threads:[~2012-04-20 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 17:12 Defconfig update for LPC32xx Roland Stigge
2012-04-19 17:12 ` Roland Stigge
2012-04-20 14:54 ` Arnd Bergmann [this message]
2012-04-20 14:54 ` 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=201204201454.09200.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stigge@antcom.de \
/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.