From: Ameet Patil <ammubhai@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Xilinx BSP for linux 2.6
Date: Thu, 06 Jul 2006 14:31:27 +0100 [thread overview]
Message-ID: <44AD10AF.10802@gmail.com> (raw)
In-Reply-To: <BAY110-F18951B1690B257545F5EEB2770@phx.gbl>
Hi Ming,
I DONOT have a ML403 with me. But does Xilinx EDK generate
xparameters_ml300.h in the BSP instead of xparameters_ml403.h for the
ML403 board?
Anyway, for linux 2.6 theres no xilinx_ocp directory in the code tree.
You need to just copy the xparameters_ml300.h file (if that is what
xilinx EDK generates) as xparameters_ml403.h in
arch/ppc/platforms/4xx/xparameters/ folder. Configure the kernel as ML403.
Like I said to you before, if you want to get started quickly and
without much headache.. then please go step-by-step. Try the things I
mention in the article PART I without applying any patches.
http://www.linux.get2knowmore.com/2006/06/30/quick-guide-linux-26-on-xilinx-virtex-ii-pro-boards-part-i/
Then if your kernel boots and shows some messages, it would be much
easier to relate to problems after applying patches.
Please DONOT hesitate to ask further clarifications!
-Ameet
Ming Liu wrote:
> Dear Ameet,
> Now I am using your patch for SystemACE in Linux 2.6. My linux version
> is 2.6.16-rc5 and I have applied the patch for SystemACE and Temac.
> When I generate BSP in EDK, how can I implement it in my linux kernel? I
> know the EDK BSP is for Linux 2.4 and the directory stucture is the same
> as 2.4(e.g. arch/ppc/platform/xilinx_ocp/......) But in 2.6, the
> directory tree is different and I cannot simply copy and replace the
> original files there. Also, there is a file called xparameters_ml403.h
> in Linux kernel but in BSP there is only xparameters_ml300.h. Shall I
> rename the xparameters_ml300 as ml403, or configure the board as ml300
> in menuconfig? In these xparameters files, the peripheral addresses are
> defined. How can I include these xparameters defination in the kernel?
> It looks complicate and you didn't mention how to replace these files in
> your article. So if you can provide some guidance, I will appreciate a
> lot because it will save me much time.
> By the way, I am still waiting for the last part of your article. Where
> are they? :)
>
> Thanks for your help.
>
> Regards
> Ming
>
> _________________________________________________________________
> 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
>
next prev parent reply other threads:[~2006-07-06 13:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 18:17 Xilinx SystemACE driver for 2.6 Ameet Patil
2006-06-29 2:45 ` sudheer
[not found] ` <44A3A77D.6000804@gmail.com>
2006-06-29 10:58 ` Ameet Patil
2006-06-30 16:12 ` Ming Liu
2006-06-30 16:55 ` Ameet Patil
2006-06-30 17:24 ` Ming Liu
2006-06-30 17:35 ` Andrei Konovalov
2006-07-01 6:21 ` David H. Lynch Jr.
2006-06-30 19:52 ` Ameet Patil
2006-06-30 20:02 ` Grant Likely
2006-06-30 20:07 ` Ming Liu
2006-07-03 9:05 ` Ameet Patil
2006-07-06 12:49 ` Xilinx BSP for linux 2.6 Ming Liu
2006-07-06 13:31 ` Ameet Patil [this message]
2006-06-29 10:56 ` Xilinx SystemACE driver for 2.6 Ameet Patil
[not found] <44AD108A.8050802@gmail.com>
2006-07-06 14:04 ` Xilinx BSP for linux 2.6 Ming Liu
2006-07-06 14:40 ` Ameet Patil
2006-07-07 11:46 ` Ming Liu
2006-07-07 12:42 ` Ameet Patil
2006-07-07 13:56 ` Ming Liu
[not found] <BAY110-F2E51F50D2158DF44D3820B2740@phx.gbl>
2006-07-07 15:55 ` Ameet Patil
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=44AD10AF.10802@gmail.com \
--to=ammubhai@gmail.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;
as well as URLs for NNTP newsgroup(s).