linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "sruel@oerlikon.ca" <sruel@oerlikon.ca>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: eth1 FEC on RPX-CLLF info
Date: Wed, 21 Nov 2001 18:59:57 +0100	[thread overview]
Message-ID: <20011121180002.AF8371138D@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 21 Nov 2001 12:52:50 EST." <3BFBE9F2.2090800@oerlikon.ca>


Dear Sebastien,

in message <3BFBE9F2.2090800@oerlikon.ca> you wrote:
>
> >What happens when you enable the MDIO option?
>
> It says:
> ...
> fec: No PHY device found.

Well, this seems to be a hint...

> Yes, the LXT971 code is enabled in fec.c.
> I find out that the older CLLF_BW board was using a QS6612 PHY, but the
> CLLF_BW31 (my board revision) is using an LXT971.

Check if your hardware requires to enable and/or reset the PHY  using
some port pins or bits in a board control register...

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
A fail-safe circuit will destroy others.                 -- Klipstein

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2001-11-21 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3BFBE9F2.2090800@oerlikon.ca>
2001-11-21 17:59 ` Wolfgang Denk [this message]
     [not found] <D73A25AA6E54D511AD74009027B1110F04F5E1@ORION>
2001-11-13 11:03 ` Linuxppc and MPC8255 routing performance Ricardo Scop
2001-11-13 17:02   ` Dan Malek
2001-11-13 12:38     ` Ricardo Scop
2001-11-13 18:21       ` Dan Malek
2001-11-20 17:07         ` eth1 FEC on RPX-CLLF info sruel
2001-11-20 19:03           ` Wolfgang Denk

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=20011121180002.AF8371138D@denx.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=sruel@oerlikon.ca \
    /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).