diff options
| author | Luis R. Rodriguez <lrodriguez@atheros.com> | 2008-12-02 12:51:21 -0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2008-12-05 10:55:15 -0800 |
| commit | 0c089be68ac41ca6e0e38dea22af8b91c52d1ee0 (patch) | |
| tree | 4c5d1be6d05993171ae7bad6e53f08621aaa8026 /include | |
| parent | c5353210bb519a01e54cdcefd940234b0e70984c (diff) | |
ath9k: correct expected max RX buffer size
commit b4b6cda2298b0c9a0af902312184b775b8867c65 upstream
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: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions