From: Nishanth Menon <nm@ti.com>
To: florian.vaussard@epfl.ch, Tero Kristo <t-kristo@ti.com>,
Kevin Hilman <khilman@linaro.org>,
kernel-build-reports@lists.linaro.org,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
"tony@atomide.com" <tony@atomide.com>
Cc: Mike Turquette <mturquette@linaro.org>,
linux-omap <linux-omap@vger.kernel.org>,
Olof Johansson <olof@lixom.net>, Ash Charles <ash@gumstix.com>
Subject: Re: next boot: 34 pass, 5 fail (next-20140122)
Date: Thu, 23 Jan 2014 11:33:50 -0600 [thread overview]
Message-ID: <52E1527E.8020509@ti.com> (raw)
In-Reply-To: <52E144BC.4000900@epfl.ch>
On 01/23/2014 10:35 AM, Florian Vaussard wrote:
>
[..]
>
> Ok, so with your patch and changing the include from omap34xx to
> omap36xx, it works. Now I have to come up with a way to manage all the
> versions without duplicating all the DT files :-(
you'd also want to be careful about the omap3_pmx_core2 Vs
omap3_pmx_core2 split for padconf.
options that come to mind are:
a) split omap3-overo.dtsi into omap3-overo-common.dtsi
omap3-overo-34xx.dtsi,omap3-overo-36xx.dtsi, corresponding tobi board
dts file include as needed
b) only have common stuff in omap3-overo.dtsi, include omap34xx.dtsi
or omap36xx.dtsi in corresponding tobi board dts.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-01-23 17:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52e06652.c103450a.79d7.6517@mx.google.com>
2014-01-23 1:35 ` next boot: 34 pass, 5 fail (next-20140122) Kevin Hilman
2014-01-23 6:23 ` Tero Kristo
2014-01-23 8:14 ` Florian Vaussard
2014-01-23 9:00 ` Tero Kristo
2014-01-23 9:15 ` Florian Vaussard
2014-01-23 9:41 ` Florian Vaussard
2014-01-23 12:27 ` Tero Kristo
2014-01-23 16:35 ` Florian Vaussard
2014-01-23 17:33 ` Nishanth Menon [this message]
2014-01-24 20:37 ` Florian Vaussard
2014-01-23 17:35 ` Tony Lindgren
2014-01-24 18:00 ` Tony Lindgren
2014-01-24 20:51 ` Florian Vaussard
2014-01-24 18:11 ` Tony Lindgren
2014-01-24 18:13 ` Florian Vaussard
2014-02-05 15:23 ` Kevin Hilman
2014-02-06 8:47 ` Florian Vaussard
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=52E1527E.8020509@ti.com \
--to=nm@ti.com \
--cc=ash@gumstix.com \
--cc=florian.vaussard@epfl.ch \
--cc=kernel-build-reports@lists.linaro.org \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=olof@lixom.net \
--cc=t-kristo@ti.com \
--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).