linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Todd Poynor <tpoynor@mvista.com>
To: andrew may <acmay@acmay.homeip.net>
Cc: Venkatesh Ramamurthy <rpranesh@hotmail.com>,
	mporter@mvista.com, frank_rowand@mvista.com,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux on 440GP Networking issues
Date: Wed, 01 May 2002 12:23:23 -0700	[thread overview]
Message-ID: <3CD040AB.5000702@mvista.com> (raw)
In-Reply-To: 20020501120137.B9360@ecam.san.rr.com


>>Yep, the kernel tries to setup the second controller. But there is someting
>>very strange. Eventhough there is no network cable connected to the second
>>ethernet port , the OCP ENET driver says that it is 10Mbps, Link up and half
>>duplex.

The above is the default provided when autonegotiation doesn't turn up
anything useful, at least for the AMD Am79C875* PHYs (see ibm_ocp_phy.c:
mii_parse_Am79C875_pcr), which probably isn't the way to go.  And
handling of the "no link" case does seem to need some work.

Could verify whether the lockup is related to configuring 2 EMACs by a
hack to ppc405_enet_open to return -ENODEV if fep->emac_num > 0.  If
that boots fine then see if ppc405_eth_mal_dump shows registers such as
EMAC0's TXCTP0R or RXCTP0R changing values after EMAC1 is configured.
If so, that FIXME in the ppc405_enet_open code probably needs revisiting.


--
Todd


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

       reply	other threads:[~2002-05-01 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F45zrLCCtgx8VUkRacU000059cf@hotmail.com>
     [not found] ` <20020501120137.B9360@ecam.san.rr.com>
2002-05-01 19:23   ` Todd Poynor [this message]
2002-05-02  0:24     ` Linux on 440GP Networking issues Roland Dreier

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=3CD040AB.5000702@mvista.com \
    --to=tpoynor@mvista.com \
    --cc=acmay@acmay.homeip.net \
    --cc=frank_rowand@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mporter@mvista.com \
    --cc=rpranesh@hotmail.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).