* Re: 2.6.33.2: Turn tx power off/on for Atheros card [not found] <r2xf69abfc31005050326oe123cb60s131ab4969341ef57@mail.gmail.com> @ 2010-05-06 14:52 ` Yegor Yefremov [not found] ` <g2wf69abfc31005060752w6876439cm45f5be68001c8382-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 2+ messages in thread From: Yegor Yefremov @ 2010-05-06 14:52 UTC (permalink / raw) To: linux-wireless; +Cc: netdev On Wed, May 5, 2010 at 12:26 PM, Yegor Yefremov <yegorslists@googlemail.com> wrote: > I'm using kernel 2.6.33.2 with AR2413 WLAN card. Issuing > > iwconfig wlan0 txpower off > > turns txpower off. I can see this status by iwconfig wlan0 and the > communication with AP terminates. But when I turn the txpower on > > iwconfig wlan0 txpower on > > nothing happens. Though iwconfig shows the previous tx power value. > Only ifconfig wlan0 down and then up recovers the transmission. > > Is it a known bug or I'm doing something wrong? I made some debugging and found out that after iwconfig wlan0 txpower off dev_close() will be invoked, so that local->open_count will be 0. The next time txpower on will be called, it will be checked if local->open_count > 0 and this conditions fails, so no hardware configuration will be made. I've made a quick and dirty hack, that opens the wireless device by enabling the txpower, if it was closed before. Is there any proper solution? Is it really necessary to close device to tunr txpower off? Best regards, Yegor Index: b/net/wireless/wext-compat.c =================================================================== --- a/net/wireless/wext-compat.c 2010-04-30 05:02:05.000000000 +0200 +++ b/net/wireless/wext-compat.c 2010-05-06 16:31:20.000000000 +0200 @@ -15,6 +15,7 @@ #include <linux/slab.h> #include <net/iw_handler.h> #include <net/cfg80211.h> +#include "../mac80211/ieee80211_i.h" #include "wext-compat.h" #include "core.h" @@ -824,6 +825,7 @@ { struct wireless_dev *wdev = dev->ieee80211_ptr; struct cfg80211_registered_device *rdev = wiphy_to_dev(wdev->wiphy); + struct ieee80211_local *local = wiphy_priv(wdev->wiphy); enum tx_power_setting type; int dbm = 0; @@ -861,6 +863,8 @@ type = TX_POWER_LIMITED; } } + if(!local->open_count) + dev_open(wdev->netdev); } else { rfkill_set_sw_state(rdev->rfkill, true); schedule_work(&rdev->rfkill_sync); ^ permalink raw reply [flat|nested] 2+ messages in thread
[parent not found: <g2wf69abfc31005060752w6876439cm45f5be68001c8382-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: 2.6.33.2: Turn tx power off/on for Atheros card [not found] ` <g2wf69abfc31005060752w6876439cm45f5be68001c8382-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2010-05-06 22:16 ` Luis R. Rodriguez 0 siblings, 0 replies; 2+ messages in thread From: Luis R. Rodriguez @ 2010-05-06 22:16 UTC (permalink / raw) To: Yegor Yefremov Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA, netdev-u79uwXL29TY76Z2rM5mHXA On Thu, May 6, 2010 at 7:52 AM, Yegor Yefremov <yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote: > On Wed, May 5, 2010 at 12:26 PM, Yegor Yefremov > <yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote: >> I'm using kernel 2.6.33.2 with AR2413 WLAN card. Issuing >> >> iwconfig wlan0 txpower off >> >> turns txpower off. I can see this status by iwconfig wlan0 and the >> communication with AP terminates. But when I turn the txpower on >> >> iwconfig wlan0 txpower on >> >> nothing happens. Though iwconfig shows the previous tx power value. >> Only ifconfig wlan0 down and then up recovers the transmission. >> >> Is it a known bug or I'm doing something wrong? > > I made some debugging and found out that after iwconfig wlan0 txpower > off dev_close() will be invoked, so that local->open_count will be 0. > The next time txpower on will be called, it will be checked if > local->open_count > 0 and this conditions fails, so no hardware > configuration will be made. > > I've made a quick and dirty hack, that opens the wireless device by > enabling the txpower, if it was closed before. Is there any proper > solution? Is it really necessary to close device to tunr txpower off? Depends on the type of interfaces you have. For a monitor device it makes no sense to close the device as you should be able to still RX. It also is possible to TX over a monitor device using frame injection so technically setting tx power to off would just mute it and would seem useful. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-05-06 22:16 UTC | newest] Thread overview: 2+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <r2xf69abfc31005050326oe123cb60s131ab4969341ef57@mail.gmail.com> 2010-05-06 14:52 ` 2.6.33.2: Turn tx power off/on for Atheros card Yegor Yefremov [not found] ` <g2wf69abfc31005060752w6876439cm45f5be68001c8382-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2010-05-06 22:16 ` Luis R. Rodriguez
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).