From: Dan Hopper <eusdbho@rtp.ericsson.se>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: trouble with FEC on MPC860T - FEC_INTERRUPT not going off?
Date: Sat, 2 Dec 2000 19:44:40 -0500 [thread overview]
Message-ID: <20001202194440.A9761@slug.rtp.ericsson.se> (raw)
In-Reply-To: <200012020923.eB29NoF07306@denx.local.net>
Wolfgang Denk <wd@denx.de> remarked:
> in message <20001201223622.A28837@slug.rtp.ericsson.se> you wrote:
> >
> > FEC, and am now working on the kernel. At the moment, I'm using the
> > 2.4-2000-11-11 kernel from ftp.denx.de as a baseline, since it
>
> This version of the kernel is derived from 2.4.0-test5 from July, 26.
OK. Is there a newer one that's also friendly to 860Ts? Some
others appeared somewhat different configuration-wise. What base do
you use?
> I have run into the same problem, and my suggestion is to try the
> version of fec.c I'll attach below (I've sent this to Dan Malek some
> days ago, but haven't heard anything since).
I did, and it seems to work great. It negotiated a 100Mbps
half-duplex after detecting the PHYs, and took off from there with
NFS. I did need to hook up the interrupt line from the 972, as you
indicated.
Next week, I guess I'll be doing a CVS merge from your latest
ppcboot tree and see if I can get that FEC code to play.
Thanks for your help!
Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-03 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-02 9:23 trouble with FEC on MPC860T - FEC_INTERRUPT not going off? Wolfgang Denk
2000-12-03 0:44 ` Dan Hopper [this message]
2000-12-03 14:40 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2000-12-02 3:36 Dan Hopper
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=20001202194440.A9761@slug.rtp.ericsson.se \
--to=eusdbho@rtp.ericsson.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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).