From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id AC30867B4F for ; Tue, 2 May 2006 09:34:22 +1000 (EST) Subject: Re: DTC/dts modifications From: Benjamin Herrenschmidt To: Kumar Gala In-Reply-To: <55FD11DB-54AF-4284-9E9A-C313F4232105@kernel.crashing.org> References: <5CA113BC-1614-4551-87E5-6926E14C2225@kernel.crashing.org> <1146512012.24239.28.camel@cashmere.sps.mot.com> <695BB790-1E64-4B53-91DD-7DD88305F201@kernel.crashing.org> <1146512732.24239.34.camel@cashmere.sps.mot.com> <55FD11DB-54AF-4284-9E9A-C313F4232105@kernel.crashing.org> Content-Type: text/plain Date: Tue, 02 May 2006 09:34:08 +1000 Message-Id: <1146526448.30710.70.camel@localhost.localdomain> Mime-Version: 1.0 Cc: "linuxppc-dev@ozlabs.org list" , Jon Loeliger List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > By what book? It would seem to me that BNF for dtc is completely > under our control and if we want to change it we can. I understand > that there is some correspondence to Open Firmware, but it seems that > if its people are ok with the dts format changing that's a lot easier > than implementing tons of support in dtc for features that cpp gives us. What about just providing a way to escape them ? Something like \# would do the trick Ben