From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: Making ARM multiplatform kernels DT-only?
Date: Thu, 3 May 2012 15:45:46 +0200 [thread overview]
Message-ID: <20120503134546.GB7788@game.jcrosoft.org> (raw)
In-Reply-To: <201205031350.35476.arnd@arndb.de>
On 13:50 Thu 03 May , Arnd Bergmann wrote:
> Hi everyone,
>
> I've been discussing multiplatform kernels with a few people recently,
> and we will have a lot of discussion sessions about this at Linaro
> Connect in Hong Kong.
>
> One question that came up repeatedly is whether we should support all
> possible board files for each platform in a multiplatform kernel,
> or just the ones that are already using DT probing. I would like
> to get a quick poll of opinions on that and I've tried to put those
> people on Cc that would be most impacted by this, i.e. the maintainers
> for platforms that have both DT and non-DT board files at the moment.
>
> My feeling is that we should just mandate DT booting for multiplatform
> kernels, because it significantly reduces the combinatorial space
> at compile time, avoids a lot of legacy board files that we cannot
> test anyway, reduces the total kernel size and gives an incentive
> for people to move forward to DT with their existing boards.
Acked-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
>
> The counterargument is that we won't be able to support all the
> boards we currently do when the user switches on multiplatform,
> but I think that is acceptable.
> Note that I would still want to allow users to build platforms
> separately in order to enable the ATAG style board files, even
> for platforms that are not multiplatform capable.
>
> Other opinions?
it will also avoid us alot of trouble and work to fix old platform that we can
not even test
Best Regards,
J.
next prev parent reply other threads:[~2012-05-03 13:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 13:50 Making ARM multiplatform kernels DT-only? Arnd Bergmann
2012-05-03 13:45 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-05-03 14:04 ` Russell King - ARM Linux
2012-05-03 13:52 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 6:31 ` Deepak Saxena
2012-05-04 7:27 ` Russell King - ARM Linux
2012-05-04 12:20 ` Arnd Bergmann
2012-05-04 16:39 ` Rob Herring
2012-05-04 16:56 ` Russell King - ARM Linux
2012-05-04 16:40 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 16:51 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04 18:56 ` Arnd Bergmann
2012-05-03 14:18 ` Russell King - ARM Linux
2012-05-03 14:23 ` Magnus Damm
2012-05-03 16:27 ` Arnd Bergmann
2012-05-04 9:22 ` Arnaud Patard (Rtp)
2012-05-04 12:34 ` Arnd Bergmann
2012-05-10 10:55 ` Ben Dooks
2012-05-10 11:02 ` Russell King - ARM Linux
2012-05-03 14:46 ` Sascha Hauer
2012-05-04 16:24 ` Arnd Bergmann
2012-05-05 8:09 ` Sascha Hauer
2012-05-05 13:17 ` Arnd Bergmann
2012-05-14 8:54 ` Arnd Bergmann
2012-05-04 5:38 ` Deepak Saxena
2012-05-04 7:39 ` Russell King - ARM Linux
2012-05-04 14:20 ` Wookey
2012-05-04 14:35 ` Russell King - ARM Linux
2012-05-04 15:17 ` Arnd Bergmann
2012-05-04 16:05 ` Wookey
2012-05-04 18:49 ` Arnd Bergmann
2012-05-04 20:03 ` Linus Walleij
2012-05-04 20:42 ` Christian Robottom Reis
2012-05-04 21:05 ` Arnd Bergmann
2012-05-04 22:43 ` Russell King - ARM Linux
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=20120503134546.GB7788@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).