From: Mirek23 <miroslaw.dach@psi.ch>
To: linuxppc-embedded@ozlabs.org
Subject: Xilinx Linux 2.6 for XPS LL_TEMAC and LL_FIFO problem
Date: Thu, 24 Jul 2008 02:19:46 -0700 (PDT) [thread overview]
Message-ID: <18628194.post@talk.nabble.com> (raw)
In-Reply-To: <20080316214832.3F77A538046@mail141-sin.bigfish.com>
Dear All,
I have done a design using EDK 8.2 using Hard_Temac IP component. In the EDK
9.2 there is a new idea to use ll_temac in conjunction with ll_fifo or
ll_dma. So far I was using happily the linux kernel by Grant Likey.
Unfortunately it does not deal with ll_temac. I have download the kernel
from git.xilinx.com.
I have tried to build the kernel 2.6.26 (by xilinx) but it seems to be that
it is not well prepared for ll_fifo.
I have noticed that in drivers/xilinx_common there are files related to
ll_fifo but in the drivers/Makefile there is no rule to build ll_fifo. The
same refers to the file arch/ppc/syslib/virtex_devices.c -> there are no
entries for LL_FIFO. I have the impression that one can use only LL_DMA but
not LL_FIFO.
Does anybody has modified the kernel to deal with LL_TEMAC together with
LL_FIFO?
I will be grateful for any hint.
Best Regards
Mirek
--
View this message in context: http://www.nabble.com/Compile-time-error%2C-compiling-Xilinx-Linux-2.6-for-XPS-LLTEMAC-tp16065692p18628194.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-07-24 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 8:30 Compile time error, compiling Xilinx Linux 2.6 for XPS LLTEMAC Mohammad Sadegh Sadri
2008-03-16 4:12 ` Koss, Mike (Mission Systems)
2008-03-16 21:43 ` Stephen Neuendorffer
2008-03-17 9:03 ` Mohammad Sadegh Sadri
2008-03-17 15:24 ` Rick Moleres
2008-03-17 15:49 ` Stephen Neuendorffer
2008-07-24 9:19 ` Mirek23 [this message]
2008-07-24 12:55 ` Xilinx Linux 2.6 for XPS LL_TEMAC and LL_FIFO problem Koss, Mike (Mission Systems)
2008-07-24 13:24 ` John Linn
2008-07-25 11:22 ` Mirek23
2008-07-25 21:54 ` John Linn
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=18628194.post@talk.nabble.com \
--to=miroslaw.dach@psi.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.