* BCM5461 phy issue in 10M/Full duplex
@ 2006-10-18 13:57 Kumar Gala
2006-10-18 16:53 ` Rick Jones
0 siblings, 1 reply; 3+ messages in thread
From: Kumar Gala @ 2006-10-18 13:57 UTC (permalink / raw)
To: netdev; +Cc: Maciej W. Rozycki
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.
Just wondering if anyone else has seen similar behavior with this PHY.
thanks
- kumar
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: BCM5461 phy issue in 10M/Full duplex
2006-10-18 13:57 BCM5461 phy issue in 10M/Full duplex Kumar Gala
@ 2006-10-18 16:53 ` Rick Jones
2006-10-19 16:50 ` Maciej W. Rozycki
0 siblings, 1 reply; 3+ messages in thread
From: Rick Jones @ 2006-10-18 16:53 UTC (permalink / raw)
To: Kumar Gala; +Cc: netdev, Maciej W. Rozycki
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: BCM5461 phy issue in 10M/Full duplex
2006-10-18 16:53 ` Rick Jones
@ 2006-10-19 16:50 ` Maciej W. Rozycki
0 siblings, 0 replies; 3+ messages in thread
From: Maciej W. Rozycki @ 2006-10-19 16:50 UTC (permalink / raw)
To: Rick Jones; +Cc: Kumar Gala, netdev
On Wed, 18 Oct 2006, Rick Jones wrote:
> > 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.
Rather than forcing a PHY into 10Mbps, you may limit its advertised list
of speeds/duplex settings and let autonegotiation do the rest. It depends
on how smart code to manage your switch is; it's certainly doable with
Linux (you can do it with `mii-tool'; not sure about `ethtool') as long as
the NIC driver supports the necessary ioctls.
> Was 10M/Fullduplex ever standardized? If not I could see where kit might not
> be willing/able to autoneg to that.
It is standard.
Maciej
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-10-19 16:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-18 13:57 BCM5461 phy issue in 10M/Full duplex Kumar Gala
2006-10-18 16:53 ` Rick Jones
2006-10-19 16:50 ` Maciej W. Rozycki
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).