From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Subject: Re: [PATCH 0/2] Character literal parsing Date: Fri, 24 Jun 2011 15:34:51 -0600 Message-ID: References: <1308871239-32683-1-git-send-email-robotboy@chromium.org> <8yawrgb3smr.fsf@huya.qualcomm.com> <8yafwmz3pg3.fsf@huya.qualcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <8yafwmz3pg3.fsf-AOX6H5vLt3Uj8izMo0bVsAC/G2K4zDHf@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: David Brown Cc: Anton Staaf , devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org List-Id: devicetree@vger.kernel.org On Fri, Jun 24, 2011 at 3:11 PM, David Brown wrote: > On Fri, Jun 24 2011, Anton Staaf wrote: > >> On Fri, Jun 24, 2011 at 1:02 PM, David Brown wro= te: >> >> >> =A0 =A0 Does this mean that the dtc inside the kernel is going to be the >> =A0 =A0 required tool to use to build device trees? =A0This change doesn= 't change >> =A0 =A0 the DTB format, so it's as much of a concern, but was wondering = if we're >> =A0 =A0 intending to keep things compatible. >> >> >> To be honest, I don't know enough to say either way. =A0I am using the c= haracter >> literals in a device tree that is used to configure a single firmware im= age for >> multiple boards. =A0That device tree is not currently passed on to the k= ernel. >> >> Your question makes me think that there are two device tree compilers th= at I >> should be paying attention to, is that the case? =A0Or was it a more gen= eral >> comment about diverging from a historic syntax for device tree source fi= les? > > Both, really. =A0There is a dtc at > git://git.kernel.org/pub/scm/linux/kernel/git/galak/dtc.git but it seems > older than the one in the kernel. The kernel one is simply a copy of the upstream dtc. You should craft your patches against: git://git.jdl.com/software/dtc.git > > Also, the dts form is defined in the ePAPR documents, and this would be > a (minor) divergence from that. dts is not set in stone, and is certainly subject to enhancements providing it doesn't break existing users. g.