Bruno Randolf 281c56dd27 ath5k: correct padding in tx descriptors ... when setting up the tx descriptors for the hardware we must account for any padding between the header and the data we might have added previously. frame len is the length of the frame in the air (including FCS but no padding) and buffer len is the length of the buffer (including padding, but without FCS). changing the way ah_setup_tx_desc is called: now excluding the FCS, since it's easier to add that in the function where we need it. before this fix we sent trailing zero bytes after the packet (because frame len included the padding) which was not a big problem without WEP, but with WEP this resultes in a wrong WEP checksum and the packet is discarded - which is how i noticed at all ;) an easy way to run into header padding problems, btw, is to connect to a QoS (WME) enabled access point (eg. madwifi) - QoS data frames are 2 byte longer and will require padding. this patch applies on top of luis latest patch series from 04.02.2008. drivers/net/wireless/ath5k/base.c: Changes-licensed-under: 3-Clause-BSD drivers/net/wireless/ath5k/hw.c: Changes-licensed-under: ISC Signed-off-by: Bruno Randolf <bruno@thinktube.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>		2008-02-15 13:44:17 -05:00
..
ath5k.h	ath5k: beacon interval is in TU	2008-01-28 15:10:50 -08:00
base.c	ath5k: correct padding in tx descriptors	2008-02-15 13:44:17 -05:00
base.h	ath5k: use SWBA to detect IBSS HW merges	2008-01-28 15:10:52 -08:00
debug.c	ath5k: debug level improvements	2008-01-31 19:26:35 -08:00
debug.h	ath5k: debug level improvements	2008-01-31 19:26:35 -08:00
hw.c	ath5k: correct padding in tx descriptors	2008-02-15 13:44:17 -05:00
hw.h
initvals.c
Makefile
phy.c
reg.h
regdom.c
regdom.h