linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
	Kukjin Kim <kgene.kim@samsung.com>,
	linaro-dev@lists.linaro.org, Jason Cooper <jason@lakedaemon.net>,
	Nicolas Pitre <nico@fluxnic.net>,
	Tony Lindgren <tony@atomide.com>,
	Nicolas Ferre <nicolas.ferre@atmel.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-kernel@vger.kernel.org,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Deepak Saxena <dsaxena@linaro.org>,
	Olof Johansson <olof@lixom.net>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	David Brown <davidb@codeaurora.org>,
	shawn.guo@linaro.org,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Subject: Re: Making ARM multiplatform kernels DT-only?
Date: Sat, 5 May 2012 10:09:36 +0200	[thread overview]
Message-ID: <20120505080936.GP4141@pengutronix.de> (raw)
In-Reply-To: <201205041624.17850.arnd@arndb.de>

On Fri, May 04, 2012 at 04:24:17PM +0000, Arnd Bergmann wrote:
> On Thursday 03 May 2012, Sascha Hauer wrote:
> > I don't think that enforcing DT only in multiplatform kernels will speed
> > up porting to DT. As a platform maintainer I am interested in building
> > multiplatform Kernels, but our customers are mostly uninterested in
> > this. They probably disable other platforms anyway to save the binary space.
> 
> I was not asking about enabling multiple board files but multiple mach-*
> directories, 

Yes, I understood that.

> which is something that I'm probably more interested in than
> you are, and the customers you refer to would certainly not do that if
> they only want to run on one board.
> 
> This is really about people who distribute kernels that run on a wide
> variety of machines across soc vendor boundaries, people like
> ubuntu or cyanogenmod. The question is really whether you see a reason
> why they should enable the 25 non-DT board files on your platform, rather
> than helping out getting DT support for the machines they are
> interested in?

They should not if they are not interested in these boards, but why
shouldn't I be able to enable these 25 boards plus a few atmel or pxa
boards?

When there are technical reasons to limit a multiplatform Kernel to DT
only, then fine, lets do it that way. If there are no technical reasons
and this limitation shall only be used to put some political pressure on
platform board maintainers, then I am against it. Look around, people
actually *are* porting their boards over to device tree, I don't think
that such pressure is necessary.

Only my two cents, it's not that important to me since I want to port my
(relevant) boards over to DT anyway, so I won't argue about this.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2012-05-05  8:09 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
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
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 [this message]
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=20120505080936.GP4141@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=arnd@arndb.de \
    --cc=davidb@codeaurora.org \
    --cc=dsaxena@linaro.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=jason@lakedaemon.net \
    --cc=kgene.kim@samsung.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=nico@fluxnic.net \
    --cc=nicolas.ferre@atmel.com \
    --cc=olof@lixom.net \
    --cc=plagnioj@jcrosoft.com \
    --cc=shawn.guo@linaro.org \
    --cc=tony@atomide.com \
    /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).