From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from WA4EHSOBE004.bigfish.com (wa4ehsobe004.messaging.microsoft.com [216.32.181.14]) by ozlabs.org (Postfix) with ESMTP id 7512BDDFA4 for ; Tue, 21 Apr 2009 00:36:14 +1000 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze Date: Mon, 20 Apr 2009 08:36:05 -0600 In-Reply-To: <977C41F842E66D4CB2E41332313B6150069D3D27@XSJ-EXCHVS1.xlnx.xilinx.com> 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> From: John Linn To: "Stephen Neuendorffer" , "John Williams" , Message-ID: <20090420143606.4309C74804E@mail192-wa4.bigfish.com> Cc: linuxppc-dev , linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > -----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.org= ; John Linn > Subject: RE: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enab= le 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 so= mehow. > > Steve It seems like John's suggestion of no arch filters would satisfy that also.= 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 using.= It's certainly less complex so I like it in that way. But maybe I'm missing something here and there's a downside? -- John > = > -----Original Message----- > From: John Williams [mailto:john.williams@petalogix.com] > Sent: Sun 4/19/2009 4:03 PM > To: microblaze-uclinux@itee.uq.edu.au > Cc: grant.likely@secretlab.ca; Stephen Neuendorffer; linuxppc-dev; linux-= kernel@vger.kernel.org; John > Linn > Subject: Re: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enab= le drivers for Microblaze > = > On Sun, Apr 19, 2009 at 12:41 PM, Stephen Neuendorffer > wrote: > > > > > > On Fri, Apr 17, 2009 at 10:49 PM, Grant Likely > > wrote: > >> > >> On Fri, Apr 17, 2009 at 11:06 AM, Stephen Neuendorffer > >> wrote: > >> > > >> > Can we have XILINX_DRIVERS, please? =A0That way this can also be ena= bled > >> > on any architecture that has FPGA peripherals. > >> > >> I've thought about this more, and I'd really rather not. =A0The list o= f > >> affected drivers is short and is not a large maintenance burden. =A0I > >> don't think a list of 2 or 3 architecture selects for each driver is > >> unreasonable. =A0A "XILINX_DRIVERS" config item doesn't really help mu= ch > >> anyway. =A0At any given time one of these drivers may be needed on > >> another platform. =A0ie. the SystemACE device is present on at least o= ne > >> non-virtex, non-spartan platform. > > > > Which is exactly why having it architecture dependent isn't right...=A0= All of > > these drivers > > could be needed and used on any OF-based platform.=A0 If you have a pla= tform > > (for instance, a processor connected to an FPGA which has these periphe= rals > > in the FPGA) then you should be able to enable these drivers.=A0 Just m= y 2 > > cents... > = > What about the radical approach of having NO architecture > filters/selectors? Even if some random i386 user selects one of these > drivers, so what? It will still compile cleanly (if it doesn't we > have to fix it), but there'll be no platform_device_register() call in > their machine startup to actually cause driver / device binding. > = > No harm, no foul. Problem goes away. > = > Then, as Grant points out, the rare cases where non-Xilinx platforms > do use this stuff, they'll presumably know what they're doing and it's > their responsibility to register the appropriate platform_device > structures and make the magic happen. > = > John > -- > 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 > = This email and any attachments are intended for the sole use of the named r= ecipient(s) and contain(s) confidential information that may be proprietary= , privileged or copyrighted under applicable law. If you are not the intend= ed recipient, do not read, copy, or forward this email message or any attac= hments. Delete this email message and any attachments immediately.