From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id AA5C1DE0DE for ; Sat, 4 Oct 2008 06:28:10 +1000 (EST) Message-ID: <48E67FCE.8010201@freescale.com> Date: Fri, 03 Oct 2008 15:25:50 -0500 From: Scott Wood MIME-Version: 1.0 To: Mike Ditto Subject: Re: unit name for /soc in device tree References: <48E67CDD.8080002@consentry.com> In-Reply-To: <48E67CDD.8080002@consentry.com> Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Mike Ditto wrote: > I'm starting a scratch port of Linux 2.6 to an MPC8272 board that currently > runs 2.4 (MontaVista). > > Documentation/powerpc/booting-without-of.txt says: > The name of an soc > node should start with "soc", and the remainder of the name should > represent the part number for the soc. For example, the MPC8540's > soc node would be called "soc8540". Gah, what's that still doing in there? Ignore it. It's a bad idea, for exactly this reason. -Scott