#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 mrenzmann):
And some answers to your initial questions:
{{{
#!blockquote
1) CHANNEL MUST be SET before txpower can be changed!!! (Should this be so
or should it be changed ?)
}}}
I think this is correct (not sure though). The reason is that each channel
might have its own regulatory limits. For example, in Germany (and other
ETSI-regulated countries) some of the 11a channels might only be used with
lower TX power in outdoor setups, but with higher limits in indoor
installations. Unless we know which channel is about to be used, it will
be hard to make a correct assumption about whether the user-selected TX
power is allowed or not.
{{{
#!blockquote
3) I think there's a race condition issue between the ath_update_txpow
(uses vaps) and the wlanconfig ath0 destroy command, needs some locking
intervention
}}}
This probably is the case for a lot of other situations, too. Iirc we have
a ticket about locking stuff, and that area should receive some more
attention IMO.
{{{
#!blockquote
4) Doing an iwconfig ususally shows the wrong value of txpower if nothing
was set. Should we set the txpower to something more meaningful first
(goes for all outputs)
}}}
Yes, I think this would be a good idea, although deciding about what "more
meaningful" actually means might become a difficult thing :)
--
Ticket URL: <http://madwifi.org/ticket/508>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
