From: John Williams <john.williams@petalogix.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: John Linn <John.Linn@xilinx.com>,
Stephen Neuendorffer <stephenn@xilinx.com>,
microblaze-uclinux@itee.uq.edu.au,
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: Tue, 21 Apr 2009 12:24:36 +1000 [thread overview]
Message-ID: <1d3f23370904201924n4ab592cdq49a4a4c8ec78d1df@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40904200748t4fc0b623naf7fd8c34a743733@mail.gmail.com>
On Tue, Apr 21, 2009 at 12:48 AM, Grant Likely
<grant.likely@secretlab.ca> wrote:
> On Mon, Apr 20, 2009 at 8:36 AM, John Linn <John.Linn@xilinx.com> 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.org; John Linn
>>> Subject: RE: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable 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 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?
>
> 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
--
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
next prev parent reply other threads:[~2009-04-21 2:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 9:56 Microblaze fixes for revision monstr
2009-04-16 9:56 ` [PATCH 01/11] microblaze: Remove unneded per cpu SYSCALL_SAVE variable monstr
2009-04-16 9:56 ` [PATCH 02/11] microblaze: Remove while(1) loop from show_regs function monstr
2009-04-16 9:56 ` [PATCH 03/11] microblaze: Remove uncache shadow condition monstr
2009-04-16 9:56 ` [PATCH 04/11] microblaze: Rename kernel_mode to pt_mode in pt_regs monstr
2009-04-16 9:56 ` [PATCH 05/11] microblaze: Move task_pt_regs up monstr
2009-04-16 9:56 ` [PATCH 06/11] microblaze: Remove sparse error in traps.c monstr
2009-04-16 9:56 ` [PATCH 07/11] microblaze: Add missing declaration for die and _exception func monstr
2009-04-16 9:56 ` [PATCH 08/11] microblaze: Add missing preadv and pwritev syscalls monstr
2009-04-16 9:56 ` [PATCH 09/11] microblaze: Move start_thread to process.c monstr
2009-04-16 9:56 ` [PATCH 10/11] microblaze: Remove redundant variable monstr
2009-04-16 9:56 ` [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze monstr
2009-04-17 5:01 ` [microblaze-uclinux] " John Williams
2009-04-17 6:52 ` Grant Likely
2009-04-17 17:21 ` Stephen Neuendorffer
2009-04-17 17:06 ` Stephen Neuendorffer
2009-04-18 5:49 ` Grant Likely
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 7:41 ` who know's what is "TestFloat cases" and how to test this feature onthe " Liu Yu-B13201
[not found] ` <495563870904181941o5a66126dgb59d8cad2b7a66f2@mail.gmail.com>
2009-04-19 23:03 ` [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze John Williams
[not found] ` <977C41F842E66D4CB2E41332313B6150069D3D27@XSJ-EXCHVS1.xlnx.xilinx.com>
2009-04-20 14:36 ` John Linn
2009-04-20 14:48 ` Grant Likely
2009-04-21 2:24 ` John Williams [this message]
2009-04-17 4:57 ` [microblaze-uclinux] [PATCH 10/11] microblaze: Remove redundant variable John Williams
2009-04-17 4:57 ` [microblaze-uclinux] [PATCH 09/11] microblaze: Move start_thread to process.c John Williams
2009-04-17 4:56 ` [microblaze-uclinux] [PATCH 08/11] microblaze: Add missing preadv and pwritev syscalls John Williams
2009-04-17 4:55 ` [microblaze-uclinux] [PATCH 07/11] microblaze: Add missing declaration for die and _exception func John Williams
2009-04-17 4:55 ` [microblaze-uclinux] [PATCH 06/11] microblaze: Remove sparse error in traps.c John Williams
2009-04-17 2:25 ` [microblaze-uclinux] [PATCH 02/11] microblaze: Remove while(1) loop from show_regs function John Williams
2009-04-20 20:31 ` Microblaze fixes for revision Andrew Morton
2009-04-21 6:30 ` Michal Simek
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=1d3f23370904201924n4ab592cdq49a4a4c8ec78d1df@mail.gmail.com \
--to=john.williams@petalogix.com \
--cc=John.Linn@xilinx.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=stephenn@xilinx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).