linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.pitre@linaro.org (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: allow for ATAGS to be configured out when DT support is selected
Date: Mon, 3 Sep 2012 22:56:26 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.02.1209032249200.1784@xanadu.home> (raw)
In-Reply-To: <201209012025.27962.arnd@arndb.de>

On Sat, 1 Sep 2012, Arnd Bergmann wrote:

> On Thursday 30 August 2012, Nicolas Pitre wrote:
> > Now that ATAGS support is well contained, we can easily remove it from
> > the kernel build if so desired.  It has to explicitly be disabled, and
> > only when DT support is selected.
> > 
> > Note: disabling kernel ATAGS support does not prevent the usage of
> > CONFIG_ARM_ATAG_DTB_COMPAT.
> 
> > ...
> 
> > +config ATAGS
> > +	bool "Support for the traditional ATAGS boot data passing" if USE_OF
> > +	default y
> > +	help
> > +	  This is the traditional way of passing data to the kernel at boot
> > +	  time. If you are solely relying on the flattened device tree (or
> > +	  the ARM_ATAG_DTB_COMPAT option) then you may unselect this option
> > +	  to remove ATAGS support from your kernel binary.  If unsure,
> > +	  leave this to y.
> 
> That's a clever way of implementing it, I had not though of making it an
> optional default-y symbol.
> 
> Acked-by: Arnd Bergmann <arnd@arndb.de>

Thanks.

> Should we do patches to the individual platforms bsaed on this to disable
> the ATAG based board files when CONFIG_ATAG is disabled?

Well... that could be a good thing to make them depend on ATAGS indeed.  
But that can be done incrementally in later patches.


Nicolas

  reply	other threads:[~2012-09-04  2:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30 21:10 [PATCH 1/2] ARM: split out ATAGS parsing Nicolas Pitre
2012-08-30 21:10 ` [PATCH 2/2] ARM: allow for ATAGS to be configured out when DT support is selected Nicolas Pitre
2012-09-01  0:23   ` Linus Walleij
2012-09-01  1:48     ` Nicolas Pitre
2012-09-01 20:25   ` Arnd Bergmann
2012-09-04  2:56     ` Nicolas Pitre [this message]
2012-09-02 15:54   ` Will Deacon
2012-09-04  2:47     ` Nicolas Pitre
2012-09-05  5:24   ` Olof Johansson

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=alpine.LFD.2.02.1209032249200.1784@xanadu.home \
    --to=nicolas.pitre@linaro.org \
    --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).