Return-path: Received: from mail-bw0-f42.google.com ([209.85.214.42]:36988 "EHLO mail-bw0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751182Ab1BRRJG (ORCPT ); Fri, 18 Feb 2011 12:09:06 -0500 Received: by bwz13 with SMTP id 13so535500bwz.1 for ; Fri, 18 Feb 2011 09:09:05 -0800 (PST) Date: Fri, 18 Feb 2011 19:59:53 +0300 From: Nikolay Ledovskikh To: linville@tuxdriver.com Cc: linux-wireless@vger.kernel.org, lrodriguez@atheros.com, mickflemm@gmail.com, me@bobcopeland.com, jirislaby@gmail.com Subject: [PATCH] ath5k: Correct channel setting for AR2317 chip Message-Id: <20110218195953.cf4e349f.nledovskikh@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: Correct channel setting function must be used for AR2317. When I tested ahb patch on bullet2 all seemed to work fine, but it couldn't connect another host (using ibss for example). During an analysis I observed that it's transmitting on another channel. I looked into madwifi code and understood that the problem is in channel setting function. So atheros RF2317 not fully handled in the current ath5k version and must be patched. Signed-off-by: Nikolay Ledovskikh --- diff --git a/drivers/net/wireless/ath/ath5k/phy.c b/drivers/net/wireless/ath/ath5k/phy.c index 78c26fd..c44111f 100644 --- a/drivers/net/wireless/ath/ath5k/phy.c +++ b/drivers/net/wireless/ath/ath5k/phy.c @@ -1253,6 +1253,7 @@ static int ath5k_hw_channel(struct ath5k_hw *ah, case AR5K_RF5111: ret = ath5k_hw_rf5111_channel(ah, channel); break; + case AR5K_RF2317: case AR5K_RF2425: ret = ath5k_hw_rf2425_channel(ah, channel); break;