On Thu, Nov 12, 2015 at 04:34:11PM +0530, Rajkumar Manoharan wrote: > On Wed, Oct 28, 2015 at 11:00:05PM +0200, Jouni Malinen wrote: > > On Fri, Oct 23, 2015 at 06:22:14PM +0530, Rajkumar Manoharan wrote: > > > Add VHT transmit power envelope element defined in IEEE std > > > 802.11ac-2013 8.4.2.164 for VHT bandwidth channel switch. > > > > Please note that this has been renamed to "Transmit Power Envelope > > element" in REVmc (i.e., "VHT" removed from the name). > > > Will remove VHT in next version. Should I keep the spec. section as it > is? You could refer to IEEE P802.11-REVmc/D4.3, 8.4.2.161 for Transmit Power Envelope element, but anyway, it is fine to use IEEE Std 802.11ac-2013 in the commit message and just remove VHT from the actual code changes. > > > + /* > > > + * Local Maximum Transmit power is encoded as 2's complement > > > + * with a 0.5 dB step > > > + */ > > > + max_tx_power = ~(chan->max_tx_power * 2) + 1; > > > + *eid++ = max_tx_power; > > > + *eid++ = max_tx_power; > > > + *eid++ = max_tx_power; > > > > Could you please clarify why all three values are set to the same value? > > Would there be no case where the local maximum transmit power is > > different for 20, 40, and 80 MHz channel cases? > > > Since I do not find per bandwidth max tx power, I used the channel max > tx power for all bandwith. Is there a way to extract per-bw max tx power from > regulatory. Please help. No idea how that could be done, but the design here does not look correct. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
