From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by ozlabs.org (Postfix) with ESMTP id 062A2DE046 for ; Tue, 21 Apr 2009 12:24:38 +1000 (EST) Received: by wf-out-1314.google.com with SMTP id 24so2005574wfg.15 for ; Mon, 20 Apr 2009 19:24:36 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <764365e7af2e476e43cd674738e51f13b306979b.1239874968.git.monstr@monstr.eu> <74c0088dfda1816c21914c0a8da0c42908526c5e.1239874968.git.monstr@monstr.eu> <20090417170707.B6C95C4004F@mail150-wa4.bigfish.com> <495563870904181941o5a66126dgb59d8cad2b7a66f2@mail.gmail.com> <1d3f23370904191603s37a6a34clccc397707394650b@mail.gmail.com> <977C41F842E66D4CB2E41332313B6150069D3D27@XSJ-EXCHVS1.xlnx.xilinx.com> <20090420143606.4309C74804E@mail192-wa4.bigfish.com> Date: Tue, 21 Apr 2009 12:24:36 +1000 Message-ID: <1d3f23370904201924n4ab592cdq49a4a4c8ec78d1df@mail.gmail.com> Subject: Re: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze From: John Williams To: Grant Likely Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-dev , Stephen Neuendorffer , John Linn , linux-kernel@vger.kernel.org, microblaze-uclinux@itee.uq.edu.au List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Apr 21, 2009 at 12:48 AM, Grant Likely wrote: > On Mon, Apr 20, 2009 at 8:36 AM, John Linn wrote: >>> -----Original Message----- >>> From: Stephen Neuendorffer >>> Sent: Sunday, April 19, 2009 11:52 PM >>> To: John Williams; microblaze-uclinux@itee.uq.edu.au >>> Cc: grant.likely@secretlab.ca; linuxppc-dev; linux-kernel@vger.kernel.o= rg; John Linn >>> Subject: RE: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: En= able drivers for Microblaze >>> >>> >>> My thinking is that these drivers are likely to be used as a group, >>> hence it would be nice to make it easy to get them all visible/enabled = somehow. >>> >>> Steve >> >> >> It seems like John's suggestion of no arch filters would satisfy that al= so. Since FPGAs are used in so many different applications this would seem = to open the drivers up to everyone regardless of what processor they're usi= ng. It's certainly less complex so I like it in that way. >> >> But maybe I'm missing something here and there's a downside? > > No, I don't think there is. > > I think CONFIG_OF is the right thing to do. Some (most?) of the Xilinx drivers currently have this construct: #ifdef CONFIG_OF // probe using OF #else // probe using platform_device #endif so unless this is going to change some time soon, maybe even CONFIG_OF is too restrictive? John --=20 John Williams, PhD, B.Eng, B.IT PetaLogix - Linux Solutions for a Reconfigurable World w: www.petalogix.com p: +61-7-30090663 f: +61-7-30090663