A new release of wireless-regdb (master-2015-10-13) is available at:
https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2015.10.13.tar.gz
The short log of changes since the 2015-09-25 release is below.
Thanks,
Seth
---
Chen-Yu Tsai (5):
wireless-regdb: Update U-NII-2c (5470 ~ 5725 MHz) rules for Taiwan (TW)
wireless-regdb: Update regulatory rule boundary frequencies for Taiwan (TW)
wireless-regdb: Update 5GHz rules for US
wireless-regdb: Add U-NII-1 (5150 ~ 5250 MHz) band for Taiwan (TW)
wireless-regdb: Update 5 GHz rules for Taiwan (TW) to follow US
Jouni Malinen (4):
wireless-regdb: Update regulatory rules for Uruguay (UY)
wireless-regdb: Add VHT channel bandwidth for Russia (RU)
wireless-regdb: Add VHT channel bandwidth for Ukraine (UA)
wireless-regdb: Update regulatory rules for Malaysia (MY)
Seth Forshee (2):
wireless-regdb: Update ZA rules for 5490-5710 MHz
wireless-regdb: update regulatory.bin based on preceding changes
Hi,
The channel context is mentioned in lots of mails and pieces of code,
but its significance or goal is never mentioned. Could someone please be
so kind to elaborate on this?
I believe the channel context is used to provide some hardware
abstraction towards the driver and mac, such that virtual interfaces are
able to work "in parallel" (to their knowledge they are the sole users)
on the hardware, even when they use different channels. When a virtual
interface needs to perform some action (transmission,...), the channel
is set to the corresponding channel of the interface. Furthermore is the
activation of virtual interfaces done in a round robin manner, where
each channel in the channel context is activated at a periodic interval.
Is this about correct, or am I gravely mistaken?
Thanks,
Kind regards,
Wim.