From: "Phil Hochstetler" <Phil.Hochstetler@serveron.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: Xilinx EDK 9.2i and current Linux src tree(s)
Date: Mon, 10 Mar 2008 11:34:09 -0700 [thread overview]
Message-ID: <ADA5878BA63680469C75C14CEEE2FE28012F4DBA@mail.serveron.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]
Thanks to responses from this group, I'm using Ubuntu and ELDK 4.1, I
have a working environment to build a linux kernel for a Xilinx ML403
board. I pulled the kernel source at
git://git.xilinx.com/linux-2.6-xlnx.git
<http://git.xilinx.com/cgi-bin/gitweb.cgi?p=linux-2.6-xlnx.git;a=summary
> and while it will compile using "make ARCH=ppc ml403_defconfig" and
"make ARCH=ppc CROSS_COMPILE=ppc_4xx- bzImage", when I use the EDK 9.2i
to create a bitstream for the ML403 board, the BSP based header files
(xparam*) files are out of sync with the kernel source. The files in
the linux-2.6-xlnx tree appear to have been build with EDK 7.1 and I am
using the current EDK release 9.2i. The major diff seems to be that the
new EDK release moves all the periphials off the OPB bus and uses the
XPS bus instead. Any ideas on how best to resolve this? Is there a
linux tree out there that is synced with the current EDK release? Is
it sufficient to had edit in the hardware address in the existing OPB
based file and ignore the differences between OPB and XPS? Is the
difference in name only? Should I just try to pick up the entire linux
tree from the EDK release and drop it on the linux kernel? Has anyone
else been down this path already? Thanks for any words of wisdom.
--phil
[-- Attachment #2: Type: text/html, Size: 3053 bytes --]
next reply other threads:[~2008-03-10 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 18:34 Phil Hochstetler [this message]
2008-03-10 18:57 ` Xilinx EDK 9.2i and current Linux src tree(s) Stephen Neuendorffer
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=ADA5878BA63680469C75C14CEEE2FE28012F4DBA@mail.serveron.com \
--to=phil.hochstetler@serveron.com \
--cc=linuxppc-embedded@ozlabs.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