From: Dan Malek <dan@embeddededge.com>
To: "Walser, Martin" <mwalser@harris.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: no link changed interrupt
Date: Fri, 05 Jul 2002 14:15:33 -0400 [thread overview]
Message-ID: <3D25E245.70303@embeddededge.com> (raw)
In-Reply-To: 8D4C69676E66D511A1CB00508BBBB1921BCF4D@ranmx1.ran.harris.com
Walser, Martin wrote:
> Is there another way to get a link change without a hardware interrupt?
The only way to guarantee a link chnage interrupt is to use a PHY and
board design that supports a hardware interrupt. Some boards/PHYs do
this, others do not, and it is a board specific design. While you could
poll the PHY status at regular intervals, it would depend upon the PHY
status registers to properly publish/latch this information. There isn't
sufficient information in the generic PHY registers to detect link change,
so again this is software that will have to be implemented unique to your
PHY (it's proprietary registers) and board design.
The only reason the FEC (or any 8xx/82xx Ethernet controller) needs to
see a link change is to properly configure full/half duplex. It will
adapt to the different link speeds and other link attributes.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-05 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 5:51 no link changed interrupt Walser, Martin
2002-07-05 18:15 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-06 15:40 Jean-Denis Boyer
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=3D25E245.70303@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mwalser@harris.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).