linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [ANN] wireless-regdb: master-2015-10-13
@ 2015-10-13 18:50 Seth Forshee
  2015-10-14  9:36 ` mac80211 and ath9k channel context Wim Torfs
  0 siblings, 1 reply; 2+ messages in thread
From: Seth Forshee @ 2015-10-13 18:50 UTC (permalink / raw)
  To: linux-wireless; +Cc: wireless-regdb, Luis R. Rodriguez

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

* mac80211 and ath9k channel context
  2015-10-13 18:50 [ANN] wireless-regdb: master-2015-10-13 Seth Forshee
@ 2015-10-14  9:36 ` Wim Torfs
  0 siblings, 0 replies; 2+ messages in thread
From: Wim Torfs @ 2015-10-14  9:36 UTC (permalink / raw)
  To: linux-wireless; +Cc: Luis R. Rodriguez

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-10-14  9:37 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-10-13 18:50 [ANN] wireless-regdb: master-2015-10-13 Seth Forshee
2015-10-14  9:36 ` mac80211 and ath9k channel context Wim Torfs

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).