From: Les Miklosy <lgm0@verizon.net>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Opencores Ethernet with Phy
Date: Mon, 09 Jun 2014 01:20:00 -0000 [thread overview]
Message-ID: <53950AE0.3000400@verizon.net> (raw)
I wish to assemble an Ethernet driver based on the opencores module for
low level functionality with phy support and the standalone layer for
io. Looking at the ecos database (ecos-3.0) it appears only the Arm,
Rattler/fcc and Moab/ppc405 PowerPC have used phy support. At the same
time no other hardware family use unmodified opencores drivers (granted
interfaces are similar for stop, start, can_send, send). Why have
opencores drivers been so unpopular among other processor families in
that regard? Why is the phy module used so seldom? Are there further
issues with the choice of io layer I should know about? I chose
standalone for the complement with Redboot rather than for an ECOS
application.
Thanks for any guidance. -Les
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2014-06-09 1:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53950AE0.3000400@verizon.net \
--to=lgm0@verizon.net \
--cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).