Search Linux Wireless

Re: [RFCv2] mac80211: Don't let regulatory make us deaf

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Feb 27, 2012 at 12:38:50PM +0100, Johannes Berg wrote:
> On Mon, 2012-02-27 at 13:32 +0200, Jouni Malinen wrote:
> > However, there
> > could be some hardware/firmware designs that would refuse HT+TKIP at
> > lower layer, so skipping the channel (re-)configuration could
> > potentially cause some problems.

> That's a good point, but I don't really think is likely to exist. I can
> see this in a full-MAC scenario, but there you get all the relevant
> parameters in the nl80211 connect() call so can do the right choices
> earlier than mac80211 can with auth/assoc calls.

Even full MAC designs may end up moving towards auth/assoc calls for
things like IEEE 802.11r.. (And maybe even more so with 802.11ai
eventually.)

> Of course, if this we actually happen to come across a device that needs
> this it could set a flag somehwere and mac80211 could re-configure the
> channel to non-HT on the assoc request, but right now I'd rather not
> worry about that since we're moving towards multi-channel and have no
> indication of such devices existing. Agree?

Yeah, that works for me.

-- 
Jouni Malinen                                            PGP id EFC895FA
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux