From: Dan Malek <dan@netx4.com>
To: kd@flaga.is
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: fads823 ethernet interface does (seams) not send data
Date: Fri, 10 Dec 1999 14:56:41 -0500 [thread overview]
Message-ID: <38515AF9.3F756E5E@netx4.com> (raw)
In-Reply-To: OF18F33680.CFE448E8-ON00256843.003AAE59@flaga.is
kd@flaga.is wrote:
> Is it possible that this has something to do with the microcode patch
> presented in 2.213?
No, it has nothing to do with that. It is only skeleton code
that someday may perform a patch. The drivers are not yet
updated to handle it. The microcode patches either work
correctly or not at all, there is no in between.
I have never used an SCC Ethernet on the FADS, but there must
be control register bits or other 8xx general purpose I/O
pins that are required to be set correctly for the Ethernet PHY
to operate correctly. You have to also make sure all of the
SCC clock and I/O pins are properly configured for the hardware
design. I can guarantee some of this may not be correct for
the 823 FADS, as all boards seem to use something different.
The 8xx SCC Ethernet driver will only run on half duplex mode.
There is no auto sensing like is provided on (some) FEC 10/100
Ethernet PHYs. The SCC (and FEC) has to be configured differently
for half or full duplex operation.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-10 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-10 10:43 fads823 ethernet interface does (seams) not send data kd
1999-12-10 19:56 ` Dan Malek [this message]
1999-12-14 21:35 ` Richard Hendricks
-- strict thread matches above, loose matches on Subject: below --
2007-04-26 17:52 Jason.Work
1999-12-10 10:30 raphael.bossek
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=38515AF9.3F756E5E@netx4.com \
--to=dan@netx4.com \
--cc=kd@flaga.is \
--cc=linuxppc-embedded@lists.linuxppc.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).