From: John Linn <John.Linn@xilinx•com>
To: "Stephen Neuendorffer" <stephenn@xilinx•com>,
"John Williams" <john.williams@petalogix•com>,
<microblaze-uclinux@itee•uq.edu.au>
Cc: linuxppc-dev <linuxppc-dev@ozlabs•org>, linux-kernel@vger•kernel.org
Subject: RE: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze
Date: Mon, 20 Apr 2009 08:36:05 -0600 [thread overview]
Message-ID: <20090420143606.4309C74804E@mail192-wa4.bigfish.com> (raw)
In-Reply-To: <977C41F842E66D4CB2E41332313B6150069D3D27@XSJ-EXCHVS1.xlnx.xilinx.com>
> -----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
> <stephen.neuendorffer@gmail•com> wrote:
> >
> >
> > On Fri, Apr 17, 2009 at 10:49 PM, Grant Likely <grant.likely@secretlab.=
ca>
> > wrote:
> >>
> >> On Fri, Apr 17, 2009 at 11:06 AM, Stephen Neuendorffer
> >> <stephen.neuendorffer@xilinx•com> 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.
next prev parent reply other threads:[~2009-04-20 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <764365e7af2e476e43cd674738e51f13b306979b.1239874968.git.monstr@monstr.eu>
[not found] ` <74c0088dfda1816c21914c0a8da0c42908526c5e.1239874968.git.monstr@monstr.eu>
[not found] ` <20090417170707.B6C95C4004F@mail150-wa4.bigfish.com>
2009-04-18 5:49 ` [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze Grant Likely
2009-04-19 2:41 ` Stephen Neuendorffer
2009-04-19 23:03 ` John Williams
2009-04-20 5:51 ` Stephen Neuendorffer
[not found] ` <977C41F842E66D4CB2E41332313B6150069D3D27@XSJ-EXCHVS1.xlnx.xilinx.com>
2009-04-20 14:36 ` John Linn [this message]
2009-04-20 14:48 ` Grant Likely
2009-04-21 2:24 ` John Williams
2009-04-24 10:49 ` Arnd Bergmann
2009-04-19 9:25 ` who know's what is "TestFloat cases" and how to test this feature on the Freescale MPC8536DS board derekzheng
2009-04-19 16:40 ` Kumar Gala
2009-04-20 5:29 ` zhengxiang9
2009-04-20 7:41 ` who know's what is "TestFloat cases" and how to test this feature onthe " Liu Yu-B13201
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090420143606.4309C74804E@mail192-wa4.bigfish.com \
--to=john.linn@xilinx$(echo .)com \
--cc=john.williams@petalogix$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=microblaze-uclinux@itee$(echo .)uq.edu.au \
--cc=stephenn@xilinx$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox