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 439CCDDDE6 for ; Fri, 1 Aug 2008 13:06:21 +1000 (EST) Received: by yw-out-2324.google.com with SMTP id 5so434010ywh.39 for ; Thu, 31 Jul 2008 20:06:20 -0700 (PDT) Message-ID: <9e4733910807312006l8e83d27qe1b5ca5f50b89e39@mail.gmail.com> Date: Thu, 31 Jul 2008 23:06:20 -0400 From: "Jon Smirl" To: "David Gibson" , "Grant Likely" , devicetree-discuss@ozlabs.org, "Benjamin Herrenschmidt" , linuxppc-dev Subject: Re: Board level compatibility matching In-Reply-To: <20080801024729.GA5008@yookeroo.seuss> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <9e4733910807311349l5770a17ib2ab2535bcd2868a@mail.gmail.com> <20080731205251.GB29834@secretlab.ca> <9e4733910807311358k54b5c088l1023d354fd0ad28e@mail.gmail.com> <20080801024729.GA5008@yookeroo.seuss> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 7/31/08, David Gibson wrote: > On Thu, Jul 31, 2008 at 04:58:34PM -0400, Jon Smirl wrote: > > 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. > > > This can still be done via the board platform code. The platform code > creates a platform device which the driver can later bind to. That is what I'm doing now. But it requires every board to add a file to arch/powerpc/platforms. Can we have some common code to make the fabric device? Can it be an OF device instead of a platform one? An OF device could be compatible with boardname-fabric, generic-fabric. That allows a stub fabric driver to always bind. > > > > -- > David Gibson | I'll have my music baroque, and my code > david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ > | _way_ _around_! > http://www.ozlabs.org/~dgibson > -- Jon Smirl jonsmirl@gmail.com