From: Edward Bockhoefer <edb@datadesigncorp.net>
To: dhlii@comcast.net, ammubhai@gmail.com, linuxppc-embedded@ozlabs.org
Subject: Re: Xilinx TEMAC
Date: Thu, 03 Aug 2006 10:34:40 -0400 [thread overview]
Message-ID: <44D20980.3030702@datadesigncorp.net> (raw)
In-Reply-To: <44D1991A.2070208@dlasys.net>
Thank you for the reply David,
I have started the montavista 10/100 enet port from the xilinx edk
generated 2.4 driver to the 2.6 driver. Unfortunately, I can't post the
driver port publicly because it's not GLP'd, as far as I know. We only
needed a 10/100 mac, so we didn't bother with a TEMAC. I got the obp and
enet directories to compile but I crash on link with an undefined reference:
**********************************************
[root@bockhoefer linux-2.6.17.6]# make
CHK include/linux/version.h
CHK include/linux/compile.h
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o(.init.text+0x246c): In function `fbcon_bmove':
drivers/video/console/fbcon.c:1887: undefined reference to `init_etherdev'
make: *** [.tmp_vmlinux1] Error 1
[root@bockhoefer linux-2.6.17.6]#
*********************************************
I will work on this more today. If you want to send me your TEMAC code,
please do so. I can always use the reference.
--
Best Regards,
Edward Bockhoefer
Data Design Corporation
7851-A Beechcraft Ave.
Gaithersburg, MD 20879
Ph: 301-670-1157 ext 36
Fax: 301-926-6441
David H. Lynch Jr. wrote:
>Ameet Patil wrote:
>
>
>> > Did you happen to get an Ethernet mac going on the virtex2 or
>> > virtex4 with the 2.6 kernel?
>>
>>Nope! :-(
>>Rumour has it that Montavista is soon going to release the source for
>>2.6 kernel to run on Xilinx platforms.
>>
>>
>>
>>
> I have 2 different TEMAC's working under 2.6 with a V4.
>
> The MontaVista driver that has been posted on the list that I think
>is from MontaVista for the PLB TEMAC with very minor modifications to
>get it to work at speeds other than GigaBit.
>
> A driver I wrote for the LocalLink TEMAC that works limpingly. I
>have been unable to figure out how to get a receive interrupt from the
>LocalLink TEMAC so receives are polled and performance is poor.
> I have pretty much abandoned work on it - my client wants the
>smallest possible FPGA footprint BUTanother OS I am porting requires
>interrupt driven IO and we are looking for a single minimal hardware
>implimentation for all platforms.
>
> Anyway, if anyone wants the LL TEMAC in its current state I can post it.
> Currently it sends fine. It drops about 50% of all received packets
>- but that is probably debugging overhead and poll rate tuning.
>
>
>
>
>
>
>
next prev parent reply other threads:[~2006-08-03 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44CE4C1D.6050103@datadesigncorp.net>
2006-07-31 19:48 ` cool article Ameet Patil
[not found] ` <44CF89B5.7080906@datadesigncorp.net>
2006-08-02 10:15 ` Ameet Patil
2006-08-03 6:35 ` Xilinx TEMAC David H. Lynch Jr.
2006-08-03 14:34 ` Edward Bockhoefer [this message]
2006-08-03 18:53 ` Frank D Lombardo
2012-10-12 12:56 Xilinx Temac Guillaume Dargaud
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=44D20980.3030702@datadesigncorp.net \
--to=edb@datadesigncorp.net \
--cc=ammubhai@gmail.com \
--cc=dhlii@comcast.net \
--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.