From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: TEMAC driver available
Date: Fri, 13 Jul 2007 00:10:46 -0400 [thread overview]
Message-ID: <4696FB46.3020103@dlasys.net> (raw)
I have finally been inspired to complete my TEMAC driver to an alpha
state.
It nearly required dynamite - I had a client application where the
Xilinx/MV TEMAC
just did not work.
Anyway, the sucker is done and I guess I will post it as soon as I
have leaned it up
if there is any interest.
A brief description:
Might optionally (as in used to badly) support the LL_TEMAC.
Supports the more common PLB TEMAC ONLY in FIFO configurations.
Autonegotiates.
Is a reasonable approximation to a normal Linux network driver.
i.e. does not require xilinx_comon, or xilinx_edk or .....
Aside from hooks into the Linux build system is entirely
contained
in a single reasonably sized source.
Is extremely loosely based on older xilinx code from their
Webserver
sample application.
For someone that desparately wants to see it immediately you can
download
http://www.picocomputing.com/files/linux/linux-2.6-pico.tar.bz2
but that is a complete 2.6.22-rc4 kernel.org linux source with the
complete
Pico BSP
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next reply other threads:[~2007-07-13 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 4:10 David H. Lynch Jr. [this message]
2007-07-13 5:40 ` TEMAC driver available Grant Likely
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=4696FB46.3020103@dlasys.net \
--to=dhlii@dlasys.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 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).