[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK2p4sJj7FRVSStVkqmn16sUv8S3vHmUYCU_VzTWAWzqV5yVsg@mail.gmail.com>
Date: Thu, 3 May 2012 22:38:15 -0700
From: Deepak Saxena <dsaxena@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linaro-dev@...ts.linaro.org,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
Linus Walleij <linus.walleij@...aro.org>, shawn.guo@...aro.org,
Sascha Hauer <s.hauer@...gutronix.de>,
Magnus Damm <magnus.damm@...il.com>,
Kukjin Kim <kgene.kim@...sung.com>,
Olof Johansson <olof@...om.net>,
David Brown <davidb@...eaurora.org>,
Nicolas Pitre <nico@...xnic.net>,
Haojian Zhuang <haojian.zhuang@...il.com>,
Jason Cooper <jason@...edaemon.net>,
Nicolas Ferre <nicolas.ferre@...el.com>
Subject: Re: Making ARM multiplatform kernels DT-only?
On 3 May 2012 06:50, Arnd Bergmann <arnd@...db.de> 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.
+1
I'm of the opinion that we support DT only platforms for
multi-platform but this is based on the approach of only caring for
multi-platform for newer systems and not worrying too much for legacy
HW. I look at this from the perspective of how much return do we get
on investing effort into making it possible for every platform to be
built as part of consolidated zImage. I don't expect distros (the
main users of a single zImage IMHO) to spend many cycles on older
platforms and those of us who still have some of them sitting around
to use are generally developers who are going to be doing a lot of
builds anyways...
~Deepak
--
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