From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jdl.com (jdl.com [208.123.74.7]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 44BE2DDE31 for ; Tue, 13 Feb 2007 07:16:36 +1100 (EST) To: Benjamin Herrenschmidt Subject: Re: [PATCH] ppc: Add support for AMCC Taishan 440GX eval board In-Reply-To: Your message of "Tue, 13 Feb 2007 06:55:08 +1100." <1171310108.20192.7.camel@localhost.localdomain> References: <200702121129.05004.sr@denx.de> <1171281988.20192.1.camel@localhost.localdomain> <1171310108.20192.7.camel@localhost.localdomain> Date: Mon, 12 Feb 2007 14:16:21 -0600 From: Jon Loeliger Message-Id: Cc: linuxppc-dev@ozlabs.org, Roland Dreier , Stefan Roese , linuxppc-embedded@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , So, like, the other day Benjamin Herrenschmidt mumbled: > > Note that there are still things that we might want to change. For > example, I think we really should look into adding a macro mecanism > and/or an include mecanism to dtc so that we can do things like #include > to get the base processor/SoC definition and then > "overlay" some properties on top of it (like emac phy mode etc...) What do people prefer here? Straight CPP pre-run? Direct support built into dtc to do file-inclusion, macros? Thoughts, opinions, suggestions, pre-NACKs, Cabernet Franc bribes? jdl