From: Laurent Pinchart <laurent.pinchart@capflow.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problem using FEC on a860T
Date: Mon, 22 Oct 2001 13:46:21 +0200 [thread overview]
Message-ID: <3BD4070D.9040405@capflow.com> (raw)
In-Reply-To: sbd43a78.005@tms-pty.com
>
>
>when I compile without "MDIO for PHY configuration"
>the kernel prints forever the message "fec.c[1374] mii_link_interrupt:
>unexpected Link interrupt
>on the console at boottime.
>
>when I compile with it, the kernel Oopses.
>after carefull debugging, I tracked it down to the line 1367 in
>arch/ppc/8xx_io/
> mii_do_cmd(dev, fep->phy->ack_int);
>
>it is a kernel access of bad area.
>
There is a problem in the FEC driver. The MII link interrupt gets
enabled too soon, before the PHY interface chip is configured. I believe
that the problem has been fixed in the linuxppc_2_4_devel tree. It was
supposed to be fixed much sooner, but the patch got lost somewhere
between the developpers and the development tree.
The problem should not occur if a full duplex ethernet link is connected
to the board at boot time.
Laurent Pinchart
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-22 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 4:25 Problem using FEC on a860T Jeremy Rosen
2001-10-22 11:46 ` Laurent Pinchart [this message]
2001-10-22 12:38 ` Young-Han, Kim
-- strict thread matches above, loose matches on Subject: below --
2001-10-22 11:38 Borracini Evandro-R45188
2001-10-22 14:51 Dave Ellis
2001-10-22 21:47 Jeremy Rosen
2001-10-23 1:00 Jeremy Rosen
2001-10-23 8:59 ` Laurent Pinchart
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=3BD4070D.9040405@capflow.com \
--to=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 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).