From: John Williams <john.williams@petalogix.com>
To: microblaze-uclinux@itee.uq.edu.au
Cc: linux-kernel@vger.kernel.org, Michal Simek <monstr@monstr.eu>
Subject: Re: [microblaze-uclinux] [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze
Date: Fri, 17 Apr 2009 15:01:21 +1000 [thread overview]
Message-ID: <1d3f23370904162201s21fc7d90q8bc4aacafa5a7ada@mail.gmail.com> (raw)
In-Reply-To: <74c0088dfda1816c21914c0a8da0c42908526c5e.1239874968.git.monstr@monstr.eu>
On Thu, Apr 16, 2009 at 7:56 PM, <monstr@monstr.eu> wrote:
> From: Michal Simek <monstr@monstr.eu>
>
> Signed-off-by: Michal Simek <monstr@monstr.eu>
ACK from a MicroBlaze perspective, but some other comments below:
A note more for the Xilinx PPC folks (ie Grant Likely):
Shouldn't some of these Kconfig depends for PPC be unified? We have:
> config XILINX_SYSACE
> tristate "Xilinx SystemACE support"
> - depends on 4xx
> + depends on 4xx || MICROBLAZE
> config XILINX_HWICAP
> tristate "Xilinx HWICAP Support"
> - depends on XILINX_VIRTEX
> + depends on XILINX_VIRTEX || MICROBLAZE
> 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
Are these all really different options? PPC_OF? XILINX_VIRTEX? 4xx?
John
next prev parent reply other threads:[~2009-04-17 5:01 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 ` John Williams [this message]
2009-04-17 6:52 ` [microblaze-uclinux] " 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
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=1d3f23370904162201s21fc7d90q8bc4aacafa5a7ada@mail.gmail.com \
--to=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
/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).