linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: "Thomas Lange" <thomas@corelatus.com>
Cc: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Potential problem in fec.c for 8xx
Date: Fri, 20 Sep 2002 16:13:35 +0200	[thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJKECBCJAA.Stephan.Linke@epygi.de> (raw)
In-Reply-To: <3D8B1950.CE2DB9A1@corelatus.com>


Hi Thomas,

normaly this shouldn't happen. By default the interrupts of the PHY chips
are disabled (see PHY register settings). So when you enable the 8xx
interrupt nothing should happen.
So FEC driver has the time to detect the PHY and setup the registers. After
the registers are initializes (esp. interrupt mask) the first interrupts may
appeare.

Maybe there is the following problem: The PHY CHIP doesn't get a reset
signal when rebooting your board (warm start). In that case I could imagine
that the interrupts are still enabled in the PHY chip.... (Do you have the
same problem after a cold start?)

Regards, Stephan

> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of Thomas
> Lange
> Sent: Freitag, 20. September 2002 14:49
> To: linuxppc-embedded@lists.linuxppc.org
> Subject: Potential problem in fec.c for 8xx
>
>
>
> When using MII, the interrupt for link status changes
> is enabled before the PHY type has been detected.
>
> If a link status change happens before PHY is detected,
> you will get kernel panic in mii_link_interrupt
> because the MII functions are undefined.
>
> The correct way to do this would be to move the
> enabling of MII interrupts from fec_enet_init
> to mii_discover_phy3.
>
> I can prepare a patch if someone points me to
> the correct version to patch.
>
> /Thomas
>
>
>


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

  reply	other threads:[~2002-09-20 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 12:49 Potential problem in fec.c for 8xx Thomas Lange
2002-09-20 14:13 ` Stephan Linke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-20 20:26 Dave Ellis

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=FCEAKDJJAPHPLJFINDAJKECBCJAA.Stephan.Linke@epygi.de \
    --to=stephan.linke@epygi.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=thomas@corelatus.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).