From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: RE: [PATCH 12/60] microblaze_v4: Generic dts file for platforms Date: Wed, 02 Jul 2008 10:25:30 +1000 Message-ID: <1214958330.20711.205.camel@pasglop> References: <1214483429-32360-1-git-send-email-monstr@seznam.cz> <1214483429-32360-6-git-send-email-monstr@seznam.cz> <1214483429-32360-7-git-send-email-monstr@seznam.cz> <1214483429-32360-8-git-send-email-monstr@seznam.cz> <1214483429-32360-9-git-send-email-monstr@seznam.cz> <1214483429-32360-10-git-send-email-monstr@seznam.cz> <1214483429-32360-11-git-send-email-monstr@seznam.cz> <1214483429-32360-12-git-send-email-monstr@seznam.cz> <1214483429-32360-13-git-send-email-monstr@seznam.cz> <1d3f23370806291702g4344a2f9lb62f85cbb475fca4@mail.gmail.com> <20080630033943.332471860046@mail171-va3.bigfish.com> <1214893302.20711.102.camel@pasglop> <20080701155845.9DDE299004D@mail180-dub.bigfish.com> Reply-To: benh@kernel.crashing.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from gate.crashing.org ([63.228.1.57]:48081 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751537AbYGBA2t (ORCPT ); Tue, 1 Jul 2008 20:28:49 -0400 In-Reply-To: <20080701155845.9DDE299004D@mail180-dub.bigfish.com> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Stephen Neuendorffer Cc: John Williams , grant.likely@secretlab.ca, linux-arch@vger.kernel.org, Michal Simek , vapier.adi@gmail.com, arnd@arndb.de, matthew@wil.cx, microblaze-uclinux@itee.uq.edu.au, linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, will.newton@gmail.com, hpa@zytor.com, John Linn , monstr@seznam.cz, drepper@redhat.com, alan@lxorguk.ukuu.org.uk On Tue, 2008-07-01 at 08:58 -0700, Stephen Neuendorffer wrote: > Doing this at the binary level would be nice, but I see enough problems > just doing it at the source level and at least for my purposes, doing it > on a dtb would be overkill, I think. > > The main difficulty remains how to deal with cross references between > nodes in a reasonable way where the references cross from one fragment > to another. I would have those done in the toplevel .dts You can always override the property with the reference.... Ie. you #include your CPU or your SOC for example, and then override some property to point to something else using the override mechanism I mentioned. Ben.