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 9512FDDEC2 for ; Fri, 20 Jul 2007 05:04:33 +1000 (EST) In-Reply-To: <469FB3C4.8070909@freescale.com> References: <20070718013604.GU15238@ld0162-tx32.am.freescale.net> <20070719205745.57f9d5a0@localhost.localdomain> <469FB3C4.8070909@freescale.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: From: Segher Boessenkool Subject: Re: [PATCH 49/61] 8xx: Update device trees. Date: Thu, 19 Jul 2007 21:04:17 +0200 To: Scott Wood Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >> Since you are using generic names, the only use for the "name" >> of a node is for a human reader to understand your tree. Maybe >> everyone using this specific SoC knows what a BCSR is; or maybe >> there is a more friendly name you could use. > > It's the standard term used in Freescale board documentation. I > could change it to board-control, though. That sounds nice and generic, I like it. Segher