linux-kernel - Re: Tegra device name for device tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACxGe6tWC2bQ=cRp=odY+suJe5DVym1L6peurk_Ldu-mY_rTzA@mail.gmail.com>
Date:	Tue, 5 Jul 2011 12:29:56 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Stephen Warren <swarren@...dia.com>
Cc:	"devicetree-discuss@...ts.ozlabs.org" 
	<devicetree-discuss@...ts.ozlabs.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Tegra device name for device tree

On Tue, Jul 5, 2011 at 12:22 PM, Stephen Warren <swarren@...dia.com> wrote:
> Grant et. al.,
>
> It recently dawned on me that all the Tegra DeviceTree support is using a
> marketing name for the SoC ("tegra250"). NVIDIA would prefer that we use
> engineering names for the SoC (e.g. "tegra20" now, "tegra30" for an
> upcoming SoC). The primary motivation for this is that engineering names
> tend to be more stable and map more directly to the HW design.
>
> Is it still possible to make this change, if I submit the appropriate
> patches to do this?

Yes, please do.  I'm completely in support of that.

> So, far, I see devicetree/next only refers to the Tegra serial port,
> whereas devicetree/arm and devicetree/test refer to more Tegra devices in
> this way. I'm not quite sure how the flow of patches works between these 3
> trees. For the serial port, I obviously need to submit a patch against
> devicetree/next, but I'm not so sure about which of devicetree/arm or
> devicetree/test to target for the other devices.

devicetree/next is the stuff I'm actually merging.  devicetree/test is
stuff being experimented with, and devicetree/arm is stuff I expect to
get merged, but I'm not actually merging through my tree (or just
isn't quite ready yet).  You can use devicetree/test as a staging
ground for getting things ready for upstream.  Let me know if anything
you see in devicetree/test needs to get upstreamed ASAP because your
work depends on it, and we'll figure out how/when to get it done.

g.


>
> Sorry for bringing this up so late in the game.
>
> Thanks!
>
> --
> nvpublic
>
>



-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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/