d you
>> linvi...@tuxdriver.com might be all we have. Be ready.
>
> This patchset is causing troubles here on a AR5212.
>
> # lspci -nnvv | grep -i ath
> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
> 802.11abg NIC [168c:1014] (rev
here on a AR5212.
# lspci -nnvv | grep -i ath
02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
802.11abg NIC [168c:1014] (rev 01)
Kernel driver in use: ath5k
With linux-next (next 20101203) I have to revert the 9 patches and
apply the 6 patches from Nick to regain a stab
Hi all,
I have an eeePC with the "Atheros Communications Inc. AR5001 Wireless
Network Adapter".
Im running emdebian with a custom 2.6.35.7 built kernel.
I connect to my WAP using:
modprobe -r ath5k
modprobe ath5k
wpa_supplicant -B -c/etc/wpa_supplicant/wpa_supplicant.conf -iwlan0
ifconfig wlan0 1
On Fri, Dec 3, 2010 at 9:55 AM, John W. Linville wrote:
> On Fri, Dec 03, 2010 at 06:03:00AM +0200, Nick Kossifidis wrote:
>> * By skipping tx power table calibration we also skip setting
>> tx power table on hw. Make sure we always write tx power table
>> on hw since it gets cleared on reset.
On Thu, Dec 02, 2010 at 08:17:41PM -0800, Luis R. Rodriguez wrote:
> On Thu, Dec 2, 2010 at 8:11 PM, Nick Kossifidis wrote:
> > * Change version number, we've added various new features lately.
> > We need to find a way to maintain this, maybe on each kernel release
> > or something. Also remov
On Fri, Dec 03, 2010 at 06:03:00AM +0200, Nick Kossifidis wrote:
> * By skipping tx power table calibration we also skip setting
> tx power table on hw. Make sure we always write tx power table
> on hw since it gets cleared on reset.
>
> Signed-off-by: Nick Kossifidis
Hey, Nick -- just a pro
> Hi,
>
> > Hi Wojciech,
> >
> >>> Hi all,
> >>>
> >>> I am trying to switch from madwifi to ath5k on AR2315 WiSoC (Fon
> >>> 2100A) using patches from Wojciech and Felix but at module
> loading
> >>> the
> >>> driver is not able to attach the HW. In particular it seems that
> >>> ath5k
> >>> is n
s.");
> MODULE_SUPPORTED_DEVICE("Atheros 5xxx WLAN cards");
> MODULE_LICENSE("Dual BSD/GPL");
> -MODULE_VERSION("0.6.0 (EXPERIMENTAL)");
> +MODULE_VERSION("0.7.0");
>
> static int ath5k_reset(struct ath5k_softc *sc, struct ieee80211_channel
Tested-by: Sedat Dilek
On Fri, Dec 3, 2010 at 5:12 AM, Nick Kossifidis wrote:
> * Since we report tx acks to the protocol stack, add the needed
> flag to hw_flags. This way we'll also use the new AP probing mechanism.
>
> Signed-off-by: Nick Kossifidis
>
> ---
> drivers/net/wireless/ath/ath
Tested-by: Sedat Dilek
On Fri, Dec 3, 2010 at 5:11 AM, Nick Kossifidis wrote:
> * Change version number, we've added various new features lately.
> We need to find a way to maintain this, maybe on each kernel release
> or something. Also remove "EXPERIMENTAL", we aren't experimental any
> mo
Tested-by: Sedat Dilek
On Fri, Dec 3, 2010 at 5:07 AM, Nick Kossifidis wrote:
> * Stop ANI durring reset to prevent false PHY error reports
>
> Signed-off-by: Nick Kossifidis
>
> ---
> drivers/net/wireless/ath/ath5k/base.c | 10 --
> 1 files changed, 8 insertions(+), 2 deletions(-)
Tested-by: Sedat Dilek
On Fri, Dec 3, 2010 at 5:09 AM, Nick Kossifidis wrote:
> * Correctly report failure to stop RX DMA
>
> Signed-off-by: Nick Kossifidis
>
> ---
> drivers/net/wireless/ath/ath5k/dma.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/n
Tested-by: Sedat Dilek
On Fri, Dec 3, 2010 at 5:03 AM, Nick Kossifidis wrote:
> * By skipping tx power table calibration we also skip setting
> tx power table on hw. Make sure we always write tx power table
> on hw since it gets cleared on reset.
>
> Signed-off-by: Nick Kossifidis
>
> ---
>
Tested-by: Sedat Dilek
On Fri, Dec 3, 2010 at 5:05 AM, Nick Kossifidis wrote:
> * Always free tx buffers before reset, since we also empty hw queues.
> If we don't and a queue gets stuck, we'll never decrease txq_len and sw
> will keep thinking the queue is still stuck even after reset.
>
>
On 12/02/2010 04:47 PM, Jeroen Avonts wrote:
> I can recreate the issue as follows:
[...]
> Note that wireshark was unable to decrypt the unsuccessful ping message with
> the provided key.
Hi Jeroen,
thanks for reproducing this, makes me feel much less paranoid ;-)
--
Stefan Nickl
System Engin
15 matches
Mail list logo
