From: Timothy Ritchey <tritchey@vacuumgenesis.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 860T FEC
Date: Mon, 29 Jan 2001 15:11:36 -0800 [thread overview]
Message-ID: <3A75F8A8.64ADB0C@vacuumgenesis.com> (raw)
Has anyone had any luck with the 860T FEC driver in the 2.4 kernel (I am
using the 01/13/01 snapshot from FSMLabs). It is certainly not working
out-of-the-box as it were. For example, it tries calling mii_queue with
read operations that require the MII interrupt before interrupts have
even been enabled. There is code that needs to be run in the
fec_restart() function (such as the interrupt enable, and just enabling
the ethernet device) but it is never called. I cannot see how this code
was ever working properly. Is anyone running it that can refute this? I
have made some changes that seem to get it halfway there, but am not
getting any transmit interrupts yet (I am getting receive and mii
interrupts).
Cheers,
tim
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-29 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 23:11 Timothy Ritchey [this message]
2001-01-30 0:20 ` 860T FEC Dan Malek
2001-01-30 0:49 ` Wolfgang Denk
2001-01-31 4:14 ` Timothy Ritchey
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=3A75F8A8.64ADB0C@vacuumgenesis.com \
--to=tritchey@vacuumgenesis.com \
--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).