Hi all,
This patch collapses all of the TXQ locking down to a single TX lock
and (mostly correctly) wraps the TX outbound path in a single, giant
lock.
The TX completion path is still a patchwork of locking, primarily
because _it_ needs to be able to free net80211 node references and
that can't b
Hi,
I meant to post this last night but fell asleep. :-)
I've verified that the 11n NIC <-> 11n NIC TDMA setup is working and
working stable.
I haven't yet run it over the course of "time needed to wrap a 32 bit
TSF", so that's next.
In this instance:
* TDMA master: AR9280
* TDMA slave: AR5416
Synopsis: [iwn] [patch] iwn(4) DOES support 6235 chip.
Responsible-Changed-From-To: freebsd-wireless->eadler
Responsible-Changed-By: eadler
Responsible-Changed-When: Fri Nov 30 23:25:59 UTC 2012
Responsible-Changed-Why:
I'll take it.
http://www.freebsd.org/cgi/query-pr.cgi?pr=173898
It's not that simple. Speak to bernhard.
There are other issues that he knows about. I don't know if he's
replied to the email or not; poke him on irc.
adrian
On 30 November 2012 15:25, wrote:
> Synopsis: [iwn] [patch] iwn(4) DOES support 6235 chip.
>
> Responsible-Changed-From-To: freebsd-
On 29 November 2012 22:58, Martin wrote:
> this is not good, if alternate MACs are not supported, because you also
> need them to configure multiple access points in hostapd. Take a look
> at the end of the hostapd.conf in examples. This definitely takes away
> features.
Alternate MACs are suppo
On 30 November 2012 20:28, Adrian Chadd wrote:
> It's not that simple. Speak to bernhard.
Davide, You mention some issues and I asked you to follow up to the
PR. Can you please explain them?
> There are other issues that he knows about. I don't know if he's
> replied to the email or not; poke
