From: "Stephen Williams" <612dlag102@sneakemail.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: System ACE MPU interface to CF card
Date: Tue, 13 Apr 2004 10:54:56 -0700 [thread overview]
Message-ID: <25757-52278@sneakemail.com> (raw)
In-Reply-To: <407ADCFE.8080302@buckeye.ece.drexel.edu>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Sharad Gupta sharad-at-buckeye.ece.drexel.edu |PPC Linux Embedded| wrote:
> Can you send me your board patch so that I can configure and build ACE
> driver for my board ? I want some help in knowing how and where to
> customize the driver for one's board.
The attached patch demonstrates how I enabled the SYSACE driver
for my (JSE) board. I'm not so sure I'm happy with it, because
each board will have to do something similar. I'm thinking that
the CONFIG_XILINX_SYSACE define should lose its dependence on
CONFIG_XILINX_OCP, but I'm not clear on the best way to account
for this in the xilinx_ocp/Makefile.
NOTE: This patch is meant to demonstrate my thinking on this
matter. It's not complete.
--
Steve Williams "The woods are lovely, dark and deep.
steve at XXXXXXXXXX But I have promises to keep,
http://www.XXXXXXXXXX and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
[-- Attachment #2: foo.txt --]
[-- Type: text/plain, Size: 1919 bytes --]
Index: arch/ppc/platforms/xilinx_ocp/Makefile
===================================================================
RCS file: /cvsroot/linuxppc_2_4_devel/arch/ppc/platforms/xilinx_ocp/Makefile,v
retrieving revision 1.1
diff -u -r1.1 Makefile
--- arch/ppc/platforms/xilinx_ocp/Makefile 1 Dec 2002 22:42:56 -0000 1.1
+++ arch/ppc/platforms/xilinx_ocp/Makefile 13 Apr 2004 17:48:37 -0000
@@ -13,6 +13,7 @@
xipif_v1_23_b.o xpacket_fifo_v1_00_b.o xversion.o
obj-$(CONFIG_XILINX_OCP) := xilinx_ocp.o
+obj-$(CONFIG_JSE) := xilinx_ocp.o
xilinx_ocp.o: $(xilinx_ocp-objs)
$(LD) -r -o $@ $(xilinx_ocp-objs)
Index: arch/ppc/platforms/xilinx_ocp/xparameters.h
===================================================================
RCS file: /cvsroot/linuxppc_2_4_devel/arch/ppc/platforms/xilinx_ocp/xparameters.h,v
retrieving revision 1.2
diff -u -r1.2 xparameters.h
--- arch/ppc/platforms/xilinx_ocp/xparameters.h 30 Oct 2003 00:32:20 -0000 1.2
+++ arch/ppc/platforms/xilinx_ocp/xparameters.h 13 Apr 2004 17:48:37 -0000
@@ -16,3 +16,7 @@
#if defined(CONFIG_XILINX_ML300)
#include "xparameters_ml300.h"
#endif
+
+#if defined(CONFIG_JSE)
+#include "xparameters_jse.h"
+#endif
Index: drivers/block/Config.in
===================================================================
RCS file: /cvsroot/linuxppc_2_4_devel/drivers/block/Config.in,v
retrieving revision 1.5
diff -u -r1.5 Config.in
--- drivers/block/Config.in 30 Oct 2003 00:32:48 -0000 1.5
+++ drivers/block/Config.in 13 Apr 2004 17:48:37 -0000
@@ -40,7 +40,7 @@
dep_tristate 'Mylex DAC960/DAC1100 PCI RAID Controller support' CONFIG_BLK_DEV_DAC960 $CONFIG_PCI
dep_tristate 'Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)' CONFIG_BLK_DEV_UMEM $CONFIG_PCI $CONFIG_EXPERIMENTAL
-if [ "$CONFIG_XILINX_OCP" = "y" ]; then
+if [ "$CONFIG_XILINX_OCP" = "y" -o "$CONFIG_JSE" = "y" ]; then
tristate 'Xilinx on-chip System ACE' CONFIG_XILINX_SYSACE
fi
next prev parent reply other threads:[~2004-04-13 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 21:21 System ACE MPU interface to CF card Sharad Gupta
2004-04-07 23:09 ` Stephen Williams
2004-04-08 0:04 ` Tom Rini
[not found] ` <407ADCFE.8080302@buckeye.ece.drexel.edu>
2004-04-13 17:54 ` Stephen Williams [this message]
2004-04-15 19:05 ` Sharad Gupta
2004-04-15 20:14 ` Stephen Williams
2004-04-18 0:28 ` Jon Masters
2004-04-20 1:02 ` Jon Masters
2004-04-18 21:06 ` Jeff Angielski
2004-04-19 18:06 ` Sharad Gupta
2004-04-19 18:38 ` Jeff Angielski
2004-04-19 23:07 ` more SystemACE problems Sharad Gupta
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=25757-52278@sneakemail.com \
--to=612dlag102@sneakemail.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).