linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Florian Vaussard <florian.vaussard@epfl.ch>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	"Kevin Hilman" <khilman@linaro.org>, "Nishanth Menon" <nm@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] ARM: dts: Fixes for Overo/Tobi against 3.14-rc2
Date: Thu, 13 Feb 2014 15:36:52 -0800	[thread overview]
Message-ID: <20140213233652.GU28216@atomide.com> (raw)
In-Reply-To: <1392287116-4548-1-git-send-email-florian.vaussard@epfl.ch>

* Florian Vaussard <florian.vaussard@epfl.ch> [140213 02:28]:
> OMAP36xx-based Overo (Storm and alike) are now failing to boot with 3.14-rc2 [1].
> This series fixes this, by moving model-agnostic DT into a common dtsi file,
> and creating model-specific DT files:
> 
> - omap3-overo-tobi.dts -> older OMAP35xx Overo
> - omap3-overo-storm-tobi.dts -> newer OMAP36xx/AM37xx/DM37xx Overo
> 
> People will have to use the right Overo / expansion board combination.
> 
> (Patch 2 in an unrelated fix that was waiting in my queue.)
> 
> omap3-overo-tobi.dts tested with Overo Sand (OMAP3503) and omap3-overo-storm-tobi.dts
> tested with Overo EarthStorm (AM3703). Both boot. With the Overo Sand, I cannot
> mount the ext3 rootfs, but this seems unrelated to the current topic, maybe
> a missing errata.

Applying patches 1 to 3 into omap-for-v3.14/fixes thanks, the last
one still seems to have discussion going.

Tony

      parent reply	other threads:[~2014-02-13 23:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 10:25 [PATCH v2 0/4] ARM: dts: Fixes for Overo/Tobi against 3.14-rc2 Florian Vaussard
2014-02-13 10:25 ` [PATCH v2 1/4] ARM: dts: omap3-tobi: Fix boot with OMAP36xx-based Overo Florian Vaussard
2014-02-13 14:41   ` Nishanth Menon
2014-02-13 10:25 ` [PATCH v2 2/4] ARM: dts: omap3-tobi: Use the correct vendor prefix Florian Vaussard
2014-02-13 14:41   ` Nishanth Menon
2014-02-13 10:25 ` [PATCH v2 3/4] ARM: dts: Add support for both OMAP35xx and OMAP36xx Overo/Tobi Florian Vaussard
2014-02-13 14:41   ` Nishanth Menon
2014-02-13 10:25 ` [PATCH v2 4/4] Documentation: dt: OMAP: Update Overo/Tobi Florian Vaussard
2014-02-13 14:43   ` Nishanth Menon
2014-02-14  7:58     ` Florian Vaussard
2014-02-14  8:14       ` Nishanth Menon
2014-02-14 16:39         ` Tony Lindgren
2014-02-13 23:36 ` Tony Lindgren [this message]

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=20140213233652.GU28216@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=florian.vaussard@epfl.ch \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@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).