linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Steffen Rumler <Steffen.Rumler@siemens.com>
Cc: "Gérard Guével" <gguevel@interfaceconcept.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8260 FCC enet driver problem
Date: Mon, 13 Oct 2003 15:30:16 -0400	[thread overview]
Message-ID: <3F8AFD48.5070507@embeddededge.com> (raw)
In-Reply-To: 3F86A52B.1070803@siemens.com


Steffen Rumler wrote:


> I have not seen this kind of synchronization (PHY -- MAC) in fcc_enet.c.
> I don't know why.

The code is there.  You need a PHY interrupt to the processor when
the link status changes, then the PHY status is interrogated to set
up the MAC.


	-- Dan


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

      reply	other threads:[~2003-10-13 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 15:20 8260 FCC enet driver problem Gérard Guével
2003-10-10 12:25 ` Steffen Rumler
2003-10-13 19:30   ` Dan Malek [this message]

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=3F8AFD48.5070507@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=Steffen.Rumler@siemens.com \
    --cc=gguevel@interfaceconcept.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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).