From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Tue, 12 Feb 2013 12:26:01 -0700 Subject: [U-Boot] [PATCH v2 2/3] Tegra114: fdt: Update DT files with I2C info for T114/Dalmore In-Reply-To: References: <1360193208-16055-1-git-send-email-twarren@nvidia.com> <1360193208-16055-3-git-send-email-twarren@nvidia.com> <5112EE93.3070407@wwwdotorg.org> <5113EFB8.5080009@wwwdotorg.org> Message-ID: <511A9749.3050903@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 02/12/2013 12:17 PM, Simon Glass wrote: > Hi Tom, > > On Tue, Feb 12, 2013 at 11:13 AM, Tom Warren wrote: ... >> That's the current POR for Tegra DT use in upstream U-Boot, assuming I >> can find an up-to-date kernel with the latest DTS files (I'll use >> Stephen's swarren/linux-tegra.git/for-next until told otherwise). > > Yes that was always my problem - finding what the kernel actually > used, might use, etc. I must say I find this quite puzzling; the kernel repos aren't exactly hidden. Tegra's kernel for-next is likely the best place right now as any DT changes typically go through that tree. However, on the off-chance any other maintainer picks up any changes, linux-next.git would have the latest bindings. That's all been true for a year or more. That said, there is a move to either move the binding definitions and .dts files out of the kernel tree and/or stop taking changes to them through individual SoC trees, but perhaps through the device tree repo. If that does happen, I'll let you know.