From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Subject: Re: Board level compatibility matching Date: Thu, 31 Jul 2008 14:52:51 -0600 Message-ID: <20080731205251.GB29834@secretlab.ca> References: <9e4733910807311349l5770a17ib2ab2535bcd2868a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <9e4733910807311349l5770a17ib2ab2535bcd2868a@mail.gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linuxppc-dev-bounces+glppd-linuxppc64-dev=m.gmane.org@ozlabs.org Errors-To: linuxppc-dev-bounces+glppd-linuxppc64-dev=m.gmane.org@ozlabs.org To: Jon Smirl Cc: devicetree-discuss@ozlabs.org, linuxppc-dev List-Id: devicetree@vger.kernel.org On Thu, Jul 31, 2008 at 04:49:49PM -0400, Jon Smirl wrote: > On 7/31/08, Grant Likely wrote: > > This topic keeps coming up, so it is probably time to address it once > > and for all. > > > > When it comes to machine level support in arch/powerpc, there seems to > > me that there are two levels or machine support. > > > ...... > > > > Thoughts? > > g. > > > As part of this, how can we going to solve the problem with triggering > the load of a board specific machine/fabric driver in a generic way? That really is a separate problem. We *could* do this with a board specific powerpc machine driver, but I don't think it is the best solution. I'm still thinking that the drivers module_init() function could check the top level board model property and decide whether or not to load based on that. g.