From: Stephen Neuendorffer <stephen.neuendorffer@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
John Linn <john.linn@xilinx.com>,
linux-kernel@vger.kernel.org, microblaze-uclinux@itee.uq.edu.au
Subject: Re: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze
Date: Sat, 18 Apr 2009 19:41:59 -0700 [thread overview]
Message-ID: <495563870904181941o5a66126dgb59d8cad2b7a66f2@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40904172249m5e261492w48c8d9d8446600e0@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5165 bytes --]
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...
Steve
>
> g.
>
> >
> > Steve
> >
> >> -----Original Message-----
> >> From: owner-microblaze-uclinux@itee.uq.edu.au
> > [mailto:owner-microblaze-uclinux@itee.uq.edu.au] On
> >> Behalf Of monstr@monstr.eu
> >> Sent: Thursday, April 16, 2009 2:57 AM
> >> To: linux-kernel@vger.kernel.org
> >> Cc: microblaze-uclinux@itee.uq.edu.au; Michal Simek
> >> Subject: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig:
> > Enable drivers for Microblaze
> >>
> >> From: Michal Simek <monstr@monstr.eu>
> >>
> >> Signed-off-by: Michal Simek <monstr@monstr.eu>
> >> ---
> >> drivers/block/Kconfig | 2 +-
> >> drivers/char/Kconfig | 2 +-
> >> drivers/gpio/Kconfig | 2 +-
> >> drivers/usb/Kconfig | 1 +
> >> 4 files changed, 4 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
> >> index ddea8e4..9f1665f 100644
> >> --- a/drivers/block/Kconfig
> >> +++ b/drivers/block/Kconfig
> >> @@ -438,7 +438,7 @@ source "drivers/s390/block/Kconfig"
> >>
> >> config XILINX_SYSACE
> >> tristate "Xilinx SystemACE support"
> >> - depends on 4xx
> >> + depends on 4xx || MICROBLAZE
> >> help
> >> Include support for the Xilinx SystemACE CompactFlash
> > interface
> >>
> >> diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
> >> index 735bbe2..bb1a071 100644
> >> --- a/drivers/char/Kconfig
> >> +++ b/drivers/char/Kconfig
> >> @@ -893,7 +893,7 @@ config DTLK
> >>
> >> config XILINX_HWICAP
> >> tristate "Xilinx HWICAP Support"
> >> - depends on XILINX_VIRTEX
> >> + depends on XILINX_VIRTEX || MICROBLAZE
> >> help
> >> This option enables support for Xilinx Internal Configuration
> >> Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex
> >> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> >> index edb0253..11f3739 100644
> >> --- a/drivers/gpio/Kconfig
> >> +++ b/drivers/gpio/Kconfig
> >> @@ -69,7 +69,7 @@ comment "Memory mapped GPIO expanders:"
> >>
> >> config GPIO_XILINX
> >> bool "Xilinx GPIO support"
> >> - depends on PPC_OF
> >> + depends on PPC_OF || MICROBLAZE
> >> help
> >> Say yes here to support the Xilinx FPGA GPIO device
> >>
> >> diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
> >> index c6c816b..5eee3f8 100644
> >> --- a/drivers/usb/Kconfig
> >> +++ b/drivers/usb/Kconfig
> >> @@ -22,6 +22,7 @@ config USB_ARCH_HAS_HCD
> >> default y if PCMCIA && !M32R # sl811_cs
> >> default y if ARM # SL-811
> >> default y if SUPERH # r8a66597-hcd
> >> + default y if MICROBLAZE
> >> default PCI
> >>
> >> # many non-PCI SOC chips embed OHCI
> >> --
> >> 1.5.5.1
> >>
> >> ___________________________
> >> microblaze-uclinux mailing list
> >> microblaze-uclinux@itee.uq.edu.au
> >> Project Home Page :
> > http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux<http://www.itee.uq.edu.au/%7Ejwilliams/mblaze-uclinux>
> >> Mailing List Archive :
> > http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/<http://www.itee.uq.edu.au/%7Elistarch/microblaze-uclinux/>
> >>
> >
> >
> > This email and any attachments are intended for the sole use of the named
> recipient(s) and contain(s) confidential information that may be
> proprietary, privileged or copyrighted under applicable law. If you are not
> the intended recipient, do not read, copy, or forward this email message or
> any attachments. Delete this email message and any attachments immediately.
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
>
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
[-- Attachment #2: Type: text/html, Size: 7341 bytes --]
next prev parent reply other threads:[~2009-04-19 2:42 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 [this message]
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
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=495563870904181941o5a66126dgb59d8cad2b7a66f2@mail.gmail.com \
--to=stephen.neuendorffer@gmail.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 \
/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).