summary refs log tree commit diff
path: root/fs/udf
diff options
context:
space:
mode:
authorAnton Vorontsov <avorontsov@mvista.com>2010-06-30 06:39:12 +0000
committerDavid S. Miller <davem@davemloft.net>2010-06-30 11:35:42 -0700
commit7d3509774c2ef4ffd1c5fd2fac65dc4e071a6f21 (patch)
tree54d32c6f6f6c72fee208ab8dea9879697b613765 /fs/udf
parent70777d03466e7a8a41b0d34677454c92f4e93d89 (diff)
downloadlinux-7d3509774c2ef4ffd1c5fd2fac65dc4e071a6f21.tar.gz
gianfar: Implement workaround for eTSEC74 erratum
MPC8313ECE says:

"If MACCFG2[Huge Frame]=0 and the Ethernet controller receives frames
 which are larger than MAXFRM, the controller truncates the frames to
 length MAXFRM and marks RxBD[TR]=1 to indicate the error. The controller
 also erroneously marks RxBD[TR]=1 if the received frame length is MAXFRM
 or MAXFRM-1, even though those frames are not truncated.
 No truncation or truncation error occurs if MACCFG2[Huge Frame]=1."

There are two options to workaround the issue:

"1. Set MACCFG2[Huge Frame]=1, so no truncation occurs for invalid large
 frames. Software can determine if a frame is larger than MAXFRM by
 reading RxBD[LG] or RxBD[Data Length].

 2. Set MAXFRM to 1538 (0x602) instead of the default 1536 (0x600), so
 normal-length frames are not marked as truncated. Software can examine
 RxBD[Data Length] to determine if the frame was larger than MAXFRM-2."

This patch implements the first workaround option by setting HUGEFRAME
bit, and gfar_clean_rx_ring() already checks the RxBD[Data Length].

Signed-off-by: Anton Vorontsov <avorontsov@mvista.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/udf')
0 files changed, 0 insertions, 0 deletions