summaryrefslogtreecommitdiffstats
path: root/sys/dev/ixgb
diff options
context:
space:
mode:
authormarius <marius@FreeBSD.org>2011-08-19 19:12:58 +0000
committermarius <marius@FreeBSD.org>2011-08-19 19:12:58 +0000
commit2852f5cc381b4789a383f57d7ae05c5752eb69eb (patch)
tree92ff24c835440203422d9ec935c2eae0d2ebddea /sys/dev/ixgb
parentb31a18eeb421bb3ef0f05f205f940cca8a5b1c1f (diff)
downloadFreeBSD-src-2852f5cc381b4789a383f57d7ae05c5752eb69eb.zip
FreeBSD-src-2852f5cc381b4789a383f57d7ae05c5752eb69eb.tar.gz
r221812 reveals that at least some Broadcom PHYs default to being not only
isolated but also powered down after a reset and while they just work fine [sic] when both is the case they don't if they are only deisolate but still powered down. So in order to put PHYs in an overall normal operation mode for the common case, ensure in mii_phy_reset() that they are not powered down after a reset. Unfortunately, this only helps in case of BCM5421, while BCM5709S apparently only work when they remain isolated and powered down after a reset. So don't call mii_phy_reset() in brgphy_reset() and implement the reset locally leaving the problematic bits alone. Effectively this bypasses r221812 for brgphy(4). Thanks to Justin Hibbits for doing a binary search in order to identify the problematic commit. PR: 157405, 158156 Reviewed by: yongari (mii_phy_reset() part) Approved by: re (kib) MFC after: 3 days
Diffstat (limited to 'sys/dev/ixgb')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud