summaryrefslogtreecommitdiff
path: root/drivers/net/phy
diff options
context:
space:
mode:
authorManfred Rudigier <Manfred.Rudigier@omicron.at>2012-01-09 23:26:51 +0000
committerDavid S. Miller <davem@davemloft.net>2012-01-12 15:26:01 -0800
commit9c4886e5e63bbecea0b560829a96f37e8d9ddd7c (patch)
tree1cc0c8626a929ecf04f8f84f9b289a20e95f32b5 /drivers/net/phy
parentdb83d136d7f7534857cd9c6e588adc08a428b190 (diff)
downloadlinux-3.10-9c4886e5e63bbecea0b560829a96f37e8d9ddd7c.tar.gz
linux-3.10-9c4886e5e63bbecea0b560829a96f37e8d9ddd7c.tar.bz2
linux-3.10-9c4886e5e63bbecea0b560829a96f37e8d9ddd7c.zip
gianfar: Fix invalid TX frames returned on error queue when time stamping
When TX time stamping for PTP messages is enabled on a socket, a time stamp is returned on the socket error queue to the user space application after the frame was transmitted. The transmitted frame is also returned on the error queue so that an application knows to which frame the time stamp belongs. In the current implementation the TxFCB is immediately followed by the frame. Since the eTSEC inserts the TX time stamp 8 bytes after the TxFCB, parts of the frame have been overwritten and an invalid frame was returned on the socket error queue. This patch fixes the described problem by adding additional 16 padding bytes between the TxFCB and the frame for all messages sent from a time stamping enabled socket (other sockets are not affected). Signed-off-by: Manfred Rudigier <manfred.rudigier@omicron.at> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/phy')
0 files changed, 0 insertions, 0 deletions