aboutsummaryrefslogtreecommitdiff
path: root/sys/dev/mii/rgephy.c
diff options
context:
space:
mode:
authorPyun YongHyeon <yongari@FreeBSD.org>2011-01-20 17:41:24 +0000
committerPyun YongHyeon <yongari@FreeBSD.org>2011-01-20 17:41:24 +0000
commit9eabd3a03a1006fa57018dbffefb6440a0aadb6d (patch)
treeba4cf5ce5a0ab589ea05a3e8bfb4857e839a4973 /sys/dev/mii/rgephy.c
parentfcd31ae7a333974dc62208d1ba5ee8bce54502c6 (diff)
downloadsrc-9eabd3a03a1006fa57018dbffefb6440a0aadb6d.tar.gz
src-9eabd3a03a1006fa57018dbffefb6440a0aadb6d.zip
MFC r217296:
For re(4) controllers that uses new jumbo frame scheme(RTL8168C/D/E), limit maximum RX buffer size to RE_RX_DESC_BUFLEN instead of blindly configuring it to 16KB. Due to lack of documentation, re(4) didn't allow jumbo frame on these controllers. However it seems controller is confused with jumbo frame such that it can DMA the received frame to wrong address instead of splitting it into multiple RX buffers. Of course, this caused panic. Since re(4) does not support jumbo frames on these controllers, make controller drop frame that is longer than RE_RX_DESC_BUFLEN sized frame. Fortunately RTL810x controllers, which do not support jumbo frame, have no such issues but this change also limited maximum RX buffer size allowed to RTL810x controllers. Allowing 16KB RX buffer for controllers that have no such capability is meaningless. Approved by: re (bz)
Notes
Notes: svn path=/releng/8.2/; revision=217647
Diffstat (limited to 'sys/dev/mii/rgephy.c')
0 files changed, 0 insertions, 0 deletions