| commit | b4b6cda2298b0c9a0af902312184b775b8867c65 | |
| author | Luis R. Rodriguez <lrodriguez@atheros.com> | |
| Fri, 21 Nov 2008 01:15:13 +0000 (20 17:15 -0800) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Tue, 25 Nov 2008 21:13:08 +0000 (25 16:13 -0500) | ||
| tree | 7357a39a07d5cb7a4360161fb8acaa09a198c77d | treesnapshot (tar.gz zip) |
| parent | ca0c7e5101fd4f37fed8e851709f08580b92fbb3 | commitdiff |
ath9k: correct expected max RX buffer size
We should only tell the hardware its capable of DMA'ing
to us only what we asked dev_alloc_skb(). Prior to this
it is possible a large RX'd frame could have corrupted
DMA data but for us but we were saved only because we
were previously also pci_map_single()'ing the same large
value. The issue prior to this though was we were unmapping
a smaller amount which the prior DMA patch fixed.
Signed-off-by: Bennyam Malavazi <Bennyam.Malavazi@atheros.com>
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
We should only tell the hardware its capable of DMA'ing
to us only what we asked dev_alloc_skb(). Prior to this
it is possible a large RX'd frame could have corrupted
DMA data but for us but we were saved only because we
were previously also pci_map_single()'ing the same large
value. The issue prior to this though was we were unmapping
a smaller amount which the prior DMA patch fixed.
Signed-off-by: Bennyam Malavazi <Bennyam.Malavazi@atheros.com>
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| drivers/net/wireless/ath9k/recv.c | diffblobblamehistory |