From: Dan Malek <dan@embeddededge.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Steven Scholz <steven.scholz@imc-berlin.de>,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: was: FEC on MPC860T & race condition
Date: Tue, 04 Feb 2003 14:55:53 -0500 [thread overview]
Message-ID: <3E401AC9.9090703@embeddededge.com> (raw)
In-Reply-To: 20030204193224.GB3522@ip68-0-152-218.tc.ph.cox.net
Tom Rini wrote:
> I believe this is wrong, in that trying to udelay() here is a bad idea.
I agree. All of the MII communcation is interrupt driven. This is easy
and the way everything should work on the 8xx. The link interrupt is
more challenging because the interrupt from that depends upon the phy
type and the board design. The link interrupts are either real interrupts
or managed with a timed thread.
If you need to wait before installing the link interrupt (which I still
don't understand why), this should be done as part of the phy discovery
interrupt. For example, add an indirect function pointer and if it isn't
NULL, call it at that time to do anything that must wait until the phy
is discovered and initialized.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-04 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 17:05 was: FEC on MPC860T & race condition Steven Scholz
2003-01-30 20:22 ` Dan Malek
2003-01-31 9:16 ` Steven Scholz
2003-02-03 21:09 ` Tom Rini
2003-02-04 8:39 ` Steven Scholz
2003-02-04 16:04 ` Tom Rini
2003-02-04 16:14 ` Steven Scholz
2003-02-04 19:32 ` Tom Rini
2003-02-04 19:55 ` Dan Malek [this message]
2003-02-07 7:35 ` Steven Scholz
2003-02-07 7:37 ` Steven Scholz
2003-02-07 17:12 ` Tom Rini
2003-02-07 17:15 ` Steven Scholz
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=3E401AC9.9090703@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
--cc=trini@kernel.crashing.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).