From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Dan Malek <dan@embeddededge.com>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>,
laurent.pinchart@capflow.com
Subject: Re: was: FEC on MPC860T & race condition
Date: Fri, 31 Jan 2003 10:16:25 +0100 [thread overview]
Message-ID: <3E3A3EE9.7000608@imc-berlin.de> (raw)
In-Reply-To: 3E39898E.5060804@embeddededge.com
Dan Malek wrote:
> Steven Scholz wrote:
>
>> You, Laurent, told us about a race condition.
>> You, Dan, first claimed, it was already fix but mentioned later that
>> the patch
>> was somehow lost.
>
>
> IIRC, it was the usual problem of having it fixed in only one of the
> two 2.4 trees. I ensured both trees were made up to date.
>
There is still no fix in linuxppc_2_4_devel!
>> Now I have this problem as well and realised that in 2.4.20 the
>> "mii_link_interrupt interrupt handler is still registered before the
>> PHY chip is initialized".
>
> The link interrupt is board design and PHY dependent. I don't think there
> is any one "right" way to initialize this interrupt handler. If you have
> something that isn't working to your liking, we may have to extend the
> MII logic in some way to accomodate this. Keep in mind that the existing
> driver is likely working with other boards, and you don't want to break
> those configurations.
There is a race condition!
Lucky you if you never see it! :o)
But fair enough. If more people had this problem, the fix would be in the trees
by now.
How about adding something like CONFIG_FEC_LATE_ENABLE_PHY or so. Of course with
a help text in Documentation/Configure.help so that people having that problem
could easily enable that. And for the rest (although this might be the majority)
everythings stays as it it.
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-31 9:16 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 [this message]
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
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=3E3A3EE9.7000608@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=dan@embeddededge.com \
--cc=laurent.pinchart@capflow.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.