All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Ledovskikh <nledovskikh@gmail.com>
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
Date: Fri, 18 Feb 2011 19:59:53 +0300	[thread overview]
Message-ID: <20110218195953.cf4e349f.nledovskikh@gmail.com> (raw)

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 <nledovskikh@gmail.com>
---
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;

             reply	other threads:[~2011-02-18 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 16:59 Nikolay Ledovskikh [this message]
2011-02-18 18:27 ` [PATCH] ath5k: Correct channel setting for AR2317 chip me
  -- strict thread matches above, loose matches on Subject: below --
2011-02-18 13:39 Nikolay Ledovskikh
2011-02-17  4:44 [PATCH] ath5k: Correct channel setting for ar2317 chip Nikolay Ledovskikh
2011-02-17 10:25 ` Jiri Slaby

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110218195953.cf4e349f.nledovskikh@gmail.com \
    --to=nledovskikh@gmail.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.