From: Rick Jones <rick.jones2@hp.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: netdev@vger.kernel.org, "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: BCM5461 phy issue in 10M/Full duplex
Date: Wed, 18 Oct 2006 09:53:57 -0700 [thread overview]
Message-ID: <45365C25.9070601@hp.com> (raw)
In-Reply-To: <BD5AE82A-22F1-4813-A350-42532AB9A920@kernel.crashing.org>
Kumar Gala wrote:
> I was wondering if anyone has had any issues when trying to force a
> BCM5461 phy into 10M/full duplex. I seem to be having an issue in the
> two managed switches I've tried this on but autoneg to 10/half. This
> causes a problem in that I start seeing a large number of frame errors.
>
> I believe, but need to double check, that if I leave the BCM5461 in
> autoneg, and foce the switch to 10M/full that the BCM5461 will autoneg
> at 10M/half duplex.
Indeed, if one side is hardcoded, autoneg will "fail" and the side trying to
autoneg is required by the specs (not that I know chapter and verse to quote
from the IEE stuff :( to go into half-duplex.
Was 10M/Fullduplex ever standardized? If not I could see where kit might not be
willing/able to autoneg to that.
> Just wondering if anyone else has seen similar behavior with this PHY.
>
> thanks
>
> - kumar
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-10-18 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 13:57 BCM5461 phy issue in 10M/Full duplex Kumar Gala
2006-10-18 16:53 ` Rick Jones [this message]
2006-10-19 16:50 ` Maciej W. Rozycki
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=45365C25.9070601@hp.com \
--to=rick.jones2@hp.com \
--cc=galak@kernel.crashing.org \
--cc=macro@linux-mips.org \
--cc=netdev@vger.kernel.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).