From: Grant Likely <grant.likely@secretlab.ca>
To: Roman Fietze <roman.fietze@telemotive.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Micrel PHY KSZ8001 on MPC5200B FEC
Date: Tue, 27 Oct 2009 14:08:51 -0600 [thread overview]
Message-ID: <fa686aa40910271308oa94ad4dkeff41859b6c4725a@mail.gmail.com> (raw)
In-Reply-To: <200910272054.47398.roman.fietze@telemotive.de>
On Tue, Oct 27, 2009 at 1:54 PM, Roman Fietze
<roman.fietze@telemotive.de> wrote:
> Hello Suvidh,
>
> On Tuesday 27 October 2009 17:47:51 suvidh kankariya wrote:
>
>> A driver for micrel phy exists in /drivers/net/phy/micrel.c. in
>> 2.6.30.
>
> Am I somewhat blind, or do you have access to other 2.6.30's than I
> have?
>
> I searched git.kernel.org, git.denx.de and git.secretlab.ca, but could
> not find that file, neither in the current master, nor in older tags
> somewhat related to "2.6.30", nor in any local clone in any version of
> the 2.6 since "He" created the repos.
No, there is a marvell driver, but not a micrel one. If the generic
phy driver doesn't work for you, then yes, add a new micrel driver.
To hook it up to the MPC5200 FEC, you just need to have the correct
PHY address in your board's .dts file.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-10-27 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1186.1256651657.12812.linuxppc-dev@lists.ozlabs.org>
[not found] ` <mailman.1186.1256651657.12812.linuxppc-dev@lists.ozlabs.or g>
2009-10-27 16:47 ` Re:Micrel PHY KSZ8001 on MPC5200B FEC suvidh kankariya
2009-10-27 19:54 ` Micrel " Roman Fietze
2009-10-27 20:08 ` Grant Likely [this message]
[not found] <mailman.1198.1256674402.12812.linuxppc-dev@lists.ozlabs.org>
[not found] ` <mailman.1198.1256674402.12812.linuxppc-dev@lists.ozlabs.or g>
2009-10-28 15:19 ` suvidh kankariya
2009-11-12 6:33 ` Roman Fietze
2009-11-12 7:03 ` Grant Likely
2009-10-27 12:17 Roman Fietze
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=fa686aa40910271308oa94ad4dkeff41859b6c4725a@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=roman.fietze@telemotive.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).