All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Radensky <felix@allot.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ppc405_enet problems
Date: Mon, 10 Dec 2001 19:56:18 +0200	[thread overview]
Message-ID: <3C14F742.A922C291@allot.com> (raw)
In-Reply-To: 20011210161702.GE22045@cpe-24-221-152-185.az.sprintbbd.net


Hi,

Support for DP83846A is already present in drivers/net/ppc405_phy.c
My guess is that phy reading fuctions are misbehaving, since i keep
getting different values of Phy id on each boot.

Felix.

Tom Rini wrote:

> On Mon, Dec 10, 2001 at 03:28:13PM +0200, Felix Radensky wrote:
> >
> > Hi,
> >
> > I'm trying to run the latest linuxppc_2_4_devel kernel on
> > our custom 405GP based board. I get kernel panic when an
> > attempt is made to probe for ethernet controller phy:
> >
> > Kernel panic: eth0: PHY id 0xfbc85c20 is not supported!
> >
> > The phy is National Semiconductor DP83846AVHG.
> > It works fine with Monta Vista HHL 2.0 kernel.
>
> IIRC, the hhl 2.0 kernel assumes that you have a National Semiconductor
> DP83843.  I'm guessing the 83846 is similar enough such that it just
> works.  Take a look at drivers/net/ppc405_phy.c, and add in support for
> your PHY (and please sumbit a patch to the list).
>
> --
> Tom Rini (TR1265)
> http://gate.crashing.org/~trini/


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

  reply	other threads:[~2001-12-10 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10 13:28 ppc405_enet problems Felix Radensky
2001-12-10 16:17 ` Tom Rini
2001-12-10 17:56   ` Felix Radensky [this message]
2001-12-10 20:03     ` Armin Kuster
2001-12-11  7:51 ` David Müller (ELSOFT AG)
2001-12-11 13:32   ` Felix Radensky
2001-12-11 18:11     ` Armin Kuster

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=3C14F742.A922C291@allot.com \
    --to=felix@allot.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.org \
    /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.