<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/net/mac80211/trace.h, branch linux-3.8.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.8.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.8.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2012-11-26T11:42:59Z</updated>
<entry>
<title>mac80211: convert to channel definition struct</title>
<updated>2012-11-26T11:42:59Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2012-11-09T10:39:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4bf88530be971bf95a7830ca61b4120980bf4347'/>
<id>urn:sha1:4bf88530be971bf95a7830ca61b4120980bf4347</id>
<content type='text'>
Convert mac80211 (and where necessary, some drivers a
little bit) to the new channel definition struct.

This will allow extending mac80211 for VHT, which is
currently restricted to channel contexts since there
are no drivers using that which makes it easier. As
I also don't care about VHT for drivers not using the
channel context API, I won't convert the previous API
to VHT support.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>cfg80211: remove remain-on-channel channel type</title>
<updated>2012-11-26T11:42:58Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2012-11-08T17:31:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=42d97a599eb6b2aab3a401b3e5799a399d6c7652'/>
<id>urn:sha1:42d97a599eb6b2aab3a401b3e5799a399d6c7652</id>
<content type='text'>
As mwifiex (and mac80211 in the software case) are the
only drivers actually implementing remain-on-channel
with channel type, userspace can't be relying on it.
This is the case, as it's used only for P2P operations
right now.

Rather than adding a flag to tell userspace whether or
not it can actually rely on it, simplify all the code
by removing the ability to use different channel types.
Leave only the validation of the attribute, so that if
we extend it again later (with the needed capability
flag), it can't break userspace sending invalid data.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>mac80211: make remain_on_channel() op pass vif param</title>
<updated>2012-11-19T15:20:37Z</updated>
<author>
<name>Eliad Peller</name>
</author>
<published>2012-11-19T15:05:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=49884568628db47a1f8c1f596c6ab3b8db81b73c'/>
<id>urn:sha1:49884568628db47a1f8c1f596c6ab3b8db81b73c</id>
<content type='text'>
Drivers (e.g. wl12xx) might need to know the vif
to roc on (mainly in order to configure the
rx filters correctly).

Add the vif to the op params, and update the current
users (iwlwifi) to use the new api.

Signed-off-by: Eliad Peller &lt;eliad@wizery.com&gt;
[fix hwsim]
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>mac80211: call driver method when restart completes</title>
<updated>2012-11-09T16:34:35Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2012-11-06T18:18:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9214ad7f9a0bfbfb2c204305e7391ce8b7fe4d29'/>
<id>urn:sha1:9214ad7f9a0bfbfb2c204305e7391ce8b7fe4d29</id>
<content type='text'>
When the driver requests a restart (reconfiguration) it
gets all the normal method calls, but can't really tell
why they're happening. Call a new restart_complete op
in the driver when the restart completes, so it could
keep its own state about the restart and clear it there.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>mac80211: remove unused tracepoint</title>
<updated>2012-11-09T16:30:50Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2012-11-08T17:16:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=60762cbfebafe41425e39d32efc07f260d4a100c'/>
<id>urn:sha1:60762cbfebafe41425e39d32efc07f260d4a100c</id>
<content type='text'>
Clearly the tracepoint drv_offchannel_tx was
forgotten when that functionality was removed,
remove it now.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>mac80211: pass P2P powersave parameters to driver</title>
<updated>2012-11-06T12:25:06Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2012-10-29T19:08:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=488dd7b53de9ea41edf7a475be63da51bdd05093'/>
<id>urn:sha1:488dd7b53de9ea41edf7a475be63da51bdd05093</id>
<content type='text'>
While connected to a GO, parse the P2P NoA attribute
and pass the CT Window and opportunistic powersave
parameters to the driver.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>mac80211: handle TX power per virtual interface</title>
<updated>2012-10-30T08:11:34Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2012-10-24T08:59:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1ea6f9c0d48b11b6ec3ec4b5579ec74fc3951cf8'/>
<id>urn:sha1:1ea6f9c0d48b11b6ec3ec4b5579ec74fc3951cf8</id>
<content type='text'>
Even before channel contexts/multi-channel, having a
single global TX power limit was already problematic,
in particular if two managed interfaces connected to
two APs with different power constraints. The channel
context introduction completely broke this though and
in fact I had disabled TX power configuration there
for drivers using channel contexts.

Change everything to track TX power per interface so
that different user settings and different channel
maxima are treated correctly. Also continue tracking
the global TX power though for compatibility with
applications that attempt to configure the wiphy's
TX power globally.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>mac80211: add explicit AP/GO driver operations</title>
<updated>2012-10-26T10:57:06Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2012-10-19T13:44:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1041638f2bba0f1de75e66086d50fb1251d64dcf'/>
<id>urn:sha1:1041638f2bba0f1de75e66086d50fb1251d64dcf</id>
<content type='text'>
Depending on the driver, a lot of setup may be
necessary to start operating as an AP, some of
which may fail. Add an explicit AP start driver
method to make such failures easier to handle,
and add an AP stop driver method for symmetry.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>mac80211: complete bss_info tracing</title>
<updated>2012-10-25T11:54:09Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2012-10-24T09:38:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1724ffbc7439de679d536163e03f54f35574d449'/>
<id>urn:sha1:1724ffbc7439de679d536163e03f54f35574d449</id>
<content type='text'>
Some fields have been added but were missed in
tracing, add them now.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>mac80211: track needed RX chains for channel contexts</title>
<updated>2012-10-17T09:02:09Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2012-09-11T12:34:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=04ecd2578e712c301fa1369d2a8f298a2b4b146a'/>
<id>urn:sha1:04ecd2578e712c301fa1369d2a8f298a2b4b146a</id>
<content type='text'>
On each channel that the device is operating on, it
may need to listen using one or more chains depending
on the SMPS settings of the interfaces using it. The
previous channel context changes completely removed
this ability (before, it was available as the SMPS
mode).

Add per-context tracking of the required static and
dynamic RX chains and notify the driver on changes.
To achieve this, track the chains and SMPS mode used
on each virtual interface and update the channel
context whenever this changes.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
</feed>
