From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: was: FEC on MPC860T & race condition
Date: Tue, 04 Feb 2003 09:39:05 +0100 [thread overview]
Message-ID: <3E3F7C29.8030807@imc-berlin.de> (raw)
In-Reply-To: 20030203210959.GA7857@ip68-0-152-218.tc.ph.cox.net
Tom Rini schrieb:
> On Fri, Jan 31, 2003 at 10:16:25AM +0100, Steven Scholz wrote:
>
>>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!
>
>
> Um, but there is in linuxppc_2_4 ?
Is that a question or a statement?
I just hab a look at arch/ppc/8xx_io/fec.c in the recent linuxppc_2_4 and could
find this problem fixed! The MII irq is still requested very early without
waiting for the PHY to discovered!
Cheers,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-04 8:39 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 [this message]
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=3E3F7C29.8030807@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--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).