[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d05b8e5a-adf7-9057-b42a-0da1fde84953@nvidia.com>
Date: Tue, 20 Sep 2016 18:56:08 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Paul Kocialkowski <contact@...lk.fr>,
<linux-kernel@...r.kernel.org>
CC: <devicetree@...r.kernel.org>,
Stephen Warren <swarren@...dotorg.org>,
Thierry Reding <thierry.reding@...il.com>,
<linux-tegra@...r.kernel.org>,
Alexandre Courbot <gnurou@...il.com>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 3/4] ARM: tegra: nyan-big: Include compatible revisions
for proper detection
On 20/09/16 18:53, Paul Kocialkowski wrote:
> * PGP Signed by an unknown key
>
> Le mardi 20 septembre 2016 à 18:41 +0100, Jon Hunter a écrit :
>> On 28/08/16 18:32, Paul Kocialkowski wrote:
>>>
>>> Depthcharge (the payload used with cros devices) will attempt to detect
>>> boards using their revision. This includes all the known revisions for
>>> the nyan-big board so that the dtb can be selected preferably.
>>
>> May be I am missing something here, but for the mainline there is only
>> one dtb available and so why is this needed for the mainline?
>
> There is indeed a single dts in mainline, but depthcharge will use the revision
> to match the compatible string (e.g. it will look for google,nyan-big-rev5, not
> google,nyan-big), so we need to list them all in that single dts. Otherwise,
> depthcharge will fall back to the default config, which may or may not be
> suitable for nyan.
Is tegra124-nyan-big.dtb not the default?
Jon
--
nvpublic
Powered by blists - more mailing lists