From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bilbo.ozlabs.org (bilbo.ozlabs.org [203.10.76.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bilbo.ozlabs.org", Issuer "CAcert Class 3 Root" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 670D3DDDFA for ; Tue, 28 Apr 2009 15:00:56 +1000 (EST) Date: Tue, 28 Apr 2009 14:26:06 +1000 From: David Gibson To: Grant Likely Subject: Re: removing get_immrbase()?? Message-ID: <20090428042606.GF11265@yookeroo.seuss> References: <49EF7B11.2000006@freescale.com> <49EF7B1C.2080105@freescale.com> <282847E1-AE1A-44EF-9D18-AF2884105FA5@kernel.crashing.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 In-Reply-To: Cc: Scott Wood , Linuxppc-dev Development , Timur Tabi List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Apr 23, 2009 at 07:53:11AM -0600, Grant Likely wrote: > On Wed, Apr 22, 2009 at 3:31 PM, Kumar Gala wrote: > > > > On Apr 22, 2009, at 3:16 PM, Timur Tabi wrote: > > > >> Scott Wood wrote: > >>> > >>> Timur Tabi wrote: > >>>>> > >>>>>      these two are related and seem like we could look for "fsl,cpm2" > >>>> > >>>> That's okay, as long as you don't break compatibility with older > >>>> device trees that don't have that property, unless you can demonstrate > >>>> that these trees would never work with the current kernel anyway. > >>> > >>> All CPM2 device trees should have fsl,cpm2 listed in the compatible of > >>> the CPM node. > >> > >> Yes, but did they always have that compatible field?  I'm concerned > >> about situations where someone updates his kernel but not his device > >> tree.  This is a scenerio that we always need to try to support. > > > > I disagree.  If you update your kernel you should update your device tree > > (thus we have .dts in the kernel tree and not somewhere else). > > Not always possible. The device tree may be 'softer' than firmware, > and easier to update, but it is still firmer than the kernel. That > is Again, this is not inherent, it's a platform design choice. It's this way for modern u-boot, but not for all platforms. > why so much effort has been spent to not break compatibility with > older device trees. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson