linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Williams <john.williams@petalogix.com>
To: microblaze-uclinux@itee.uq.edu.au
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>,
	linux-kernel@vger.kernel.org, John Linn <john.linn@xilinx.com>
Subject: Re: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable  drivers for Microblaze
Date: Mon, 20 Apr 2009 09:03:40 +1000	[thread overview]
Message-ID: <1d3f23370904191603s37a6a34clccc397707394650b@mail.gmail.com> (raw)
In-Reply-To: <495563870904181941o5a66126dgb59d8cad2b7a66f2@mail.gmail.com>

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?  That way this can also be enabled
>> > on any architecture that has FPGA peripherals.
>>
>> I've thought about this more, and I'd really rather not.  The list of
>> affected drivers is short and is not a large maintenance burden.  I
>> don't think a list of 2 or 3 architecture selects for each driver is
>> unreasonable.  A "XILINX_DRIVERS" config item doesn't really help much
>> anyway.  At any given time one of these drivers may be needed on
>> another platform.  ie. the SystemACE device is present on at least one
>> non-virtex, non-spartan platform.
>
> Which is exactly why having it architecture dependent isn't right...  All of
> these drivers
> could be needed and used on any OF-based platform.  If you have a platform
> (for instance, a processor connected to an FPGA which has these peripherals
> in the FPGA) then you should be able to enable these drivers.  Just my 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

  parent reply	other threads:[~2009-04-19 23:03 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                             ` John Williams [this message]
     [not found]                               ` <977C41F842E66D4CB2E41332313B6150069D3D27@XSJ-EXCHVS1.xlnx.xilinx.com>
2009-04-20 14:36                                 ` [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze John Linn
2009-04-20 14:48                                   ` Grant Likely
2009-04-21  2:24                                     ` John Williams
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=1d3f23370904191603s37a6a34clccc397707394650b@mail.gmail.com \
    --to=john.williams@petalogix.com \
    --cc=grant.likely@secretlab.ca \
    --cc=john.linn@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    --cc=stephen.neuendorffer@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).