From: Tony Lindgren <tony@atomide.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
devicetree-discuss@lists.ozlabs.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: OMAP2+: kconfig: Enable devicetree by default for OMAP2+ systems
Date: Tue, 13 Dec 2011 14:38:56 -0800 [thread overview]
Message-ID: <20111213223855.GW32251@atomide.com> (raw)
In-Reply-To: <4EE75448.4010701@ti.com>
* Cousson, Benoit <b-cousson@ti.com> [111213 05:02]:
> On 12/13/2011 2:27 PM, Tomi Valkeinen wrote:
> >Hi,
> >
> >On Tue, 2011-12-06 at 17:49 +0100, Benoit Cousson wrote:
> >>devicetree will become the mandatory boot method for OMAP2+.
> >>In order to avoid cluttering the OMAP code with #ifdef CONFIG_OF,
> >>select USE_OF by default for every OMAP2+ systems.
> >>Select as well the APPENDED_DTB and ATAG_DTB_COMPAT to allow legacy
> >>boot loader to keep working properly.
> >
> >APPENDED_DTB sounds a bit dangerous to be enabled by default according
> >to the config help text.
>
> The help is indeed really scary :-)
Heh, but it's also true.
> Tony,
> Do we want to keep it by default? Or should we fix the kconfig help?
Let's just leave out those two from omap2plus_defconfig then.
Regards,
Tony
next prev parent reply other threads:[~2011-12-13 22:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 16:49 [PATCH 1/3] ARM: OMAP2+: kconfig: Enable devicetree by default for OMAP2+ systems Benoit Cousson
2011-12-13 13:27 ` Tomi Valkeinen
2011-12-13 13:34 ` Cousson, Benoit
2011-12-13 22:38 ` Tony Lindgren [this message]
2011-12-15 16:28 ` Cousson, Benoit
[not found] ` <20111213223855.GW32251-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2011-12-16 15:25 ` Cousson, Benoit
2011-12-17 0:20 ` Tony Lindgren
2012-01-04 20:11 ` Grant Likely
[not found] ` <CACxGe6sAEs4H4FR75psy74x9V3mbp6wAdryJbDu8HBZ4tMmyvw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-06 16:37 ` Cousson, Benoit
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=20111213223855.GW32251@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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).