Search Linux Wireless

[RFCv2] respect channels in iface combinations

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

 



Hi,

Here goes an updated patchset with multi-channel work on
cfg80211. Thanks go to Johannes and Eliad for review and
pointing out my mistakes.

I've addressed the issue with non-fixed channel IBSS.
Channels are now cosidered either shared or exclusive. An
exclusive channel always takes a channel resource (when
accouting interface combinations and
num_different_channels). Exclusive channel could also be
called hopping but I thought the first one fits better as it
explicitly states code logic decisions.

I've also refactored and fixed interface combination
checking. There are now functions like
cfg80211_can_use_chan, cfg80211_can_use_iftype_chan.

Monitor channel is now always defined. When there are
only monitors running we set a channel (first we can find in
supported bands structures). This way the corner case
(of a monitor not having a channel and .get_channel
returning NULL) mentioned by Johannes is fixed.

This is based on wireless-next tree.


-- Pozdrawiam / Best regards, Michal Kazior.


--
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