#508: Setting TXpower Issues
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: dyqith
Type: defect | Status: assigned
Priority: major | Milestone: version 0.9.0 - move to new
codebase
Component: madwifi: driver | Version: trunk
Resolution: | Keywords:
Patch_attached: 1 |
-----------------------------------+----------------------------------------
Comment (by dyqith):
{{{
Why do you move set_node_txpower() to if_ath.c?
}}}
I think the ath_update_txpow clamps the tx power from the user to the
regulatory one.
Leaving it in the ieee80211_wireless.c makes it so the nodes can all get
higher values than the regulatory one. ath_update_txpow also updates all
the VAPs, so I thought it might as well update all the VAP's nodes too.
Will also fix the coding format :)
{{{
ticket about locking stuff...
}}}
Yeah, I'm working on that ticket too... I'm getting a few kernel panics
from NULL pointer derefs, which shouldn't really happen.
{{{
Yes, I think this would be a good idea, although deciding about what "more
meaningful" actually means might become a difficult thing :)
}}}
This patch changes the starting txpower to be 0. I think it makes more
sense than 50.
--
Ticket URL: <http://madwifi.org/ticket/508>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
