On Wed, Aug 20, 2014 at 1:29 PM, Adrian Chadd adr...@freebsd.org wrote:
Are you seeing RX CRC errors for all rates? CCK? OFDM? HT? At all distances?
CCK not sure, OFDM and HT yes. And at wide range of distances. (Tx
rates usually hit mcs 12 to 14 with 2s ht20 ap)
There's a handful of things
The following reply was made to PR kern/177451; it has been noted by GNATS.
From: PseudoCylon moonlightak...@yahoo.ca
To: bug-follo...@freebsd.org, dav...@freebsd.org
Cc:
Subject: Re: kern/177451: [ieee80211] page fault in ieee80211_tx_mgt_timeout
Date: Fri, 29 Mar 2013 16:37:20 -0600
Oops
On Mon, Feb 25, 2013 at 12:27 AM, Adrian Chadd adr...@freebsd.org wrote:
The trouble with using a queue is that things will dequeue frames out
of order, bceause multiple dequeue contexts (ie, each call to
driver_start / driver_transmit) will execute in-parallel.
Actually, to prevent that,
On Sun, Feb 24, 2013 at 12:45 AM, Adrian Chadd adr...@freebsd.org wrote:
On 23 February 2013 22:30, PseudoCylon moonlightak...@yahoo.ca wrote:
So, this is all pretty terrible. The only sane solution for now is to
make my VAP TX lock an IC TX lock,and grab said IC TX lock for all
VAPs. That way
--
Message: 12
Date: Fri, 22 Feb 2013 17:18:44 -0800
From: Adrian Chadd adr...@freebsd.org
To: freebsd-wireless@freebsd.org
Subject: Re: [RFT] net80211 TX serialisation, take #4
Message-ID:
On Fri, Feb 22, 2013 at 12:05 PM, Bernhard Schmidt
bschm...@techwires.net wrote:
On Friday, February 22, 2013 07:52:47 PM Adrian Chadd wrote:
Hm, it's possible in my sleep deprived state that I'm on the right but
wrong track here.
The OP problem is that we're not advertising the right
On Wed, Feb 20, 2013 at 9:40 PM, Adrian Chadd adr...@freebsd.org wrote:
On 20 February 2013 20:38, PseudoCylon moonlightak...@yahoo.ca wrote:
Who can we rope in to review whether this is being done right ?
Since it is ht param issue, anyone with 11n capable hardware with
working driver
On Wed, Feb 20, 2013 at 4:52 PM, Adrian Chadd adr...@freebsd.org wrote:
On 15 February 2013 21:18, Adrian Chadd adr...@freebsd.org wrote:
Oh lordie. :-)
Please file a PR so we don't forget to fix this? :)
Ok, you filed a PR with a patch.
Who can we rope in to review whether this is being
On Fri, Feb 15, 2013 at 4:03 PM, Adrian Chadd adr...@freebsd.org wrote:
The (many) problems include the two TX paths - one is via _start /
_transmit, and one is the raw xmit path.
So in the short term it'll be easier (!) to just wrap all TX entry
points with a VAP TX lock.
Once that's done
--
Message: 5
Date: Fri, 23 Nov 2012 17:21:30 +0300
From: Nikolay Tychina niktych...@gmail.com
To: freebsd-wireless@freebsd.org
Subject: Wireless Ralink Adapter is detected but doesn't work
Message-ID:
--
Message: 4
Date: Fri, 5 Oct 2012 23:44:10 -0700
From: Adrian Chadd adr...@freebsd.org
Subject: [RFC] How the TX path works; I'd like to fix this before 10.x
To: freebsd-wireless@freebsd.org
Message-ID:
--
Message: 1
Date: Thu, 27 Sep 2012 12:44:04 -0700
From: Adrian Chadd adr...@freebsd.org
Subject: Re: ath0_node_lock ath0_com_lock lor
To: Kim Culhan w8hd...@gmail.com
Cc: freebsd-wireless@freebsd.org
Message-ID:
12 matches
Mail list logo
