From: Matthias Kaehlcke <matthias@kaehlcke.net>
To: Bryan Wu <bryan.wu@canonical.com>
Cc: netdev@vger.kernel.org, Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: FEC driver: rcv is not +last
Date: Fri, 9 Apr 2010 10:17:59 +0200 [thread overview]
Message-ID: <20100409081759.GR29538@darwin> (raw)
In-Reply-To: <4BBEBE57.8020800@canonical.com>
Hi Bryan,
El Fri, Apr 09, 2010 at 01:42:47PM +0800 Bryan Wu ha dit:
> On 04/08/2010 06:40 PM, 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!
> >...
> please try this patch on your hardware, it introduced phylib
> supporting in fec.c driver:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/012214.html
sascha pointed me yesterday to your patch, i tried it with v2
(http://lkml.org/lkml/2010/3/31/130), but without success.
our distributor informed us that the board they let us is a
preliminary hardware version and that this is probably the cause of
the problem :/
i hope i'll get soon my hands on an offical board release and can
verify that the FEC just works ;)
thanks for your help!
--
Matthias Kaehlcke
Embedded Linux Developer
Barcelona
If sharing a thing in no way diminishes it,
it is not rightly owned if it is not shared
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
prev parent reply other threads:[~2010-04-09 8:19 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
2010-04-08 16:05 ` Sascha Hauer
2010-04-09 5:42 ` Bryan Wu
2010-04-09 8:17 ` Matthias Kaehlcke [this message]
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=20100409081759.GR29538@darwin \
--to=matthias@kaehlcke.net \
--cc=bryan.wu@canonical.com \
--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).