Date: Sat, 9 Jan 2010 00:26:57 +0000 (UTC) From: Pyun YongHyeon <yongari@FreeBSD.org> To: cvs-src-old@freebsd.org Subject: cvs commit: src/sys/dev/vge if_vge.c if_vgereg.h if_vgevar.h Message-ID: <201001090027.o090RE1p050998@repoman.freebsd.org>
index | next in thread | raw e-mail
yongari 2010-01-09 00:26:57 UTC
FreeBSD src repository
Modified files: (Branch: RELENG_8)
sys/dev/vge if_vge.c if_vgereg.h if_vgevar.h
Log:
SVN rev 201871 on 2010-01-09 00:26:57Z by yongari
MFC r200696,200740,200756,200758-200759,200972
r200696:
Add rudimentary WOL support. While I'm here remove enabling
busmastering/memory address in resume path. Bus driver will handle
that.
r200740:
Swap VGE_TXQTIMER and VGE_RXQTIMER register definition. Pending
timer for Tx queue is at 0x3E.
r200756:
Correct fragment bit definition in comments.
r200758:
VT6130 datasheet was wrong. If VT6130 receive a jumbo frame the
controller will split the jumbo frame into multiple RX buffers.
However it seems the hardware always dma the frame to 8 bytes
boundary for the split frames. Only the first part of the fragment
can have 4 byte alignment and subsequent buffers should be 8 bytes
aligned. Change RX buffer the alignment requirement to 8 bytes from
4 bytes.
r200759:
Disable jumbo frame support for PCIe VT6130/VT6132 controllers.
Quite contrary to VT6130 datasheet which says it supports up to 8K
jumbo frame, VT6130 does not seem to send jumbo frame that is
larger than 4K in length. Trying to send a frame that is larger
than 4K cause TX MAC hang.
Even though it's possible to allow 4K jumbo frame for VT6130, I
think it's meaningless to allow 4K jumbo frame. I'm not sure VT6132
also has the same limitation but I guess it uses the same MAC of
VT6130.
r200972:
Remove wrong assertion.
Revision Changes Path
1.37.2.11 +200 -21 src/sys/dev/vge/if_vge.c
1.2.22.6 +40 -4 src/sys/dev/vge/if_vgereg.h
1.4.22.9 +4 -1 src/sys/dev/vge/if_vgevar.h
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201001090027.o090RE1p050998>