From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by ozlabs.org (Postfix) with ESMTP id 67DCDDEBDC for ; Fri, 1 Aug 2008 06:58:36 +1000 (EST) Received: by yw-out-2324.google.com with SMTP id 5so378522ywh.39 for ; Thu, 31 Jul 2008 13:58:34 -0700 (PDT) Message-ID: <9e4733910807311358k54b5c088l1023d354fd0ad28e@mail.gmail.com> Date: Thu, 31 Jul 2008 16:58:34 -0400 From: "Jon Smirl" To: "Grant Likely" Subject: Re: Board level compatibility matching In-Reply-To: <20080731205251.GB29834@secretlab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <9e4733910807311349l5770a17ib2ab2535bcd2868a@mail.gmail.com> <20080731205251.GB29834@secretlab.ca> Cc: devicetree-discuss@ozlabs.org, linuxppc-dev List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 7/31/08, Grant Likely wrote: > 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. You're assuming the driver is compiled in. If the drivers are on initrd selection has to happen via the normal device/driver matching process. Search for a device in the alias table of the drive file. -- Jon Smirl jonsmirl@gmail.com