From: Sascha Hauer <s.hauer@pengutronix.de>
To: Matthias Kaehlcke <matthias@kaehlcke.net>
Cc: netdev@vger.kernel.org
Subject: Re: FEC driver: rcv is not +last
Date: Thu, 8 Apr 2010 15:20:33 +0200 [thread overview]
Message-ID: <20100408132033.GJ3688@pengutronix.de> (raw)
In-Reply-To: <20100408104033.GI3787@darwin>
On Thu, Apr 08, 2010 at 12:40:33PM +0200, Matthias Kaehlcke wrote:
> hi,
>
> i have problems with the FEC on a i.MX25 3-Stack board. the kernel is
> v2.6.34-rc2 plus the following patch:
> http://patchwork.ozlabs.org/patch/41235/
>
> the following traces are generated at boot time:
>
> FEC Ethernet Driver
> fec: PHY @ 0x1, ID 0x20005ce1 -- unknown PHY!
> ...
> eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
> ...
> FEC ENET: rcv is not +last
> FEC ENET: rcv is not +last
> FEC ENET: rcv is not +last
> FEC ENET: rcv is not +last
> ...
No idea, I have never seen this message. Does the controller work
besides these messages?
>
> the PHY of the board is a DP83840, which is not supported by the
> driver. could this be the problem? i tried to make the kernel think
> the DP83840 is a DP83848, which is supported, but the behaviour is the
> same except the 'unknown PHY' warning.
This should be solved by the phylib patches recently posted for the fec
driver.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2010-04-08 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 10:40 FEC driver: rcv is not +last Matthias Kaehlcke
2010-04-08 13:20 ` Sascha Hauer [this message]
2010-04-08 14:53 ` Matthias Kaehlcke
2010-04-08 16:04 ` Matthias Kaehlcke
2010-04-08 16:05 ` Sascha Hauer
2010-04-09 5:42 ` Bryan Wu
2010-04-09 8:17 ` Matthias Kaehlcke
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=20100408132033.GJ3688@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=matthias@kaehlcke.net \
--cc=netdev@vger.kernel.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).