From: Timothy Ritchey <tritchey@vacuumgenesis.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 860T FEC
Date: Tue, 30 Jan 2001 20:14:47 -0800 [thread overview]
Message-ID: <3A779137.9598691A@vacuumgenesis.com> (raw)
In-Reply-To: 200101300049.f0U0n3G05511@denx.local.net
Wolfgang Denk wrote:
>
> BTW: I've sent all these patches to Dan and Cort and Ben, so I hope
> at least part of it will make it in the official sources.
Thanks! I finally got it up and running, and have ethernet!!!. I had to
make some changes WRT some of the MII commands, which I don't think
would impact anyone else, but I also had to change the order of setting
the fecp->imask, and clearing the interrupts. The patch had it clearing
the interrupts, then setting the mask. It needed to be the otherway
around, at least for me.
Cheers,
tim
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-01-31 4:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 23:11 860T FEC Timothy Ritchey
2001-01-30 0:20 ` Dan Malek
2001-01-30 0:49 ` Wolfgang Denk
2001-01-31 4:14 ` Timothy Ritchey [this message]
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=3A779137.9598691A@vacuumgenesis.com \
--to=tritchey@vacuumgenesis.com \
--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).