From: Matthias Kaehlcke <matthias@kaehlcke.net>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: netdev@vger.kernel.org
Subject: Re: FEC driver: rcv is not +last
Date: Thu, 8 Apr 2010 18:04:46 +0200 [thread overview]
Message-ID: <20100408160446.GL29538@darwin> (raw)
In-Reply-To: <20100408145324.GH29538@darwin>
El Thu, Apr 08, 2010 at 04:53:24PM +0200 Matthias Kaehlcke ha dit:
> El Thu, Apr 08, 2010 at 03:20:33PM +0200 Sascha Hauer ha dit:
>
> > 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?
>
> nope
>
> > > 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.
>
> thanks for the pointer!
>
> i just applied the patch. it actually makes the 'unkown PHY' and even
> the 'FEC ENET: rcv is not +last' messages disappear, but networking
> still doesn't work
i just received a mail from our distributor:
the PDK board they gave us for evaluation is a preliminary version,
with a slightly different hardware than the official one. they suppose
that's the reason of our problem
sorry for the noise
--
Matthias Kaehlcke
Embedded Linux Developer
Barcelona
Debugging is like alien abduction. Large blocks of time disappear,
for which you have no explanation
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
next prev parent reply other threads:[~2010-04-08 16:06 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
2010-04-08 14:53 ` Matthias Kaehlcke
2010-04-08 16:04 ` Matthias Kaehlcke [this message]
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=20100408160446.GL29538@darwin \
--to=matthias@kaehlcke.net \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).