From: Grant Likely <grant.likely@secretlab.ca>
To: Michael Guntsche <mike@it-loops.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: PHY not found after migration of gianfar driver to an of_platform_driver
Date: Sat, 28 Feb 2009 08:03:57 -0700 [thread overview]
Message-ID: <fa686aa40902280703p5ad8ee73y116d7e2252df21a5@mail.gmail.com> (raw)
In-Reply-To: <D5EBE54F-FD6D-4973-8835-33541ADCBABD@it-loops.com>
Hey Michael,
I just wanted to let you know that I'm reading your questions, and I'm
crafting a reply, but it's not trivial and I'm also swamped under at
the moment. I should have something for you in the next few days. I
just didn't want you to think you were being ignored.
g.
On Thu, Feb 26, 2009 at 12:15 PM, Michael Guntsche <mike@it-loops.com> wrot=
e:
> Hello everyone,
>
> I recently obtained a Mikrotik RB600 and applied the patch from
> http://cynigram.com/~nfontes/rb600/=A0to get it up and running with 2.6.2=
8.3
> With this patch applied everything was detected on the board and worked. =
For
> testing purposes I tried a recent git snapshot and noticed that the gianf=
ar
> driver had problems.
> While the the Gianfar was detected
>
> [ =A0 =A00.549115] Gianfar MII Bus: probed
> [ =A0 =A00.553316] eth0 (fsl-gianfar): not using net_device_ops yet
> [ =A0 =A00.560861] eth0: Gianfar Ethernet Controller Version 1.2,
> 00:0c:42:28:de:4e
> [ =A0 =A00.568024] eth0: Running with NAPI enabled
> [ =A0 =A00.572234] eth0: 256/256 RX/TX BD ring size
> [ =A0 =A00.576802] eth1 (fsl-gianfar): not using net_device_ops yet
> [ =A0 =A00.584200] eth1: Gianfar Ethernet Controller Version 1.2,
> 00:0c:42:28:de:4f
> [ =A0 =A00.591345] eth1: Running with NAPI enabled
> [ =A0 =A00.595575] eth1: 256/256 RX/TX BD ring size
>
> trying to up either of the devices gave me
>
> [ =A0 =A08.724818] mdio@24520:01 not found
> [ =A0 =A08.728330] eth1: Could not attach to PHY
> [ =A0 =A08.732945] mdio@24520:01 not found
> [ =A0 =A08.737720] eth1: Could not attach to PHY
>
> I tracked this back to commit "b31a1d8b41513b96e9c7ec2f68c5734cef0b26a4
> gianfar: Convert gianfar to an of_platform_driver". Reverting this one an=
d
> applying for fsc_soc.c made the two nics work again.
> I tried to figure out what was causing the problem in the first place, bu=
t
> failed miserably. I am pretty sure it is just a minor probing issue
> somewhere in the code but I am not able to spot that.
> Maybe someone more knowledgeable than me can take a look at it and help m=
e
> out a little bit.
>
> According to lspci the board is a
>
> 00:00.0 Power PC: Freescale Semiconductor Inc MPC8343 (rev 30)
>
> Please CC me in any replies since I am not subscribed to the ML .. yet.
>
> Thanks in advance,
> Michael
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-02-28 15:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 19:15 PHY not found after migration of gianfar driver to an of_platform_driver Michael Guntsche
2009-02-26 23:38 ` Michael Guntsche
2009-02-27 18:39 ` Michael Guntsche
2009-02-28 13:41 ` Michael Guntsche
2009-02-28 15:03 ` Grant Likely [this message]
[not found] ` <3B1D47A2-329E-491E-B3AC-E76C1CE1762D@it-loops.com>
[not found] ` <fa686aa40903011353t464b1df3obd553132e5bc2570@mail.gmail.com>
[not found] ` <CD026D29-687D-4078-960E-108CC94C30E4@it-loops.com>
2009-03-02 1:15 ` Grant Likely
2009-03-02 11:58 ` Michael Guntsche
2009-03-02 15:08 ` Grant Likely
2009-03-03 7:35 ` Michael Guntsche
2009-03-03 9:49 ` Michael Guntsche
2009-03-03 15:23 ` Grant Likely
[not found] ` <7AC161D8-83A8-4330-A2CF-3120F15D9038@it-loops.com>
[not found] ` <fa686aa40903031310o4e0c0b2bnba0544012b0fb8bc@mail.gmail.com>
[not found] ` <68DDAAA9-42AF-4E9C-907C-7D3269816184@it-loops.com>
2009-03-04 15:57 ` Grant Likely
2009-03-04 16:47 ` Michael Guntsche
2009-03-05 7:41 ` Michael Guntsche
2009-03-05 15:08 ` Grant Likely
2009-03-08 12:18 ` Wolfgang Ocker
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=fa686aa40902280703p5ad8ee73y116d7e2252df21a5@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=mike@it-loops.com \
/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).