[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5372288A.5010403@ti.com>
Date: Tue, 13 May 2014 10:13:30 -0400
From: Tom Rini <trini@...com>
To: Javier Martinez Canillas <javier@...hile0.org>
CC: Robert Nelson <robertcnelson@...il.com>,
Tony Lindgren <tony@...mide.com>,
Matt Ranostay <mranostay@...il.com>, <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Russell King <linux@....linux.org.uk>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
linux kernel <linux-kernel@...r.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@...il.com>,
Matt Porter <matt.porter@...aro.org>
Subject: Re: [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition
On 05/13/2014 10:06 AM, Javier Martinez Canillas wrote:
> Agreed. I think that until the device tree overlay and the cape
> manager find their way into mainline we should treat capes as if they
> were expansion boards attached to a Computer-on-Module. That is, a
> static based board which its own DTS including the BB{B,W} as an dtsi
> and not something that can be added on runtime.
Sometimes nothing exposes just how big a problem something is (and how
much we need the solution to it) like actually showing the output.
Someone could also start posting the profileN device trees for the
am335x GP EVMs too.
--
Tom
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists