From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <17700.19414.724178.711359@cargo.ozlabs.ibm.com> Date: Thu, 5 Oct 2006 10:03:34 +1000 From: Paul Mackerras To: Benjamin Herrenschmidt Subject: Re: [PATCH 10/11] Add MPC8360EMDS board support In-Reply-To: <1160005019.5887.30.camel@localhost.localdomain> References: <20060927155626.4d5ca19c@vitb.ru.mvista.com> <4879B0C6C249214CBE7AB04453F84E4D19D865@zch01exm20.fsl.freescale.net> <20060927165556.04c8d5d7@vitb.ru.mvista.com> <20060927112201.293fef44@localhost.localdomain> <1159942128.13323.21.camel@localhost.localdomain> <7BD0D5CE-7BA3-43DC-B972-B75672F6A31E@embeddedalley.com> <1160005019.5887.30.camel@localhost.localdomain> Cc: Olof Johansson , linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Benjamin Herrenschmidt writes: > > It's the 'or not' part that I am worried about. Things like > > you mention above make sense. I'm starting to worry about > > some of this other stuff, and the bscr example is what > > woke me up :-) I think that's an example of things that > > should be considered not necessary. > > I haven't looked at this specific example. I'll try to have a look > later. I jumped into the discussion pointed by somebody else :) That one was interesting - the bcsr was being referenced from an ethernet driver that looked to me like it would be useful on any board based on an 836x chip (I think). Yet it was claimed that the bcsr was so specific and unique to each board that there was no point putting it in the device tree - which implies that we would have to have a separate lump of code in the tree to drive it for every single board. :P I asked why the ethernet driver was accessing it directly if that was the case, but didn't get an answer (well, only an indirect answer in that the bcsr access code got removed from the ethernet driver). Paul.