All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@gefanuc.com>
To: Carlos Roberto Moratelli <carlos.moratelli@digitel.com.br>
Cc: Linuxppc-embedded@ozlabs.org
Subject: Re: MPC8313 and Marvell PHY 88e1112
Date: Mon, 01 Dec 2008 12:22:11 +0000	[thread overview]
Message-ID: <4933D6F3.6050807@gefanuc.com> (raw)
In-Reply-To: <1227873994.3812.21.camel@parana>

Carlos Roberto Moratelli wrote:
> Hi,
> 

Hi Carlos,

> I am working in a custom board based on a mpc8313erdb and my Kernel
> version is 2.6.24. This board has a Marvell PHY 88E1112 on TSEC2
> processor port. 
> 
> The problem is that the PHY is detected and configured, but no data can
> be send or received. I am sure that dtb is fine. In another custom board
> I have a 88e3015 on TSEC2 and it is working fine.
> 
> Did someone work with this PHY? Does Compiling gianfar and Marvell
> support on Kernel is enough? 

We have a board using a 8641d and Marvel 88E1111 PHY. I had problems getting the PHY to work correctly when using the Marvell PHY driver, however we were using the PHY as a standard PHY and found that the generic PHY driver worked just fine. Have you tried it without enabling the Marvell PHY driver so it uses the generic one?

Martyn

-- 
Martyn Welch MEng MPhil MIET (Principal Software Engineer)   T:+44(0)1327322748
GE Fanuc Intelligent Platforms Ltd,        |Registered in England and Wales
Tove Valley Business Park, Towcester,      |(3828642) at 100 Barbirolli Square,
Northants, NN12 6PF, UK T:+44(0)1327359444 |Manchester,M2 3AB  VAT:GB 729849476

  reply	other threads:[~2008-12-01 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 12:06 MPC8313 and Marvell PHY 88e1112 Carlos Roberto Moratelli
2008-12-01 12:22 ` Martyn Welch [this message]
2008-12-01 12:31 ` Richard Parsons

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=4933D6F3.6050807@gefanuc.com \
    --to=martyn.welch@gefanuc.com \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=carlos.moratelli@digitel.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.